From: Andrew Morton <akpm@osdl.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc6-mm1 (NFS tree ... busy inodes ... relatively harmless)
Date: Sun, 12 Mar 2006 20:47:36 -0800 [thread overview]
Message-ID: <20060312204736.3102c314.akpm@osdl.org> (raw)
In-Reply-To: <17428.63369.446803.958721@cse.unsw.edu.au>
Neil Brown <neilb@suse.de> wrote:
>
> On Sunday March 12, akpm@osdl.org wrote:
> >
> > - The NFS tree is a bit sick - you may see the `busy inodes - self destruct
> > in five seconds" message when performing NFS unmounts. It seems relatively
> > harmless.
>
> I think the term is "mostly harmless" ... see the entry for "Earth" in
> The Hitch-Hikers Guide To The Galaxy... :-)
>
> I don't believe this is harmless at all, and I have an oops to prove
> it - though it is with NFSv4 which is still EXPERIMENTAL.
>
> I don't believe it is an NFS bug at all, but a VFS bug. It happens
> more with NFS because iput on nfs can be a lot slower due to the
> required network activity, so the race is easier to hit.
It's 100% repeatable for me, with nfsv3 unmounts. First the busy inodes,
then a use-after-free oops if CONFIG_DEBUG_PAGEALLOC (if that workaround
patch I have in there isn't applied).
Not a race, methinks.
next prev parent reply other threads:[~2006-03-13 4:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 11:10 2.6.16-rc6-mm1 Andrew Morton
2006-03-12 13:16 ` 2.6.16-rc6-mm1 Rafael J. Wysocki
2006-03-12 13:35 ` 2.6.16-rc6-mm1 Sam Ravnborg
2006-03-12 13:49 ` 2.6.16-rc6-mm1 Rafael J. Wysocki
2006-03-12 14:29 ` [PATCH] kbuild: fix genksyms build error Sam Ravnborg
2006-03-12 15:46 ` 2.6.16-rc6-mm1 Benoit Boissinot
2006-03-12 15:48 ` 2.6.16-rc6-mm1 Benoit Boissinot
2006-03-12 15:55 ` 2.6.16-rc6-mm1 Benoit Boissinot
2006-03-12 18:45 ` 2.6.16-rc6-mm1: BUG at fs/sysfs/inode.c:180 Laurent Riffard
2006-03-12 22:55 ` Alexey Dobriyan
2006-03-12 23:33 ` Laurent Riffard
2006-03-12 23:01 ` Andrew Morton
2006-03-13 14:00 ` Maneesh Soni
2006-03-13 17:04 ` Laurent Riffard
2006-03-13 19:22 ` Greg KH
2006-03-14 3:23 ` Maneesh Soni
2006-03-12 21:43 ` BUG: atomic counter underflow [Was: 2.6.16-rc6-mm1] Jiri Slaby
2006-03-13 3:35 ` Ian Kent
2006-03-13 5:33 ` Ian Kent
2006-03-17 16:47 ` Jiri Slaby
2006-03-17 17:47 ` Jiri Slaby
2006-03-19 1:06 ` Jiri Slaby
2006-03-19 1:19 ` Jiri Slaby
2006-03-23 11:44 ` Ian Kent
2006-03-12 21:47 ` 2.6.16-rc6-mm1 Grant Coady
2006-03-13 3:18 ` 2.6.16-rc6-mm1 James Morris
2006-03-13 4:39 ` 2.6.16-rc6-mm1 (NFS tree ... busy inodes ... relatively harmless) Neil Brown
2006-03-13 4:47 ` Andrew Morton [this message]
2006-03-13 21:14 ` [-mm patch] sound/pci/ice1712/delta.c: make 2 functions static Adrian Bunk
2006-03-14 11:16 ` Takashi Iwai
2006-03-13 21:16 ` [RFC: -mm patch] remove drivers/message/fusion/mptscsih.c:mptscsih_setDevicePage1Flags() Adrian Bunk
2006-03-13 21:19 ` [RFC: -mm patch] fs/nfsd/export.c,net/sunrpc/cache.c: make needlessly global code static Adrian Bunk
2006-03-13 21:21 ` [RFC: -mm patch] remove drivers/scsi/constants.c:scsi_print_req_sense() Adrian Bunk
2006-03-13 21:26 ` [-mm patch] make drivers/net/tg3.c:tg3_request_irq() Adrian Bunk
2006-03-15 1:04 ` David S. Miller
2006-03-13 21:28 ` [-mm patch] dvb/frontends/zl10353.c: make a function static Adrian Bunk
2006-03-15 7:41 ` 2.6.16-rc6-mm1 Nishanth Aravamudan
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=20060312204736.3102c314.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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
Powered by JetHome