From: syzbot <syzbot+5078fc2d7cf37d71de1c@syzkaller.appspotmail.com>
To: davem@davemloft.net, dima@arista.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,
tonymarislogistics@yandex.com, xiyou.wangcong@gmail.com,
zoe.byrne@bpchargemaster.com
Subject: Re: [syzbot] general protection fault in xfrm_user_rcv_msg_compat
Date: Mon, 06 Sep 2021 12:29:12 -0700 [thread overview]
Message-ID: <000000000000ed630705cb58a93b@google.com> (raw)
In-Reply-To: <00000000000056c3e005b82689d1@google.com>
syzbot suspects this issue was fixed by commit:
commit 4e9505064f58d1252805952f8547a5b7dbc5c111
Author: Dmitry Safonov <dima@arista.com>
Date: Sat Jul 17 15:02:21 2021 +0000
net/xfrm/compat: Copy xfrm_spdattr_type_t atributes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b8aa69300000
start commit: a99163e9e708 Merge tag 'devicetree-for-5.12' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7a875029a795d230
dashboard link: https://syzkaller.appspot.com/bug?extid=5078fc2d7cf37d71de1c
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=167c1832d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10214f12d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/xfrm/compat: Copy xfrm_spdattr_type_t atributes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-09-06 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 12:42 general protection fault in xfrm_user_rcv_msg_compat syzbot
2021-02-23 14:47 ` syzbot
2021-02-23 22:44 ` Cong Wang
2021-09-06 19:29 ` syzbot [this message]
2022-05-12 13:12 ` [syzbot] " 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=000000000000ed630705cb58a93b@google.com \
--to=syzbot+5078fc2d7cf37d71de1c@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dima@arista.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 \
--cc=tonymarislogistics@yandex.com \
--cc=xiyou.wangcong@gmail.com \
--cc=zoe.byrne@bpchargemaster.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).