From: syzbot <syzbot+131cd4c6d21724b99a26@syzkaller.appspotmail.com>
To: anant.thazhemadam@gmail.com, davem@davemloft.net,
dvyukov@google.com, edumazet@google.com, glider@google.com,
herbert@gondor.apana.org.au, icytxw@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, steffen.klassert@secunet.com,
syzkaller-bugs@googlegroups.com, tobias@strongswan.org,
tonymarislogistics@yandex.com
Subject: Re: [syzbot] [net?] KMSAN: uninit-value in xfrm_state_find
Date: Mon, 19 Jun 2023 23:41:23 -0700 [thread overview]
Message-ID: <00000000000097ad8105fe89f0a9@google.com> (raw)
In-Reply-To: <0000000000001f31eb056ea92fcb@google.com>
syzbot suspects this issue was fixed by commit:
commit 3d776e31c841ba2f69895d2255a49320bec7cea6
Author: Tobias Brunner <tobias@strongswan.org>
Date: Tue May 9 08:59:58 2023 +0000
xfrm: Reject optional tunnel/BEET mode templates in outbound policies
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13eeaa4b280000
start commit: e4cf7c25bae5 Merge tag 'kbuild-fixes-v6.2' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2651619a26b4d687
dashboard link: https://syzkaller.appspot.com/bug?extid=131cd4c6d21724b99a26
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1140605c480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c92718480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfrm: Reject optional tunnel/BEET mode templates in outbound policies
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-20 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 7:30 KMSAN: uninit-value in xfrm_state_find syzbot
2018-06-15 7:31 ` Dmitry Vyukov
2023-06-20 6:41 ` syzbot [this message]
2023-06-20 9:13 ` [syzbot] [net?] " Aleksandr Nogikh
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=00000000000097ad8105fe89f0a9@google.com \
--to=syzbot+131cd4c6d21724b99a26@syzkaller.appspotmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=icytxw@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tobias@strongswan.org \
--cc=tonymarislogistics@yandex.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 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.