From: Eric Dumazet <eric.dumazet@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NeilBrown <neilb@suse.de>, Greg Banks <gnb@fastmail.fm>,
Christoph Hellwig <hch@infradead.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
David Miller <davem@davemloft.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] sunrpc: use better NUMA affinities
Date: Sun, 28 Aug 2011 12:02:24 +0200 [thread overview]
Message-ID: <1314525744.3036.10.camel@edumazet-laptop> (raw)
In-Reply-To: <20110827000219.GF18699@fieldses.org>
Le vendredi 26 août 2011 à 20:02 -0400, J. Bruce Fields a écrit :
> On Sun, Jul 31, 2011 at 08:58:54AM +0200, Eric Dumazet wrote:
> > Le samedi 30 juillet 2011 à 08:23 +0200, Eric Dumazet a écrit :
> > > Le samedi 30 juillet 2011 à 16:06 +1000, NeilBrown a écrit :
> > > > umount /proc/fs/nfsd
> > > >
> > > >
> > >
> > > Thans a lot, this was the thing I missed !
> > >
> > >
> >
> > Hmm, after this, I left things as the were (nfsd module loaded, but a 0
> > use count )
> >
> > I got a BUG while updatedb was running,
> > (I tried this on a debian machine/kernel)
> >
> > Same bug on :
> >
> > cat /proc/self/mounts
>
> Any luck figuring this out?
>
> I tried reproducing, by stopping everything to get nfsd refcount to
> zero:
>
> # lsmod | grep '^nfsd'
> nfsd 300025 0
>
> then running 'cat /proc/self/mounts'.
>
> But I don't see any crash.
>
> This is only 3.1.0-rc1 plus some nfsd patches.
>
> --b.
>
> >
> > I'll take a look at this issue later, after my vacations, unless someone
> > wants to take a look before me ;)
Unfortunately, latest linux tree doesnt even boot on my machine, so I
cannot reproduce the problem right now.
Last message displayed being "Switching to clocksource tsc"
Previous kernels were continuing with :
[ 4.448417] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 4.597727] Real Time Clock Driver v1.12b
Might be a problem with latest tty changes
next prev parent reply other threads:[~2011-08-28 10:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110729153207.17af3085@notabene.brown>
2011-07-29 6:05 ` Fw: " Greg Banks
2011-07-29 6:30 ` Eric Dumazet
2011-07-29 6:53 ` Greg Banks
2011-07-29 10:36 ` Christoph Hellwig
2011-07-29 11:58 ` Greg Banks
2011-07-29 12:11 ` Eric Dumazet
2011-07-29 13:30 ` Greg Banks
2011-07-29 16:48 ` J. Bruce Fields
2011-07-29 16:53 ` J. Bruce Fields
2011-07-29 18:15 ` Eric Dumazet
2011-07-29 20:34 ` Greg Banks
2011-07-29 23:30 ` NeilBrown
2011-07-29 23:48 ` J. Bruce Fields
2011-07-30 4:08 ` Eric Dumazet
2011-07-30 6:06 ` NeilBrown
2011-07-30 6:23 ` Eric Dumazet
2011-07-31 6:58 ` Eric Dumazet
2011-08-27 0:02 ` J. Bruce Fields
2011-08-28 10:02 ` Eric Dumazet [this message]
2011-08-02 1:06 ` J. Bruce Fields
2011-07-29 16:45 ` Fw: " J. Bruce Fields
2011-07-29 20:24 ` Greg Banks
2011-07-29 16:48 ` Fw: " J. Bruce Fields
2011-07-28 18:04 Eric Dumazet
2011-07-29 16:42 ` J. Bruce Fields
2011-07-29 18:02 ` Eric Dumazet
2011-07-29 18:08 ` J. Bruce Fields
2011-07-29 20:39 ` Greg Banks
2011-08-05 21:28 ` J. Bruce Fields
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=1314525744.3036.10.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=gnb@fastmail.fm \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®