From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43349 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752096AbeDQKdu (ORCPT ); Tue, 17 Apr 2018 06:33:50 -0400 Date: Tue, 17 Apr 2018 12:33:44 +0200 From: Greg KH To: Dexuan Cui Cc: Jan Kara , Guillaume Morin , Haiyang Zhang , Pavlos Parissis , "stable@vger.kernel.org" , "jack@suse.com" , "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mszeredi@redhat.com" Subject: Re: kernel panics with 4.14.X versions Message-ID: <20180417103344.GB8445@kroah.com> References: <20180416132550.d25jtdntdvpy55l3@bender.morinfr.org> <20180416144041.t2mt7ugzwqr56ka3@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Mon, Apr 16, 2018 at 09:10:35PM +0000, Dexuan Cui wrote: > > From: Jan Kara > > 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