From: Bruce Fields <bfields@fieldses.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Dmitry Vyukov <dvyukov@google.com>, NeilBrown <neilb@suse.com>,
syzbot <syzbot+a4a3d526b4157113ec6a@syzkaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: KASAN: use-after-free Read in locks_delete_block
Date: Sat, 17 Nov 2018 09:03:56 -0500 [thread overview]
Message-ID: <20181117140356.GA29895@fieldses.org> (raw)
In-Reply-To: <c76712278e2d7f5c4c8cfbab687a941bf493b0c6.camel@kernel.org>
On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote:
> Thanks for the explanation, Dmitry. I've added the tag to the patch in
> my tree. It should show up in linux-next soon.
>
> I still find it a little misleading to say that syzbot reported a bug
> when it actually found a bug inside an earlier version of the patch, but
> I'll just learn to get over it.
The usual tag for someone that found a bug in an earlier version of a
patch would be Reviewed-by:. Is there any reason we can't use that
here? The "syzbot+..." email should be enough on its own, I can't see a
reason why their scripts would need to require a particular tag. Or
maybe we could use Tested-by:, or some other tag made up for this case?
I do worry that someone who sees "Reported-by:..." might for example
mistakenly assume that it would help to backport that patch if they see
a similar-looking oops.
--b.
next prev parent reply other threads:[~2018-11-17 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 20:34 KASAN: use-after-free Read in locks_delete_block syzbot
2018-11-13 10:37 ` Jeff Layton
2018-11-13 20:40 ` NeilBrown
2018-11-14 10:36 ` Jeff Layton
2018-11-15 22:45 ` Dmitry Vyukov
2018-11-15 23:41 ` NeilBrown
2018-11-16 20:37 ` Dmitry Vyukov
2018-11-17 13:33 ` Jeff Layton
2018-11-17 14:03 ` Bruce Fields [this message]
2018-11-20 6:57 ` Dmitry Vyukov
2018-11-20 11:08 ` Jeff Layton
2018-11-20 13:23 ` Dmitry Vyukov
2018-11-13 19:58 ` 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=20181117140356.GA29895@fieldses.org \
--to=bfields@fieldses.org \
--cc=dvyukov@google.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=syzbot+a4a3d526b4157113ec6a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).