From: Keith Owens <kaos@ocs.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH] large /proc/mounts and friends
Date: Tue, 16 Oct 2001 15:16:40 +1000 [thread overview]
Message-ID: <20357.1003209400@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 15 Oct 2001 21:41:49 MST." <Pine.LNX.4.33.0110152132110.8730-100000@penguin.transmeta.com>
On Mon, 15 Oct 2001 21:41:49 -0700 (PDT),
Linus Torvalds <torvalds@transmeta.com> wrote:
> s_seek()
> {
> struct mod_sym *v = p;
> int mod_nr = pos >> 32;
> while (mod_nr && v->mod) {
> mod_nr--;
> v->mod = v->mod->next;
> };
> }
If a module is deleted between calls to s_seek() and that deletion is
before mod_nr then the caller has seen the deleted module but a later
module will transiently disappear. I don't see how counting on a
linked list which is subject to deletion at any point can deliver
reliable results. Seeing the old module is wrong but acceptable. Not
seeing a module that still exists is wrong.
next prev parent reply other threads:[~2001-10-16 5:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 1:10 [CFT][PATCH] large /proc/mounts and friends Alexander Viro
2001-10-16 3:01 ` Linus Torvalds
2001-10-16 3:45 ` Alexander Viro
2001-10-16 4:01 ` Linus Torvalds
2001-10-16 4:08 ` Alexander Viro
2001-10-16 9:58 ` Chris Wedgwood
2001-10-16 3:52 ` Linus Torvalds
2001-10-16 4:03 ` Alexander Viro
2001-10-16 4:29 ` Linus Torvalds
2001-10-16 4:41 ` Linus Torvalds
2001-10-16 5:16 ` Keith Owens [this message]
2001-10-17 2:09 ` Alexander Viro
2001-10-16 4:43 ` Alexander Viro
2001-10-16 4:05 ` Anton Blanchard
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=20357.1003209400@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.