linux-kernel - Re: [NFSv4.1] 6ae373394c4: kernel boot crash

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: <20150207043141.GA4394@wfg-t540p.sh.intel.com>
Date:	Fri, 6 Feb 2015 20:31:41 -0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Trond Myklebust <trond.myklebust@...marydata.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, LKP <lkp@...org>
Subject: Re: [NFSv4.1] 6ae373394c4: kernel boot crash

Hi Trond,

On Fri, Feb 06, 2015 at 10:43:34PM -0500, Trond Myklebust wrote:
> On Fri, Feb 6, 2015 at 9:45 PM, Fengguang Wu <fengguang.wu@...el.com> wrote:
> >
> > Hi Trond,
> >
> > We noticed the below kernel crash on
> >
> > git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
> > commit 6ae373394c4257bad562817aa60464ff7fe8f9c4 ("NFSv4.1: Ask for no delegation on OPEN if using O_DIRECT")
> >
> >
> > testbox/testcase/testparams: vm-vp-quantal-x86_64/boot/1
> >
> > 0e3b137fbf0f4ab9  6ae373394c4257bad562817aa6
> > ----------------  --------------------------
> >        fail:runs  %reproduction    fail:runs
> >            |             |             |
> >            :100          4%           2:46    dmesg.BUG:kernel_test_crashed
> >
> > The last dmesg lines before the kernel crash are
> >
> > [    0.274266] NET: Registered protocol family 1
> > [    0.275236] RPC: Registered named UNIX socket transport module.
> > [    0.276123] RPC: Registered udp transport module.
> > [    0.276860] RPC: Registered tcp transport module.
> > [    0.277617] RPC: Registered tcp NFSv4.1 backchannel transport module
> >
> > Thanks,
> > Fengguang
> 
> 
> Hi Fengguang,
> 
> I'm trying to reproduce this issue, but so far no luck. Do you have
> any details on the test itself that you could share with me?

It looks like a false report, sorry!  The real crash dmesg is much
longer and it ends here:

[   14.605487] i6300esb: Unexpected close, not stopping watchdog!

Which is not relevant to the NFS change at all.

The dmesg I looked at happen to be truncated (perhaps by email server)
exactly at a NFS line, which treats me to believe it's a good bisect.

Cheers,
Fengguang
--
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/