linux-kernel - Re: [syzbot] kernel panic: stack is corrupted in writeback_single

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: <CANpmjNPXPoguZAS9L0XPey4=XX1NSTDEB_mA7j7t10FThefuUQ@mail.gmail.com>
Date:   Fri, 30 Sep 2022 16:09:32 +0200
From:   Marco Elver <elver@...gle.com>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     syzbot <syzbot+84b7b87a6430a152c1f4@...kaller.appspotmail.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com,
        Hrutvik Kanabar <hrutvik@...gle.com>,
        Aleksandr Nogikh <nogikh@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [syzbot] kernel panic: stack is corrupted in writeback_single_inode

On Thu, 29 Sept 2022 at 22:50, Al Viro <viro@...iv.linux.org.uk> wrote:
[...]
> ... and you _still_ have not bothered to Cc ntfs maintainers.
> Once more, with feeling:
>         If you are fuzzing something (ntfs, in this case), the people most
> interested in your report are the maintainers of the code in question.
> You know that from the moment you put the test together.  No matter where
> exactly the oops gets triggered, what it looks like, etc.

Apologies - we just updated syzbot to do better, so for bugs like this
it should now pick appropriate sub-filesystem maintainers.

Thanks,
~~ Marco