From: Andrey Konovalov <andreyknvl@gmail.com>
To: Marcello Sylvester Bauer <sylv@sylv.io>
Cc: andrey.konovalov@linux.dev,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Vyukov <dvyukov@google.com>,
Aleksandr Nogikh <nogikh@google.com>,
Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
kasan-dev@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+2388cdaeb6b10f0c13ac@syzkaller.appspotmail.com,
syzbot+17ca2339e34a1d863aad@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: dummy_hcd: execute hrtimer callback in softirq context
Date: Mon, 29 Jul 2024 18:14:30 +0200 [thread overview]
Message-ID: <CA+fCnZcWvtnTrST3PrORdPwmo0m2rrE+S-hWD74ZU_4RD6mSPA@mail.gmail.com> (raw)
In-Reply-To: <baae33f5602d8bcd38b48cd6ea4617c8e17d8650.camel@sylv.io>
On Mon, Jul 29, 2024 at 10:26 AM Marcello Sylvester Bauer <sylv@sylv.io> wrote:
>
> Hi Andrey,
Hi Marcello,
> Thanks for investigating and finding the cause of this problem. I have
> already submitted an identical patch to change the hrtimer to softirq:
> https://lkml.org/lkml/2024/6/26/969
Ah, I missed that, that's great!
> However, your commit messages contain more useful information about the
> problem at hand. So I'm happy to drop my patch in favor of yours.
That's very considerate, thank you. I'll leave this up to Greg - I
don't mind using either patch.
> Btw, the same problem has also been reported by the intel kernel test
> robot. So we should add additional tags to mark this patch as the fix.
>
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes:
> https://lore.kernel.org/oe-lkp/202406141323.413a90d2-lkp@intel.com
> Acked-by: Marcello Sylvester Bauer <sylv@sylv.io>
Let's also add the syzbot reports mentioned in your patch:
Reported-by: syzbot+c793a7eca38803212c61@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=c793a7eca38803212c61
Reported-by: syzbot+1e6e0b916b211bee1bd6@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=1e6e0b916b211bee1bd6
And I also found one more:
Reported-by: syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=edd9fe0d3a65b14588d5
Thank you!
next prev parent reply other threads:[~2024-07-29 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 2:23 andrey.konovalov
2024-07-29 8:25 ` Marcello Sylvester Bauer
2024-07-29 16:14 ` Andrey Konovalov [this message]
2024-07-29 18:01 ` Alan Stern
2024-07-30 13:43 ` Andrey Konovalov
2024-08-09 15:22 ` Alexander Potapenko
2024-08-27 0:02 ` Andrey Konovalov
2024-09-03 7:09 ` Greg Kroah-Hartman
2024-09-04 1:34 ` Andrey Konovalov
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=CA+fCnZcWvtnTrST3PrORdPwmo0m2rrE+S-hWD74ZU_4RD6mSPA@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=nogikh@google.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=sylv@sylv.io \
--cc=syzbot+17ca2339e34a1d863aad@syzkaller.appspotmail.com \
--cc=syzbot+2388cdaeb6b10f0c13ac@syzkaller.appspotmail.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