Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 17 Apr 2018 17:58:01 +0200
From:   Jan Kara <jack@suse.cz>
To:     Pavlos Parissis <pavlos.parissis@gmail.com>
Cc:     Jan Kara <jack@suse.cz>, mszeredi@redhat.com, amir73il@gmail.com,
        linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: kernel 4.14.x crash around fsnotify_mark_connector
Message-ID: <20180417155801.y4boo2nnoznn6sg6@quack2.suse.cz>
References: <e7323798-3175-3d27-fdd1-349f1422cb26@gmail.com>
 <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>
 <3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com>
User-Agent: NeoMutt/20170421 (1.8.2)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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@suse.com>
SUSE Labs, CR