From: syzbot <syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] KASAN: slab-out-of-bounds Read in ext4_search_dir
Date: Thu, 02 Oct 2025 23:38:02 -0700 [thread overview]
Message-ID: <68df6f4a.a00a0220.102ee.010f.GAE@google.com> (raw)
In-Reply-To: <20251003061658.2515919-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com
Tested-by: syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com
Tested on:
commit: e406d57b Merge tag 'mm-nonmm-stable-2025-10-02-15-29' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=134ad942580000
kernel config: https://syzkaller.appspot.com/x/.config?x=84e81c4d0c0e900a
dashboard link: https://syzkaller.appspot.com/bug?extid=3ee481e21fd75e14c397
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=100165cd980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-03 6:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251003061658.2515919-1-kartikey406@gmail.com>
2025-10-03 6:38 ` syzbot [this message]
[not found] <aRZ0EwX9Ajg38Sei@rpthibeault-XPS-13-9305>
2025-11-14 0:34 ` [syzbot] [ext4?] KASAN: slab-out-of-bounds Read in ext4_search_dir syzbot
[not found] <aRZbvQgQgxVbfgow@rpthibeault-XPS-13-9305>
2025-11-13 22:48 ` syzbot
[not found] <aQ-D6qQkBA6XUgyD@rpthibeault-XPS-13-9305>
2025-11-08 18:16 ` syzbot
[not found] <aQ7WfQOMTIDiPBin@rpthibeault-XPS-13-9305>
2025-11-08 5:55 ` syzbot
[not found] <20251003090932.2559979-1-kartikey406@gmail.com>
2025-10-03 9:30 ` syzbot
[not found] <20251003083604.2556017-1-kartikey406@gmail.com>
2025-10-03 8:57 ` syzbot
[not found] <20251003081442.2555454-1-kartikey406@gmail.com>
2025-10-03 8:35 ` syzbot
[not found] <20251003040153.2411696-1-kartikey406@gmail.com>
2025-10-03 4:23 ` syzbot
[not found] <20251003031625.2411015-1-kartikey406@gmail.com>
2025-10-03 3:43 ` syzbot
[not found] <20251003030202.2409492-1-kartikey406@gmail.com>
2025-10-03 3:23 ` syzbot
[not found] <20251003020223.2408483-1-kartikey406@gmail.com>
2025-10-03 2:23 ` syzbot
[not found] <20251003014049.2407777-1-kartikey406@gmail.com>
2025-10-03 2:02 ` syzbot
[not found] <20251003010657.2402278-1-kartikey406@gmail.com>
2025-10-03 1:28 ` syzbot
[not found] <20251003002303.2398961-1-kartikey406@gmail.com>
2025-10-03 0:44 ` syzbot
[not found] <20251002235337.2398242-1-kartikey406@gmail.com>
2025-10-03 0:16 ` syzbot
[not found] <20251002225742.2395560-1-kartikey406@gmail.com>
2025-10-02 23:34 ` syzbot
[not found] <20251002100108.2390216-1-kartikey406@gmail.com>
2025-10-02 10:32 ` syzbot
[not found] <20251002093807.2387597-1-kartikey406@gmail.com>
2025-10-02 9:48 ` syzbot
[not found] <20251002062804.2167179-1-kartikey406@gmail.com>
2025-10-02 6:49 ` syzbot
[not found] <20251002061821.2163863-1-kartikey406@gmail.com>
2025-10-02 6:26 ` syzbot
[not found] <20251002050906.2082433-1-kartikey406@gmail.com>
2025-10-02 5:30 ` syzbot
2025-10-02 0:10 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=68df6f4a.a00a0220.102ee.010f.GAE@google.com \
--to=syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).