From: syzbot <syzbot+2f2bc79f24dae1dc62b6@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, adilger@dilger.ca, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, jack@suse.cz,
kuba@kernel.org, kuniyu@amazon.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, sandeen@redhat.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [net?] [ext4?] BUG: corrupted list in __sk_destruct (2)
Date: Thu, 06 Mar 2025 00:20:01 -0800 [thread overview]
Message-ID: <67c95ab1.050a0220.15b4b9.002f.GAE@google.com> (raw)
In-Reply-To: <67c6cf6f.050a0220.15b4b9.0008.GAE@google.com>
syzbot has bisected this issue to:
commit 5872331b3d91820e14716632ebb56b1399b34fe1
Author: Eric Sandeen <sandeen@redhat.com>
Date: Wed Jun 17 19:19:04 2020 +0000
ext4: fix potential negative array index in do_split()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=122e44b7980000
start commit: 7eb172143d55 Linux 6.14-rc5
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=112e44b7980000
console output: https://syzkaller.appspot.com/x/log.txt?x=162e44b7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=523d3ff8e053340a
dashboard link: https://syzkaller.appspot.com/bug?extid=2f2bc79f24dae1dc62b6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126fd5a8580000
Reported-by: syzbot+2f2bc79f24dae1dc62b6@syzkaller.appspotmail.com
Fixes: 5872331b3d91 ("ext4: fix potential negative array index in do_split()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-06 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:01 syzbot
2025-03-06 8:20 ` 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=67c95ab1.050a0220.15b4b9.002f.GAE@google.com \
--to=syzbot+2f2bc79f24dae1dc62b6@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=adilger@dilger.ca \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sandeen@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®