Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: syzbot <syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com>,
	asml.silence@gmail.com, axboe@kernel.dk, brauner@kernel.org,
	io-uring@vger.kernel.org, jack@suse.cz, kartikey406@gmail.com,
	kees@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, mjguzik@gmail.com, nogikh@google.com,
	syzbot@kernel.org, syzbot@lists.linux.dev,
	syzkaller-bugs@googlegroups.com,
	syzkaller-upstream-moderation@googlegroups.com,
	torvalds@ppc970.osdl.org, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Read in ep_open
Date: Wed, 19 Aug 2026 14:26:54 +0200	[thread overview]
Message-ID: <2026081906-possible-seltzer-6db9@gregkh> (raw)
In-Reply-To: <6232f9c1-8b07-42b9-8660-ad514702ae1c@rowland.harvard.edu>

On Tue, Aug 18, 2026 at 11:37:16AM -0400, Alan Stern wrote:
> On Tue, Aug 18, 2026 at 09:42:34AM +0200, Greg KH wrote:
> > On Mon, Aug 17, 2026 at 02:14:17PM -0400, Alan Stern wrote:
> > > Greg:
> > > 
> > > Has this patch ever been queued?
> > > 
> > > https://lore.kernel.org/linux-usb/ee41fbfd-f368-4a06-95d6-ae9b4267fd82@mail.kernel.org/
> > 
> > No because it looks like there are competing patches here as you point
> > out.
> > 
> > > Looks like you can add syzbot's Tested-by: tag, as well as my Acked-by:.
> > > 
> > > Note that a different patch to fix the same problem was submitted here:
> > > 
> > > https://lore.kernel.org/linux-usb/20260731230603.4637-1-kartikey406@gmail.com/
> > > 
> > > IMO the first patch above is superior.
> > 
> > So Aleksandr's patch should be applied and not Deepanshu's?
> 
> That's my recommendation.  You can take a quick look at the two patches 
> and see what you think.
> 
> We haven't heard back from Deepanshu.  Aleksandr doesn't seem to have 
> strong feelings either way.

Aleksandr's patch is much more simple, and relies on the reference
counting logic in the inode itself, instead of "hand rolling" it like
Deepanshu's does.

I'll take it after -rc1 is out.  As this is a syzbot-only type of thing,
there's no rush here.

thanks,

greg k-h

      reply	other threads:[~2026-08-19 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  1:28 [syzbot] [usb?] KASAN: slab-use-after-free Read in ep_open syzbot
2026-08-17 13:42 ` syzbot
2026-08-17 15:04   ` Jens Axboe
2026-08-17 15:45     ` Alan Stern
2026-08-17 16:38       ` syzbot
2026-08-17 18:14         ` Alan Stern
2026-08-18  7:42           ` Greg KH
2026-08-18 15:37             ` Alan Stern
2026-08-19 12:26               ` Greg KH [this message]

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=2026081906-possible-seltzer-6db9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=kartikey406@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=nogikh@google.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com \
    --cc=syzbot@kernel.org \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller-upstream-moderation@googlegroups.com \
    --cc=torvalds@ppc970.osdl.org \
    --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