From: Kees Cook <keescook@chromium.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Zhang, Qiang1" <qiang1.zhang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
syzbot <syzbot+9bb26e7c5e8e4fa7e641@syzkaller.appspotmail.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] WARNING in exit_tasks_rcu_finish
Date: Mon, 13 Jun 2022 16:42:07 -0700 [thread overview]
Message-ID: <202206131639.DBA0A8D@keescook> (raw)
In-Reply-To: <20220613233753.GK1790663@paulmck-ThinkPad-P17-Gen-1>
On Mon, Jun 13, 2022 at 10:36:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+9bb26e7c5e8e4fa7e641@syzkaller.appspotmail.com
Looks like the patch solved the reproducer. :)
> Tested on:
>
> commit: 6d0c8068 Add linux-next specific files for 20220610
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git next-20220610
> console output: https://syzkaller.appspot.com/x/log.txt?x=12d068eff00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a30d6e3e814e5931
> dashboard link: https://syzkaller.appspot.com/bug?extid=9bb26e7c5e8e4fa7e641
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> patch: https://syzkaller.appspot.com/x/patch.diff?x=147f47c8080000
>
> Note: testing is done by a robot and is best-effort only.
You can see the dashboard link above for testing details...
--
Kees Cook
next prev parent reply other threads:[~2022-06-13 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 15:39 [syzbot] WARNING in exit_tasks_rcu_finish syzbot
[not found] ` <87bkux1yn4.fsf@email.froward.int.ebiederm.org>
2022-06-12 20:22 ` Paul E. McKenney
2022-06-13 13:55 ` Zhang, Qiang1
2022-06-13 15:23 ` Paul E. McKenney
2022-06-13 22:26 ` Zhang, Qiang1
2022-06-13 23:37 ` Paul E. McKenney
2022-06-13 23:42 ` Kees Cook [this message]
2022-06-14 0:03 ` Paul E. McKenney
2022-06-14 0:52 ` Zhang, Qiang1
2022-06-14 2:41 ` Paul E. McKenney
2022-06-14 2:47 ` Zhang, Qiang1
2022-06-13 23:54 ` Zhang, Qiang1
2022-06-14 0:01 ` Zhang, Qiang1
2022-06-14 0:04 ` Paul E. McKenney
2022-06-13 0:16 ` syzbot
2022-06-13 10:44 ` 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=202206131639.DBA0A8D@keescook \
--to=keescook@chromium.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=syzbot+9bb26e7c5e8e4fa7e641@syzkaller.appspotmail.com \
--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