From: "Paul E. McKenney" <paulmck@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+fe9d8c955bd1d0f02dc1@syzkaller.appspotmail.com>,
bigeasy@linutronix.de, jgross@suse.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, josh@joshtriplett.org,
linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com,
mingo@kernel.org, namit@vmware.com, netdev@vger.kernel.org,
peterz@infradead.org, rcu@vger.kernel.org, rdunlap@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in trc_read_check_handler
Date: Sat, 4 Dec 2021 07:07:59 -0800 [thread overview]
Message-ID: <20211204150759.GW641268@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <CACT4Y+bLs5ycD1khkbMFDW=5UxMqxmbkXQoskyEz74H-u98pDw@mail.gmail.com>
On Sat, Dec 04, 2021 at 10:50:47AM +0100, Dmitry Vyukov wrote:
> On Wed, 1 Dec 2021 at 22:09, Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > On Wed, Dec 01, 2021 at 12:50:07PM -0800, syzbot wrote:
> > > syzbot suspects this issue was fixed by commit:
> > >
> > > commit 96017bf9039763a2e02dcc6adaa18592cd73a39d
> > > Author: Paul E. McKenney <paulmck@kernel.org>
> > > Date: Wed Jul 28 17:53:41 2021 +0000
> > >
> > > rcu-tasks: Simplify trc_read_check_handler() atomic operations
> > >
> > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1281d89db00000
> > > start commit: 5319255b8df9 selftests/bpf: Skip verifier tests that fail ..
> > > git tree: bpf-next
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=9290a409049988d4
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=fe9d8c955bd1d0f02dc1
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14990477300000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105ebd84b00000
> > >
> > > If the result looks correct, please mark the issue as fixed by replying with:
> >
> > #syz fix: rcu-tasks: Simplify trc_read_check_handler() atomic operations
> >
> > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> >
> > Give or take. There were quite a few related bugs, so some or all of
> > the following commits might also have helped:
> >
> > cbe0d8d91415c rcu-tasks: Wait for trc_read_check_handler() IPIs
> > 18f08e758f34e rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
> > 46aa886c483f5 rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
>
> Thanks for checking. If we don't have one exact fix, let's go with
> what syzbot suggested. At this point it does not matter much since all
> of them are in most trees I assume. We just need to close the bug with
> something.
>
> #syz fix: rcu-tasks: Simplify trc_read_check_handler() atomic operations
Fair enough!
> > Quibbles aside, it is nice to get an automated email about having fixed
> > a bug as opposed to having added one. ;-)
>
> Yes, but one is not possible without the other :-)
But of course it is possible! For example, syzkaller might find a bug
that was already fixed, and then before notifying me about the bug, you
see the fix. For example, by failing to reproduce a mainline bug on -rcu.
Not that I particularly want to be auto-spammed about bugs that I have
already fixed, mind you! ;-)
Thanx, Paul
prev parent reply other threads:[~2021-12-04 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 9:06 [syzbot] WARNING in trc_read_check_handler syzbot
2021-08-05 16:09 ` Paul E. McKenney
2021-12-01 20:50 ` syzbot
2021-12-01 21:09 ` Paul E. McKenney
2021-12-04 9:50 ` Dmitry Vyukov
2021-12-04 15:07 ` Paul E. McKenney [this message]
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=20211204150759.GW641268@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=dvyukov@google.com \
--cc=jgross@suse.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzbot+fe9d8c955bd1d0f02dc1@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;
as well as URLs for NNTP newsgroup(s).