From: syzbot <syzbot+a7e701c8385bd8543074@syzkaller.appspotmail.com>
To: 0x7f454c46@gmail.com, davem@davemloft.net, dima@arista.com,
hdanton@sina.com, herbert@gondor.apana.org.au, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in xfrm_alloc_compat
Date: Sat, 31 Oct 2020 09:24:05 -0700 [thread overview]
Message-ID: <0000000000001e5c6b05b2f9f1e5@google.com> (raw)
In-Reply-To: <00000000000021315205b29353aa@google.com>
syzbot has bisected this issue to:
commit 5f3eea6b7e8f58cf5c8a9d4b9679dc19e9e67ba3
Author: Dmitry Safonov <dima@arista.com>
Date: Mon Sep 21 14:36:53 2020 +0000
xfrm/compat: Attach xfrm dumps to 64=>32 bit translator
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=102aadf4500000
start commit: 2b94f526 net: stmmac: Fix channel lock initialization
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=122aadf4500000
console output: https://syzkaller.appspot.com/x/log.txt?x=142aadf4500000
kernel config: https://syzkaller.appspot.com/x/.config?x=803dd96a0e492ac1
dashboard link: https://syzkaller.appspot.com/bug?extid=a7e701c8385bd8543074
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a6e324500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1382100c500000
Reported-by: syzbot+a7e701c8385bd8543074@syzkaller.appspotmail.com
Fixes: 5f3eea6b7e8f ("xfrm/compat: Attach xfrm dumps to 64=>32 bit translator")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-10-31 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 13:58 WARNING in xfrm_alloc_compat syzbot
2020-10-28 10:45 ` Steffen Klassert
2020-10-28 17:42 ` Dmitry Safonov
2020-10-31 9:16 ` syzbot
2020-10-31 16:24 ` 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=0000000000001e5c6b05b2f9f1e5@google.com \
--to=syzbot+a7e701c8385bd8543074@syzkaller.appspotmail.com \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=hdanton@sina.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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