linux-kernel - Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in __dabt

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: <CANiq72=vMydenfkxQx4X7kYvHD0cHzNK19xxxqow3WcLStsdRA@mail.gmail.com>
Date:   Wed, 26 Apr 2023 12:29:55 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzkaller@...glegroups.com, alex.gaynor@...il.com,
        andriy.shevchenko@...ux.intel.com, bjorn3_gh@...tonmail.com,
        boqun.feng@...il.com, bpf@...r.kernel.org, gary@...yguo.net,
        linux-kernel@...r.kernel.org, linux@...musvillemoes.dk,
        ojeda@...nel.org, pmladek@...e.com, rostedt@...dmis.org,
        rust-for-linux@...r.kernel.org, senozhatsky@...omium.org,
        syzkaller-bugs@...glegroups.com, wedsonaf@...il.com,
        Joe Perches <joe@...ches.com>
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL
 pointer dereference in __dabt_svc

On Wed, Apr 26, 2023 at 12:12 PM Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
> In which of the dozens of kernel testing systems? ;)
> And also in heads of thousands of kernel developers and users?
> All of them use get_maintainer.pl.

I am aware, but `get_maintainer.pl` is fine as it is -- we still want
to know about things that touch things that mention Rust in general,
so that we can possibly be helpful to others, especially early on.

However, if a bot is testing the kernel with Rust actually disabled at
runtime, what I am saying is that the chance that it has something to
do with Rust is quite low, especially if matched via `K:` rather than
`F:`. Thus my request.

Now, it could be nice to have some logic like that in
`get_maintainer.pl` encoded for all bots to filter things out based on
the kernel config and the type of match; but otherwise, yes, the bots
would need to add the logic.

Cc'ing Joe in case this is already possible in `get_maintainer.pl` or
whether there could be a better approach.

Cheers,
Miguel