Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <0000000000008ea2da05e979435f@google.com> <0000000000000f962805e9d6ae62@google.com>
 <YzYFIK/jFiN6WEzT@ZenIV>
In-Reply-To: <YzYFIK/jFiN6WEzT@ZenIV>
From:   Marco Elver <elver@google.com>
Date:   Fri, 30 Sep 2022 16:09:32 +0200
Message-ID: <CANpmjNPXPoguZAS9L0XPey4=XX1NSTDEB_mA7j7t10FThefuUQ@mail.gmail.com>
Subject: Re: [syzbot] kernel panic: stack is corrupted in writeback_single_inode
To:     Al Viro <viro@zeniv.linux.org.uk>
Cc:     syzbot <syzbot+84b7b87a6430a152c1f4@syzkaller.appspotmail.com>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        syzkaller-bugs@googlegroups.com,
        Hrutvik Kanabar <hrutvik@google.com>,
        Aleksandr Nogikh <nogikh@google.com>,
        Dmitry Vyukov <dvyukov@google.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 29 Sept 2022 at 22:50, Al Viro <viro@zeniv.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