From: David Mosberger <davidm@napali.hpl.hp.com>
To: Roland McGrath <roland@redhat.com>
Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com
Subject: Re: second thoughts on using dl_iterate_phdr() for cache-validation
Date: Fri, 05 Nov 2004 02:09:00 -0000 [thread overview]
Message-ID: <16778.57550.54390.106251@napali.hpl.hp.com> (raw)
In-Reply-To: <200411050136.iA51aPf6004341@magilla.sf.frob.com>
>>>>> On Thu, 4 Nov 2004 17:36:25 -0800, Roland McGrath <roland@redhat.com> said:
>> So when should I check back?
Roland> You should take responsibility for the work you want done
Roland> and continue improving it until you've submitted a patch
Roland> that has nothing wrong with it. Please don't pretend there
Roland> is some mystery about how to contribute effectively.
I'm not sure I understand. You said the tree is currently closed for
new interfaces. All I'm asking is when you're expecting the tree to
reopen again.
>> Fine; I don't mind changing it back to "unsigned long int".
Roland> What is the documentation about the meaning of the values
Roland> and the effects of overflow?
As for the meaning of the values, see the documentation in link.h:
----
/* The value returned by this function increments by at least 1 when
objects are added to the list visited by dl_iterate_phdr(). This
function is not serialized with respect to dl_iterate_phdr(). If
serialization is needed, this function should be called from within
a dl_itereate_phdr() callback. */
extern unsigned long int dl_phdr_additions_counter (void);
/* The vaue returned by this function increments by at least 1 when
objects are removed from the list visited by dl_iterate_phdr().
This function is not serialized with respect to dl_iterate_phdr().
If serialization is needed, this function should be called from
within a dl_itereate_phdr() callback. */
extern unsigned long int dl_phdr_removals_counter (void);
----
I'll add a comment about the possibility of overflows.
--david
next prev parent reply other threads:[~2004-11-05 2:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 8:53 David Mosberger
2004-03-31 16:04 ` Roland McGrath
2004-04-01 2:33 ` David Mosberger
2004-11-04 23:41 ` David Mosberger
2004-11-04 23:53 ` Roland McGrath
2004-11-05 0:40 ` David Mosberger
2004-11-05 1:10 ` Roland McGrath
2004-11-05 1:28 ` David Mosberger
2004-11-05 1:36 ` Roland McGrath
2004-11-05 2:09 ` David Mosberger [this message]
2004-11-05 3:27 ` Roland McGrath
2004-11-06 0:21 ` David Mosberger
2004-11-06 2:32 ` Roland McGrath
2004-11-09 0:15 ` David Mosberger
2004-11-09 4:40 ` Roland McGrath
2004-11-10 5:40 ` David Mosberger
2004-11-10 20:36 ` David Mosberger
2004-11-10 20:45 ` Roland McGrath
2004-11-11 6:17 ` David Mosberger
2004-11-11 22:24 ` Roland McGrath
2004-11-12 19:32 ` David Mosberger
2004-04-15 18:28 David Mosberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16778.57550.54390.106251@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).