linux-kernel - Re: [PATCH] usb: gadget: dummy_hcd: execute hrtimer callback in softirq context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+fCnZebutAq7dfzutMhp-KO0vwM67PC7r4FRHPUcY1eg5rW3Q@mail.gmail.com>
Date: Tue, 30 Jul 2024 15:43:34 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Marcello Sylvester Bauer <sylv@...v.io>, andrey.konovalov@...ux.dev, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Dmitry Vyukov <dvyukov@...gle.com>, 
	Aleksandr Nogikh <nogikh@...gle.com>, Marco Elver <elver@...gle.com>, 
	Alexander Potapenko <glider@...gle.com>, kasan-dev@...glegroups.com, 
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org, linux-usb@...r.kernel.org, 
	linux-kernel@...r.kernel.org, 
	syzbot+2388cdaeb6b10f0c13ac@...kaller.appspotmail.com, 
	syzbot+17ca2339e34a1d863aad@...kaller.appspotmail.com, stable@...r.kernel.org
Subject: Re: [PATCH] usb: gadget: dummy_hcd: execute hrtimer callback in
 softirq context

On Mon, Jul 29, 2024 at 8:01 PM Alan Stern <stern@...land.harvard.edu> wrote:
>
> > And I also found one more:
> >
> > Reported-by: syzbot+edd9fe0d3a65b14588d5@...kaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=edd9fe0d3a65b14588d5
>
> You need to be careful about claiming that this patch will fix those bug
> reports.  At least one of them (the last one above) still fails with the
> patch applied.  See:
>
> https://lore.kernel.org/linux-usb/ade15714-6aa3-4988-8b45-719fc9d74727@rowland.harvard.edu/
>
> and the following response.

Ah, right, that one is something else, so let's not add those last
Reported-by/Closes.

However, that crash was bisected to the same guilty patch, so the
issue is somehow related. Even if we were to mark it as to be fixed
with the patch I sent, this wouldn't be critical: syzbot would just
rereport it, and with fresher stack traces.

Thank you!