All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3654c027d861c6df4b06@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, bp@alien8.de, coreteam@netfilter.org,
	davem@davemloft.net, fw@strlen.de, fweisbec@gmail.com,
	hdanton@sina.com, hpa@zytor.com, jmaloy@redhat.com,
	jmattson@google.com, joro@8bytes.org, kadlec@netfilter.org,
	kuba@kernel.org, kuznet@ms2.inr.ac.ru, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
	pablo@netfilter.org, pbonzini@redhat.com,
	sean.j.christopherson@intel.com, subashab@codeaurora.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	tuong.t.lien@dektech.com.au, vkuznets@redhat.com,
	wanpengli@tencent.com, x86@kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: INFO: rcu detected stall in tipc_release
Date: Sun, 20 Dec 2020 01:37:03 -0800	[thread overview]
Message-ID: <0000000000008647f705b6e215de@google.com> (raw)
In-Reply-To: <000000000000264c6305a9c74d9b@google.com>

syzbot suspects this issue was fixed by commit:

commit cc00bcaa589914096edef7fb87ca5cee4a166b5c
Author: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Date:   Wed Nov 25 18:27:22 2020 +0000

    netfilter: x_tables: Switch synchronization to RCU

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1445cb37500000
start commit:   7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=3654c027d861c6df4b06
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12948233100000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11344c05100000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: netfilter: x_tables: Switch synchronization to RCU

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2020-12-20  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 15:12 INFO: rcu detected stall in tipc_release syzbot
2020-07-17  4:20 ` syzbot
2020-12-20  9:37 ` syzbot [this message]
2020-12-21  9:21   ` Dmitry Vyukov
2020-12-23 10:24     ` Dmitry Vyukov

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=0000000000008647f705b6e215de@google.com \
    --to=syzbot+3654c027d861c6df4b06@syzkaller.appspotmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=bp@alien8.de \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=fweisbec@gmail.com \
    --cc=hdanton@sina.com \
    --cc=hpa@zytor.com \
    --cc=jmaloy@redhat.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=subashab@codeaurora.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=tuong.t.lien@dektech.com.au \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /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.