[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <KL1P15301MB0006B378757EC8F6B4D87BBBBFB00@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
Date: Mon, 16 Apr 2018 21:10:35 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Jan Kara <jack@...e.cz>, Guillaume Morin <guillaume@...infr.org>
CC: 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
> 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
Thanks,
-- Dexuan
Powered by blists - more mailing lists