public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5f996b83575ef4058638@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	 linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in raw_ioctl
Date: Tue, 11 Jun 2024 11:03:03 -0700	[thread overview]
Message-ID: <000000000000babbf8061aa113df@google.com> (raw)
In-Reply-To: <684687e4-8be4-42ee-a125-8ef9acc3fec9@rowland.harvard.edu>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+5f996b83575ef4058638@syzkaller.appspotmail.com

Tested on:

commit:         8867bbd4 mm: arm64: Fix the out-of-bounds issue in con..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14e092de980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3b4350cf56c61c80
dashboard link: https://syzkaller.appspot.com/bug?extid=5f996b83575ef4058638
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=137c697e980000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-06-11 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  9:02 [syzbot] [usb?] INFO: rcu detected stall in raw_ioctl syzbot
2024-06-09  0:28 ` syzbot
2024-06-09  1:57   ` Alan Stern
2024-06-09  4:41     ` syzbot
2024-06-10 17:24       ` Alan Stern
2024-06-10 17:58         ` syzbot
2024-06-10 19:42           ` Alan Stern
2024-06-10 20:12             ` syzbot
2024-06-11 15:20               ` Alan Stern
2024-06-11 15:53                 ` syzbot
2024-06-11 17:26                   ` Alan Stern
2024-06-11 18:03                     ` syzbot [this message]
2024-06-12 14:37                       ` Alan Stern
2024-06-13  1:23                         ` Alan Stern
2024-06-13  3:40                           ` syzbot

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=000000000000babbf8061aa113df@google.com \
    --to=syzbot+5f996b83575ef4058638@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.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