From: Eric Biggers <ebiggers@kernel.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Marco Elver <elver@google.com>,
Theodore Ts'o <tytso@mit.edu>, Hillf Danton <hdanton@sina.com>,
Matthew Wilcox <willy@infradead.org>,
syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Thu, 29 Dec 2022 13:17:31 -0800 [thread overview]
Message-ID: <Y64D69VTnJEQuHwT@sol.localdomain> (raw)
In-Reply-To: <CANp29Y4x8zoXW0z-HarX3xZ6o8OHzWnGyHw8+JGsbLJKDWUgGA@mail.gmail.com>
On Fri, Dec 16, 2022 at 04:48:34PM +0100, 'Aleksandr Nogikh' via syzkaller-bugs wrote:
>
> Thanks for the feedback, and we regret the inconvenience this may have caused.
>
> We've deployed a simple short term solution to the immediate issue:
> syzbot will extract the involved filesystems from reproducers and use
> this information to construct the email subject line and Cc the
> related people/mailing lists. This should take effect starting next
> week.
>
> That being said, in response to the original feedback we have already
> been planning comprehensive improvements to the subsystem selection
> process that will support more than just filesystems. But
> unfortunately, this is going to take longer to become available.
>
Thanks Aleksandr. From what I can see, the fix is working for new filesystem
bugs: the filesystem(s) involved get added to the title and the recipients.
One question: what happens to all the open bugs, like this one ("WARNING in
do_mkdirat") that were reported before the syzbot fix? Are they going to be
re-reported correctly? Perhaps any bug whose reproducer includes
"syz_mount_image" and was reported before the date of this fix should be
invalidated more aggressively than usual, so that it can be re-reported?
- Eric
next prev parent reply other threads:[~2022-12-29 21:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221211002908.2210-1-hdanton@sina.com>
[not found] ` <00000000000025ff8d05ef842be6@google.com>
[not found] ` <Y5VGCefLZmrOyd0Z@ZenIV>
2022-12-11 7:56 ` [syzbot] WARNING in do_mkdirat Hillf Danton
2022-12-11 8:39 ` Al Viro
2022-12-11 10:22 ` Hillf Danton
2022-12-11 15:46 ` Matthew Wilcox
2022-12-11 20:54 ` Al Viro
2022-12-12 3:29 ` Hillf Danton
2022-12-12 18:58 ` Theodore Ts'o
2022-12-12 19:29 ` Marco Elver
2022-12-13 1:44 ` Al Viro
2022-12-13 2:25 ` Hillf Danton
2022-12-16 15:48 ` Aleksandr Nogikh
2022-12-29 21:17 ` Eric Biggers [this message]
2022-12-31 16:57 ` Theodore Ts'o
2022-12-31 17:03 ` Randy Dunlap
2023-01-03 13:36 ` Aleksandr Nogikh
2022-12-13 1:47 ` Hillf Danton
2022-12-13 3:36 ` Al Viro
2022-12-13 4:12 ` Hillf Danton
2022-12-13 11:05 ` Alexander Potapenko
[not found] <00000000000064d06705eeed9b4e@google.com>
2022-12-04 1:04 ` Hillf Danton
2022-12-09 19:50 ` syzbot
2022-12-09 19:57 ` Matthew Wilcox
2022-12-10 18:06 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y64D69VTnJEQuHwT@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=elver@google.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nogikh@google.com \
--cc=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).