linux-kernel - Re: Bug 215605 - [5.14 regression] BUG: unable to handle page fault while running badblocks (fsck.ext4 -c) on a raid5 md array

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] [day] [month] [year] [list]

Message-ID: <CAPhsuW5vn7gepzFSn3a1p6SqzFHdvf0N7-U7EoAC7YTnF8wiFQ@mail.gmail.com>
Date:   Thu, 17 Mar 2022 15:41:32 -0700
From:   Song Liu <song@...nel.org>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Dominik Mierzejewski <dominik@...ysector.net>,
        linux-raid <linux-raid@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        Jens Axboe <axboe@...nel.dk>
Subject: Re: Bug 215605 - [5.14 regression] BUG: unable to handle page fault
 while running badblocks (fsck.ext4 -c) on a raid5 md array

On Thu, Mar 17, 2022 at 6:14 AM Thorsten Leemhuis
<regressions@...mhuis.info> wrote:
>
> Hi, this is your Linux kernel regression tracker. Top-posting for once,
> to make this easily accessible to everyone.
>
> Song, two weeks ago you said you would try to reproduce this. Any
> success? Or was the discussion moved somewhere else and I just missed it?
>

I haven't got luck to reproduce the issue yet. I will keep trying and
update when
there is progress.

Thanks,
Song

> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.
>