All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: syzbot <syzbot+ce483fd06e2061f44f5d@syzkaller.appspotmail.com>,
	akpm@linux-foundation.org, liam.howlett@oracle.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-usb@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
	Marcello Sylvester Bauer <sylv@sylv.io>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>
Subject: Re: [syzbot] [input?] [usb?] [mm?] INFO: rcu detected stall in vma_link_file
Date: Wed, 16 Oct 2024 09:14:27 +0200	[thread overview]
Message-ID: <2024101602-skintight-crawfish-ebab@gregkh> (raw)
In-Reply-To: <bacc4301-be1a-4f3f-9da3-1543cbf9874c@lucifer.local>

On Wed, Oct 16, 2024 at 08:06:20AM +0100, Lorenzo Stoakes wrote:
> + some people from USB/HID subsystem.
> 
> This is really not looking mm-related, as for a second time we've asked
> syzbot to re-run and for a second time it's not hit any mm-specific code -
> I think this is misattributed - could somebody from the USB/HID side take a
> look?
> 
> It looks to be something that isn't reproduced by a specific C program but
> by a syzkaller USB configuration [0]?

There's a lot of odd usb syzbot issues right now dealing with the dummy
hcd controller, so maybe this is another one of them...

thanks,

greg k-h

  reply	other threads:[~2024-10-16  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 15:02 [syzbot] [input?] [usb?] [mm?] INFO: rcu detected stall in vma_link_file syzbot
2024-10-15  8:44 ` Lorenzo Stoakes
2024-10-15 10:32   ` syzbot
2024-10-15 10:43     ` Lorenzo Stoakes
2024-10-15 20:05 ` Liam R. Howlett
2024-10-15 20:27   ` syzbot
2024-10-16  7:06     ` Lorenzo Stoakes
2024-10-16  7:14       ` Greg Kroah-Hartman [this message]
2024-10-16  8:30         ` Tetsuo Handa

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=2024101602-skintight-crawfish-ebab@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=sylv@sylv.io \
    --cc=syzbot+ce483fd06e2061f44f5d@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.