From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F396DC32771 for ; Wed, 17 Aug 2022 18:38:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238036AbiHQSiU (ORCPT ); Wed, 17 Aug 2022 14:38:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237097AbiHQSiT (ORCPT ); Wed, 17 Aug 2022 14:38:19 -0400 Received: from mail.itouring.de (mail.itouring.de [IPv6:2a01:4f8:a0:4463::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E5954C603; Wed, 17 Aug 2022 11:38:18 -0700 (PDT) Received: from tux.applied-asynchrony.com (p5ddd78be.dip0.t-ipconnect.de [93.221.120.190]) by mail.itouring.de (Postfix) with ESMTPSA id 9BD74103762; Wed, 17 Aug 2022 20:38:16 +0200 (CEST) Received: from [192.168.100.221] (hho.applied-asynchrony.com [192.168.100.221]) by tux.applied-asynchrony.com (Postfix) with ESMTP id 654FAF01600; Wed, 17 Aug 2022 20:38:16 +0200 (CEST) Subject: Re: stalling IO regression since linux 5.12, through 5.18 To: Chris Murphy , Nikolay Borisov , Jens Axboe , Jan Kara , Paolo Valente Cc: Linux-RAID , linux-block , linux-kernel , Josef Bacik References: <2220d403-e443-4e60-b7c3-d149e402c13e@www.fastmail.com> <61e5ccda-a527-4fea-9850-91095ffa91c4@www.fastmail.com> <4995baed-c561-421d-ba3e-3a75d6a738a3@www.fastmail.com> <2b8a38fa-f15f-45e8-8caa-61c5f8cd52de@www.fastmail.com> <7c830487-95a6-b008-920b-8bc4a318f10a@applied-asynchrony.com> From: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?= Organization: Applied Asynchrony, Inc. Message-ID: <8a75ee2c-0972-6e14-36e1-053122de7a35@applied-asynchrony.com> Date: Wed, 17 Aug 2022 20:38:16 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On 2022-08-17 20:16, Chris Murphy wrote: > > > On Wed, Aug 17, 2022, at 5:52 AM, Holger Hoffstätte wrote: > >> Chris, just a shot in the dark but can you try the patch from >> >> https://lore.kernel.org/linux-block/20220803121504.212071-1-yukuai1@huaweicloud.com/ >> >> on top of something more recent than 5.12? Ideally 5.19 where it applies >> cleanly. > > > This patch applies cleanly on 5.12.0. I can try newer kernels later, but as the problem so easily reproduces with 5.12 and the problem first appeared there, is why I'm sticking with it. (For sure we prefer to be on 5.19 series.) > > Let me know if I should try it still. I just started running it in 5.19.2 to see if it breaks something; no issues so far but then again I didn't have any problems to begin with and only do peasant I/O load, and no MegaRAID. However if it applies *and builds* on 5.12 I'd just go ahead and see what catches fire. But you need to set the megaraid setting to fail, otherwise we won't be able to see whether this is really a contributing factor, or indeed the other commit that Jan identified. Unfortunately 5.12 is a bit old already and most of the other important fixes to sbitmap.c probably won't apply due to some other blk-mq changes. In any case the plot thickens, so keep going. :) -h