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 0980EC0015E for ; Thu, 6 Jul 2023 10:55:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232111AbjGFKzB (ORCPT ); Thu, 6 Jul 2023 06:55:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45138 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232235AbjGFKye (ORCPT ); Thu, 6 Jul 2023 06:54:34 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5C49E1BDB; Thu, 6 Jul 2023 03:54:17 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qHMco-0005gy-HF; Thu, 06 Jul 2023 12:54:14 +0200 Message-ID: <7336b8ea-64bd-d08d-1d85-bf942d5660e2@leemhuis.info> Date: Thu, 6 Jul 2023 12:54:13 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: Fwd: vmalloc error: btrfs-delalloc btrfs_work_helper [btrfs] in kernel 6.3.x To: Forza , Uladzislau Rezki , Bagas Sanjaya Cc: Linux btrfs , Linux Kernel Mailing List , Linux Regressions , Linux Stable , Chris Mason , Josef Bacik , David Sterba , a1bert@atlas.cz References: <20230524091357.GH32559@suse.cz> <2063d59.8f9f4a3a.1892a3ec50f@tnonline.net> Content-Language: en-US, de-DE From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list In-Reply-To: <2063d59.8f9f4a3a.1892a3ec50f@tnonline.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1688640857;1fe2e194; X-HE-SMSGID: 1qHMco-0005gy-HF Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06.07.23 10:08, Forza wrote: >>> On Wed, May 24, 2023 at 11:13:57AM +0200, David Sterba wrote: > [...] > A small update. Thx for this. > I have been able test 6.2.16, all 6.3.x and 6.4.1 and they all show > the same issue. > > I am now trying 6.1.37 since two days and have not been able to > reproduce this issue on any of my virtual qemu/kvm machines. Perhaps > this information is helpful in finding the root cause? That means it's most likely a regression between v6.1..v6.2 (or v6.1..v6.2.16 if we are unlucky) somewhere (from earlier in the thread it sounds like it might not be Btrfs). Which makes we wonder: how long do you usually need to reproduce the issue? If it's not too long it might mean that a bisection is the best way forward, unless some developer sits down and looks closely at the logs. With a bit of luck some dev will do that; but if we are unlucky we likely will need a bisection. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.