From: syzbot <syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com>
To: alexanderduyck@fb.com, chuck.lever@oracle.com,
davem@davemloft.net, edumazet@google.com,
herbert@gondor.apana.org.au, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linyunsheng@huawei.com,
netdev@vger.kernel.org, pabeni@redhat.com,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] kernel BUG in set_ipsecrequest
Date: Fri, 17 Oct 2025 03:53:04 -0700 [thread overview]
Message-ID: <68f22010.050a0220.91a22.041c.GAE@google.com> (raw)
In-Reply-To: <68f1d9d6.050a0220.91a22.0419.GAE@google.com>
syzbot has bisected this issue to:
commit 14ad6ed30a10afbe91b0749d6378285f4225d482
Author: Paolo Abeni <pabeni@redhat.com>
Date: Tue Feb 18 18:29:39 2025 +0000
net: allow small head cache usage with large MAX_SKB_FRAGS values
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=177a35e2580000
start commit: 48a97ffc6c82 bpf: Consistently use bpf_rcu_lock_held() eve..
git tree: bpf-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14fa35e2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10fa35e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ad7b090a18654a7
dashboard link: https://syzkaller.appspot.com/bug?extid=be97dd4da14ae88b6ba4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16f7e5e2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ecec58580000
Reported-by: syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com
Fixes: 14ad6ed30a10 ("net: allow small head cache usage with large MAX_SKB_FRAGS values")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-17 10:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 5:53 [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-17 10:53 ` syzbot [this message]
2025-10-19 2:34 ` [PATCH] key: No support for family zero Edward Adam Davis
2025-10-27 21:00 ` Simon Horman
2025-10-19 18:29 ` [syzbot] [net?] kernel BUG in set_ipsecrequest shaurya
2025-10-19 18:32 ` syzbot
2025-10-20 2:57 ` Forwarded: [Testing] net: key: Validate address family in set_ipsecrequest() syzbot
2025-10-20 7:30 ` Forwarded: [PATCH] Fix integer overflow " syzbot
2025-10-20 7:54 ` Forwarded: Re: [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-20 11:19 ` Forwarded: syzbot
2025-10-21 3:00 ` [PATCH] fix integer overflow in set_ipsecrequest clingfei
2025-10-23 12:24 ` [PATCH net] net: key: Fix potential " clingfei
2025-10-27 20:37 ` Simon Horman
[not found] <81eb1a55-dd34-43d1-93d1-33d0f24c7622@ee.vjti.ac.in>
2025-10-19 18:31 ` [syzbot] [net?] kernel BUG " syzbot
[not found] <ac912e45-9267-4c0c-b700-dd1b602ef2c0@gmail.com>
2025-10-19 18:32 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 2:49 [PATCH] net: key: Validate address family in set_ipsecrequest() SHAURYA RANE
2025-10-20 2:52 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
[not found] <20251020025728.15250-1-ssranevjti@gmail.com>
2025-10-20 3:16 ` syzbot
2025-10-20 6:00 1599101385
2025-10-20 6:01 ` syzbot
2025-10-20 6:03 1599101385
2025-10-20 7:30 [PATCH] Fix integer overflow in set_ipsecrequest() clingfei
2025-10-20 7:36 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
2025-10-20 7:46 ` clingfei
2025-10-20 7:48 ` syzbot
[not found] <CADPKJ-7HnHKJ6RxzUcLh8NSXRq+99aim5tTvhz8j1s-TMx9saA@mail.gmail.com>
2025-10-20 7:56 ` syzbot
[not found] <20251020111926.938354-1-1599101385@qq.com>
2025-10-20 13:48 ` syzbot
2025-11-06 13:56 [PATCH 3/3] net: key: Validate address family in set_ipsecrequest() clingfei
2025-11-06 14:22 ` [syzbot] [net?] kernel BUG in set_ipsecrequest syzbot
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=68f22010.050a0220.91a22.041c.GAE@google.com \
--to=syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com \
--cc=alexanderduyck@fb.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.