Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Message-ID: <17bd838f-12a0-43c2-a45c-46021083170b@leemhuis.info>
Date:   Mon, 4 Dec 2023 13:10:46 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: block/badblocks.c warning in 6.7-rc2
Content-Language: en-US, de-DE
To:     Coly Li <colyli@suse.de>, Bagas Sanjaya <bagasdotme@gmail.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Regressions <regressions@lists.linux.dev>,
        Linux Block Devices <linux-block@vger.kernel.org>,
        Linux RAID <linux-raid@vger.kernel.org>,
        Linux bcachefs <linux-bcachefs@vger.kernel.org>,
        Xiao Ni <xni@redhat.com>, Geliang Tang <geliang.tang@suse.com>,
        Jens Axboe <axboe@kernel.dk>, Song Liu <song@kernel.org>,
        Kent Overstreet <kent.overstreet@linux.dev>,
        Janpieter Sollie <janpieter.sollie@edpnet.be>
References: <562a2442-d098-4972-baa1-5a843e06b180@gmail.com>
 <C8305655-3749-411B-A696-E07E95882215@suse.de>
From:   "Linux regression tracking #update (Thorsten Leemhuis)" 
        <regressions@leemhuis.info>
Reply-To: Linux regressions mailing list <regressions@lists.linux.dev>
In-Reply-To: <C8305655-3749-411B-A696-E07E95882215@suse.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 29.11.23 09:08, Coly Li wrote:
>> 2023年11月29日 07:47，Bagas Sanjaya <bagasdotme@gmail.com> 写道：
>>
>> I notice a regression report that is rather well-handled on Bugzilla [1].
>> Quoting from it:
>>
>>>
>>> when booting from 6.7-rc2, compiled with clang, I get this warning on one of my 3 bcachefs volumes:
>>> WARNING: CPU: 3 PID: 712 at block/badblocks.c:1284 badblocks_check (block/badblocks.c:1284) 
>>> The reason why isn't clear, but the stack trace points to an error in md error handling.
>>> This bug didn't happen in 6.6
>>> there are 3 commits in 6.7-rc2 which may cause them,
>>> in attachment:
>>> - decoded stacktrace of dmesg
>>> - kernel .config
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218184
> 
> It seems the improved bad blocks code caught a zero-size bio request
> from upper layer, this improper behavior was silently neglected before.
> It might be too early or simple to decide this is a regression,

Well, it's often better to add an issue to the tracking even if there is
a chance that it's not a real regression, as the issue might otherwise
fall through the cracks. But given...

> especially Janpieter closes the report for now.

...this I agree that this is likely not worth tracking, hence:

#regzbot inconclusive: maybe not a regression and report can not
reproduce it anymore

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
That page also explains what to do if mails like this annoy you.