linux-kernel - Re: kernel 4.14.x crash around fsnotify_mark

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] [day] [month] [year] [list]

Message-ID: <20180417155801.y4boo2nnoznn6sg6@quack2.suse.cz>
Date:   Tue, 17 Apr 2018 17:58:01 +0200
From:   Jan Kara <jack@...e.cz>
To:     Pavlos Parissis <pavlos.parissis@...il.com>
Cc:     Jan Kara <jack@...e.cz>, mszeredi@...hat.com, amir73il@...il.com,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: kernel 4.14.x crash around fsnotify_mark_connector

On Tue 17-04-18 16:15:07, Pavlos Parissis wrote:
> On 17/04/2018 04:02 μμ, Jan Kara wrote:
> > On Tue 17-04-18 12:39:32, Pavlos Parissis wrote:
> >> In one of our production servers where we run kernel version 4.14.32, I noticed
> >> the following:
> > 
> > OK, I was looking into this for some time and couldn't find a problem in
> > 4.14.32 code. Can you try running a kernel with CONFIG_DEBUG_SLAB and
> > CONFIG_DEBUG_PAGEALLOC enabled to hopefully catch the problem earlier?
> > Thanks!
> > 
> 
> I can certainly do that, but I can't reproduce that specific crash. So,
> it may take days before we get a similar crash. Having said that, the
> soft lockup issue, which I mentioned in another thread, happens once per
> day, so I hope running a kernel with those debug settings will help you.

Yes, the hope is debug checks will trigger faster than the actual data
corruption (or softlockup) you've hit.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR