From: syzbot <syzbot+263f8c0d007dc09b2dda@syzkaller.appspotmail.com>
To: davem@davemloft.net, jmaloy@redhat.com, jon.maloy@ericsson.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net,
tuong.t.lien@dektech.com.au, ying.xue@windreiver.com,
ying.xue@windriver.com
Subject: Re: BUG: using smp_processor_id() in preemptible code in tipc_crypto_xmit
Date: Fri, 09 Oct 2020 03:58:09 -0700 [thread overview]
Message-ID: <000000000000f9638c05b13ad2a1@google.com> (raw)
In-Reply-To: <000000000000cbef4a05a8ffc4ef@google.com>
syzbot suspects this issue was fixed by commit:
commit bb8872a1e6bc911869a729240781076ed950764b
Author: Tuong Lien <tuong.t.lien@dektech.com.au>
Date: Sat Aug 29 19:37:55 2020 +0000
tipc: fix using smp_processor_id() in preemptible
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100f5bb8500000
start commit: 6a9dc5fd lib: Revert use of fallthrough pseudo-keyword in ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
dashboard link: https://syzkaller.appspot.com/bug?extid=263f8c0d007dc09b2dda
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131a8c96900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1747c605900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: tipc: fix using smp_processor_id() in preemptible
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-10-09 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:09 BUG: using smp_processor_id() in preemptible code in tipc_crypto_xmit syzbot
2020-07-13 7:19 ` syzbot
2020-07-22 10:59 ` syzbot
2020-10-09 10:58 ` syzbot [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=000000000000f9638c05b13ad2a1@google.com \
--to=syzbot+263f8c0d007dc09b2dda@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jmaloy@redhat.com \
--cc=jon.maloy@ericsson.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tuong.t.lien@dektech.com.au \
--cc=ying.xue@windreiver.com \
--cc=ying.xue@windriver.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).