From: Bruce Fields <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Larry McVoy <lm@bitmover.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: kernel BUG at /build/buildd/linux-3.2.0/fs/lockd/clntxdr.c:226!
Date: Wed, 17 Oct 2012 10:00:20 -0400 [thread overview]
Message-ID: <20121017140020.GA25488@fieldses.org> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9091FFA38@SACEXCMBX04-PRD.hq.netapp.com>
On Sat, Oct 13, 2012 at 04:42:05AM +0000, Myklebust, Trond wrote:
> On Fri, 2012-10-12 at 19:56 -0700, Larry McVoy wrote:
> > On Sat, Oct 13, 2012 at 02:52:51AM +0000, Myklebust, Trond wrote:
> > > On Fri, 2012-10-12 at 19:31 -0700, Larry McVoy wrote:
> > > > As I've said, debugging this is going to be hard, it means stopping my
> > > > company. We can do one more crash, you guys can tell me what to do,
> > > > but that's about it.
> > >
> > > Do you have a reproducer?
> >
> > Oh yeah, it happens every time. Run skype on a mac w/ your home dir NFS
> > mounted. Skype tries to do some lock operation and the machine panics.
> >
> > We've done it 4 times in a row to be sure we weren't smoking crack. No
> > crack. Just panics.
>
> OK. I think I can see what is happening. We need to filter the return
> values from nlm_lookup_file() when dealing with NLMv1 and NLMv3.
>
> Can you please try the attached patch?
Larry, did you get a chance to test this patch?
It seems obviously right anyway, so I'll go ahead and pass it along
regardless, but it would be nice to have the confirmation.
--b.
next prev parent reply other threads:[~2012-10-17 14:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121012211701.GA8301@bitmover.com>
2012-10-12 23:52 ` kernel BUG at /build/buildd/linux-3.2.0/fs/lockd/clntxdr.c:226! Linus Torvalds
2012-10-13 0:21 ` Larry McVoy
2012-10-13 1:02 ` Linus Torvalds
2012-10-13 1:36 ` Jim Rees
2012-10-13 1:45 ` Linus Torvalds
2012-10-13 21:31 ` Daniel Kahn Gillmor
2012-10-13 2:08 ` Boaz Harrosh
2012-10-13 2:28 ` Myklebust, Trond
2012-10-13 2:31 ` Larry McVoy
2012-10-13 2:52 ` Myklebust, Trond
2012-10-13 2:56 ` Larry McVoy
2012-10-13 3:05 ` Myklebust, Trond
2012-10-13 4:42 ` Myklebust, Trond
2012-10-14 1:42 ` Larry McVoy
2012-10-15 0:43 ` Bruce Fields
2012-10-15 4:38 ` Myklebust, Trond
2012-10-15 14:34 ` Larry McVoy
2012-10-15 18:02 ` Bruce Fields
2012-10-15 4:41 ` Myklebust, Trond
2012-10-15 12:11 ` Bruce Fields
2012-10-17 14:00 ` Bruce Fields [this message]
2012-10-14 19:39 ` Bruce Fields
2012-10-14 19:44 ` Linus Torvalds
2012-10-14 20:55 ` Chuck Lever
2012-10-14 21:05 ` Linus Torvalds
2012-10-14 22:32 ` Chuck Lever
2012-10-14 22:54 ` Linus Torvalds
2012-10-13 2:27 ` Boaz Harrosh
2012-10-13 2:30 ` Larry McVoy
2012-10-13 2:32 ` Myklebust, Trond
2012-10-13 2:39 ` Boaz Harrosh
2012-10-13 2:43 ` Larry McVoy
2012-10-14 19:43 ` Bruce Fields
2012-10-15 18:20 ` Boaz Harrosh
2012-10-13 2:37 ` Linus Torvalds
2012-10-15 8:05 George Spelvin
2012-10-15 12:19 ` Myklebust, Trond
2012-10-15 16:02 ` VDR User
2012-10-16 1:48 ` George Spelvin
2012-10-16 1:52 ` Larry McVoy
2012-10-16 3:46 ` Myklebust, Trond
2012-10-16 4:39 ` George Spelvin
2012-10-16 11:17 ` Jim Rees
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=20121017140020.GA25488@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=torvalds@linux-foundation.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