lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2d47b6c-3420-4785-8e04-e5f217d09a46@leemhuis.info>
Date:   Thu, 7 Dec 2023 14:58:13 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Genes Lists <lists@...ience.com>, snitzer@...nel.org,
        song@...nel.org, yukuai3@...wei.com, axboe@...nel.dk,
        mpatocka@...hat.com, heinzm@...hat.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux RAID <linux-raid@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>
Cc:     Bhanu Victor DiCara <00bvd0+linux@...il.com>,
        Xiao Ni <xni@...hat.com>,
        Guoqing Jiang <guoqing.jiang@...ux.dev>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: md raid6 oops in 6.6.4 stable

On 07.12.23 14:30, Bagas Sanjaya wrote:
> On Thu, Dec 07, 2023 at 08:10:04AM -0500, Genes Lists wrote:
>> I have not had chance to git bisect this but since it happened in stable I
>> thought it was important to share sooner than later.
>>
>> One possibly relevant commit between 6.6.3 and 6.6.4 could be:
>>
>>   commit 2c975b0b8b11f1ffb1ed538609e2c89d8abf800e
>>   Author: Song Liu <song@...nel.org>
>>   Date:   Fri Nov 17 15:56:30 2023 -0800
>>
>>     md: fix bi_status reporting in md_end_clone_io
>>
>> log attached shows page_fault_oops.
>> Machine was up for 3 days before crash happened.
> 
> Can you confirm that culprit by bisection?

Bagas, I know you are trying to help, but sorry, I'd say this is not
helpful at all -- any maybe even harmful.

>From the quoted texts it's pretty clear that the reporter knows that a
bisection would be helpful, but currently is unable to perform one --
and even states reasons for reporting it without having it bisected. So
your message afaics doesn't bring anything new to the table; and I might
be wrong with that, but I fear some people in a situation like this
might even be offended by a reply like that, as it states something
already obvious.

Ciao, Thorsten

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ