From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Dexuan Cui To: Jan Kara CC: Pavlos Parissis , Haiyang Zhang , Robert Kolchmeyer , Guillaume Morin , "stable@vger.kernel.org" , "jack@suse.com" , "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mszeredi@redhat.com" , Josh Poulson Subject: RE: kernel panics with 4.14.X versions Date: Fri, 20 Apr 2018 17:43:01 +0000 Message-ID: References: <20180416132550.d25jtdntdvpy55l3@bender.morinfr.org> <20180416144041.t2mt7ugzwqr56ka3@quack2.suse.cz> <9b11cfba-4bdc-8a3e-cd33-2f7e8d513bdf@gmail.com> <20180417121207.cs7eijrndovbplgz@quack2.suse.cz> <9cb08428-66ed-2306-d2f2-ae734863c68d@gmail.com> <20180419202302.vj2eu43hy77g5mv7@quack2.suse.cz> <20180420102136.a637r6eoghxjqhaf@quack2.suse.cz> In-Reply-To: <20180420102136.a637r6eoghxjqhaf@quack2.suse.cz> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: stable-owner@vger.kernel.org List-ID: > From: Jan Kara > Sent: Friday, April 20, 2018 03:22 > On Thu 19-04-18 21:37:25, Dexuan Cui wrote: > > > From: Jan Kara > > > Sent: Thursday, April 19, 2018 13:23 > > > Good news guys, Robert has just spotted a bug which looks like what I= 'd > > > expect can cause your lockups / crashes. I've merged his patch to my = tree > > > and will push it to Linus for -rc3 so eventually it should land in > > > appropriate stable trees as well. If you are too eager to test it out= , it > > > is attached for you to try. > > > > > > Jan Kara > > > > The patch's changelog says "... this behavior results in a kernel panic= ." > > This sounds like a reference to corrupt memory causes a page fault or > > general protection fault. > > > > But what I saw is only a lockup rather than a kernel panic: > > watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [java:87260]" > > > > So I guess what I saw can be a different unresolved issue? >=20 > Actually I don't think so. The list iteration simply went through stray > pointer. That can crash but it can also end in an infinite loop, or it ca= n > just randomly corrupt memory. I've seen all these situations with similar > problems. So the fix is definitely worth trying. >=20 > Jan Kara Thanks for the explanation! It sounds promising! We haven't been able to reproduce the issue by ourselves. If our customer still keeps the setup to reproduce the issue, we'll try to test the patch.=20 -- Dexuan =20