From: syzbot <syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com>
To: amir73il@gmail.com, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, repnop@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] KASAN: slab-out-of-bounds Write in __put_unused_fd
Date: Mon, 06 Jan 2025 03:49:03 -0800 [thread overview]
Message-ID: <677bc32f.050a0220.3b3668.000a.GAE@google.com> (raw)
In-Reply-To: <dlkmio7icps3j2l7iz5g7d2patw2ivssiaus7jzucbrqd4jaq5@w3rekecxeeka>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com
Tested-by: syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com
Tested on:
commit: 94dfee45 Merge fix for access beyond end of bitmap in ..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_next
console output: https://syzkaller.appspot.com/x/log.txt?x=13473418580000
kernel config: https://syzkaller.appspot.com/x/.config?x=16a6f811a8c2a826
dashboard link: https://syzkaller.appspot.com/bug?extid=6a3aa63412255587b21b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-01-06 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 13:27 [syzbot] [fs?] KASAN: slab-out-of-bounds Write in __put_unused_fd syzbot
2024-12-31 13:32 ` Eric Dumazet
2024-12-31 13:41 ` syzbot
2024-12-31 22:15 ` syzbot
2025-01-01 1:34 ` Hillf Danton
2025-01-01 2:03 ` syzbot
2025-01-06 11:15 ` Jan Kara
2025-01-06 11:49 ` 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=677bc32f.050a0220.3b3668.000a.GAE@google.com \
--to=syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=repnop@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox