From: Greg KH <greg@kroah.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: Jan Kara <jack@suse.cz>, Guillaume Morin <guillaume@morinfr.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
Pavlos Parissis <pavlos.parissis@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"jack@suse.com" <jack@suse.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mszeredi@redhat.com" <mszeredi@redhat.com>
Subject: Re: kernel panics with 4.14.X versions
Date: Tue, 17 Apr 2018 12:33:44 +0200 [thread overview]
Message-ID: <20180417103344.GB8445@kroah.com> (raw)
In-Reply-To: <KL1P15301MB0006B378757EC8F6B4D87BBBBFB00@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
On Mon, Apr 16, 2018 at 09:10:35PM +0000, Dexuan Cui wrote:
> > From: Jan Kara <jack@suse.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
next prev parent reply other threads:[~2018-04-17 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180416132550.d25jtdntdvpy55l3@bender.morinfr.org>
2018-04-16 14:40 ` kernel panics with 4.14.X versions Jan Kara
2018-04-16 16:06 ` Guillaume Morin
2018-04-16 21:10 ` Dexuan Cui
2018-04-17 10:33 ` Greg KH [this message]
2018-04-17 11:48 ` Amir Goldstein
2018-04-17 12:03 ` Jan Kara
2018-04-17 17:42 ` Dexuan Cui
2018-04-16 23:31 ` Pavlos Parissis
2018-04-17 11:18 ` Pavlos Parissis
2018-04-17 12:04 ` Jan Kara
2018-04-17 12:12 ` Jan Kara
2018-04-18 8:32 ` Pavlos Parissis
2018-04-19 20:23 ` Jan Kara
2018-04-19 21:16 ` Pavlos Parissis
2018-04-19 21:24 ` Robert Kolchmeyer
2018-04-19 21:37 ` Dexuan Cui
2018-04-20 10:21 ` Jan Kara
2018-04-20 17:43 ` Dexuan Cui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180417103344.GB8445@kroah.com \
--to=greg@kroah.com \
--cc=decui@microsoft.com \
--cc=guillaume@morinfr.org \
--cc=haiyangz@microsoft.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=pavlos.parissis@gmail.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).