linux-kernel - Re: kernel panics with 4.14.X versions

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: <20180417103344.GB8445@kroah.com>
Date:   Tue, 17 Apr 2018 12:33:44 +0200
From:   Greg KH <greg@...ah.com>
To:     Dexuan Cui <decui@...rosoft.com>
Cc:     Jan Kara <jack@...e.cz>, Guillaume Morin <guillaume@...infr.org>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Pavlos Parissis <pavlos.parissis@...il.com>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "jack@...e.com" <jack@...e.com>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "mszeredi@...hat.com" <mszeredi@...hat.com>
Subject: Re: kernel panics with 4.14.X versions

On Mon, Apr 16, 2018 at 09:10:35PM +0000, Dexuan Cui wrote:
> > From: Jan Kara <jack@...e.cz>
> > Sent: Monday, April 16, 2018 07:41
> > ...
> > How easily can you hit this? Are you able to run debug kernels / inspect
> > crash dumps when the issue occurs? Also testing with the latest mainline
> > kernel (4.16) would be welcome whether this isn't just an issue with the
> > backport of fsnotify fixes from Miklos.
> 
> It's not easy for us to reproduce the fsnotify() lockup issue, and actually
> we still don't have an easy & reliable way to reproduce it.
> 
> According to our tests, v4.16 doesn't have the issue.
> And v4.15 doesn't have the issue either, if I recall correctly.
> I only know the issue happens to v4.14.x and 4.13.x kernels

Any chance to run 'git bisect' between 4.14 and 4.15 to find the fix?

thanks,

greg k-h