linux-kernel - Re: [NFSv4] 2.6.23-rc4 oops in nfs4_cb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6278d2220709100739lbb75a6duf34e62de80f71765@mail.gmail.com>
Date:	Mon, 10 Sep 2007 15:39:23 +0100
From:	"Daniel J Blueman" <daniel.blueman@...il.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	"Trond Myklebust" <Trond.Myklebust@...app.com>,
	nfsv4@...ux-nfs.org, "Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [NFSv4] 2.6.23-rc4 oops in nfs4_cb_recall...

On 09/09/2007, J. Bruce Fields <bfields@...ldses.org> wrote:
> > When accessing a directory inode from a single other client, NFSv4
> > callbacks catastrophically failed [1] on the NFS server with
> > 2.6.23-rc4 (unpatched); clients are both 2.6.22 (Ubuntu Gutsy build).
> > Seems not easy to reproduce, since this kernel was running smoothly
> > for 7 days on the server.
> >
> > What information will help track this down, or is there a known
> > failure mechanism?
>
> I haven't seen that before.
>
> > I can map stack frames to source lines with objdump, if that helps.

> If it's still easy, it might help to figure out exactly where in
> xprt_reserve() it died, and why.  If we've got some race that can lead
> to freeing the client while a callback is in progress, then perhaps this
> is on the first dereference of xprt?

I've raised the bug report into bugzilla, added other observations
from a second occurrence recently and disassembled xprt_reserve with
line numbers.

http://bugzilla.kernel.org/show_bug.cgi?id=9003

Ping me for any more detail/info and thanks!

Daniel
-- 
Daniel J Blueman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/