From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Khazhy Kumykov <khazhy@google.com>,
syzbot <syzbot+18996170f8096c6174d0@syzkaller.appspotmail.com>,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: slab-out-of-bounds Read in read_descriptors (3)
Date: Thu, 3 Aug 2023 08:34:02 +0200 [thread overview]
Message-ID: <2023080309-economist-each-6f51@gregkh> (raw)
In-Reply-To: <58e8a28b-ab24-4449-9072-e0fb7ed39196@rowland.harvard.edu>
On Wed, Aug 02, 2023 at 04:00:28PM -0400, Alan Stern wrote:
> Greg:
>
> I'm putting together a series of three patches to deal with this
> problem. The first two do some preparatory work, and the bug found by
> syzbot actually gets fixed by the third patch.
>
> In view of this, how should I tag the patches? They should all get into
> the -stable trees eventually, but only the third one really deserves a
> Fixes: or Reported-by: tag.
>
> What's your advice?
Sounds correct, just tag the last one with a reported-by: Same for the
fixes: tag, we deal with this in the stable tree a lot, and can figure
out the dependancies like this for patch series.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-03 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 2:55 [syzbot] [usb?] KASAN: slab-out-of-bounds Read in read_descriptors (3) syzbot
2023-07-21 18:10 ` Khazhy Kumykov
2023-07-21 18:23 ` Khazhy Kumykov
2023-07-21 18:56 ` Alan Stern
2023-07-21 22:40 ` Khazhy Kumykov
2023-07-23 2:01 ` Alan Stern
2023-07-23 2:21 ` syzbot
2023-07-25 19:26 ` Alan Stern
2023-07-25 20:42 ` Khazhy Kumykov
2023-07-25 21:30 ` Alan Stern
2023-07-25 21:46 ` Khazhy Kumykov
2023-07-26 4:00 ` Greg KH
2023-08-02 20:00 ` Alan Stern
2023-08-03 6:34 ` Greg KH [this message]
2023-07-25 20:54 ` 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=2023080309-economist-each-6f51@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=khazhy@google.com \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+18996170f8096c6174d0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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