From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756054AbbJIIFX (ORCPT ); Fri, 9 Oct 2015 04:05:23 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:34443 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756015AbbJIIFN (ORCPT ); Fri, 9 Oct 2015 04:05:13 -0400 Subject: Re: Hard lockup in ext4_finish_bio To: John Stoffel References: <56165784.60206@kyup.com> <22038.32498.570540.37956@quad.stoffel.home> <56167F93.8010408@kyup.com> <22038.48242.126925.476449@quad.stoffel.home> Cc: "Linux-Kernel@Vger. Kernel. Org" , linux-ext4 , "Theodore Ts'o" , Marian Marinov , Jan Kara From: Nikolay Borisov Message-ID: <56177536.10501@kyup.com> Date: Fri, 9 Oct 2015 11:05:10 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <22038.48242.126925.476449@quad.stoffel.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/08/2015 09:56 PM, John Stoffel wrote: >>>>>> "Nikolay" == Nikolay Borisov writes: > > Nikolay> On 10/08/2015 05:34 PM, John Stoffel wrote: >>> Great bug report, but you're missing the info on which kernel >>> you're > > Nikolay> This is on 3.12.47 (self compiled). It was evident on my > Nikolay> initial post, but I did forget to mention that in the > Nikolay> reply. Also, I suspect even current kernel are susceptible to > Nikolay> this since the locking in question hasn't changed. > > Hi Nikolay, must have missed it. I looked quickly, but didn't find > it. Since it's such an older kernel release, it might be best if you > upgrade to the latest version and try to re-create the lock if at all > possible. The relevant code hasn't changed. I've already posted RFC patches. You can find the thread here: http://thread.gmane.org/gmane.linux.kernel/2056996 > > What kind of workload are you running on there? And if you have more > details on the hardware, that might help as well. > > John >