[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c81d455-a4f2-4173-be72-9d77728378c1@rowland.harvard.edu>
Date: Fri, 31 Oct 2025 10:13:45 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: vsshingne <vaibhavshingne66@...il.com>, skhan@...uxfoundation.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: core: prevent double URB enqueue causing list
corruption
On Fri, Oct 31, 2025 at 02:59:07PM +0100, Greg KH wrote:
> On Fri, Oct 31, 2025 at 07:17:39PM +0530, vsshingne wrote:
> > Prevents the same URB from being enqueued twice on the same endpoint,
> > which could lead to list corruption detected by list_debug.c.
> >
> > This was observed in syzbot reports where URBs were re-submitted
> > before completion, triggering 'list_add double add' errors.
> >
> > Adding a check to return -EEXIST if the URB is already on a queue
> > prevents this corruption.
>
> This text makes no sense at all, it does not describe what this patch
> does in any way. Please do not use AI to generate patches.
In fact, the patch doesn't do _anything_ (except maybe change some
whitespace). And it does not apply to any recent kernel source.
Alan Stern
Powered by blists - more mailing lists