From: syzbot <syzbot+c3b90a95b2d6bd4f29b1@syzkaller.appspotmail.com>
To: davem@davemloft.net, gregkh@linuxfoundation.org,
jon.maloy@ericsson.com, keescook@chromium.org,
kstewart@linuxfoundation.org, ktkhai@virtuozzo.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
nicolas.dichtel@6wind.com, pombredanne@nexb.com,
syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com
Subject: Re: INFO: task hung in genl_rcv_msg
Date: Thu, 28 Mar 2019 04:36:00 -0700 [thread overview]
Message-ID: <0000000000006088db058525f51f@google.com> (raw)
In-Reply-To: <0000000000007f82d805783fe8ce@google.com>
syzbot has bisected this bug to:
commit 928df1880e24bcd47d6359ff86df24db3dfba3c3
Author: Jon Maloy <jon.maloy@ericsson.com>
Date: Thu Mar 15 15:48:51 2018 +0000
tipc: obsolete TIPC_ZONE_SCOPE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1487ea0f200000
start commit: a5ed1e96 Merge tag 'powerpc-5.1-3' of git://git.kernel.org..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1687ea0f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1287ea0f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a31fb246de2a622
dashboard link: https://syzkaller.appspot.com/bug?extid=c3b90a95b2d6bd4f29b1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176657ef200000
Reported-by: syzbot+c3b90a95b2d6bd4f29b1@syzkaller.appspotmail.com
Fixes: 928df1880e24 ("tipc: obsolete TIPC_ZONE_SCOPE")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-03-28 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 8:06 INFO: task hung in genl_rcv_msg syzbot
2019-03-28 11:36 ` 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=0000000000006088db058525f51f@google.com \
--to=syzbot+c3b90a95b2d6bd4f29b1@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jon.maloy@ericsson.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pombredanne@nexb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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).