From: syzbot <syzbot+2625ce08c2659fb9961a@syzkaller.appspotmail.com>
To: dhowells@redhat.com, jlayton@kernel.org, joannelkoong@gmail.com,
josef@toxicpanda.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, miklos@szeredi.hu,
mszeredi@redhat.com, netfs@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] KASAN: slab-use-after-free Read in iov_iter_revert
Date: Mon, 06 Jan 2025 09:42:05 -0800 [thread overview]
Message-ID: <677c15ed.050a0220.3b3668.0016.GAE@google.com> (raw)
In-Reply-To: <CAJnrk1ZC4orWTbJAKVuDwmRCRRN-WSM6xpcNiGW48P55nD3r+Q@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2625ce08c2659fb9961a@syzkaller.appspotmail.com
Tested-by: syzbot+2625ce08c2659fb9961a@syzkaller.appspotmail.com
Tested on:
commit: 78f2560f fuse: Set *nbytesp=0 in fuse_get_user_pages o..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16eeb418580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0669984e46cc674
dashboard link: https://syzkaller.appspot.com/bug?extid=2625ce08c2659fb9961a
compiler: gcc (Debian 12.2.0-14) 12.2.0, 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.
next prev parent reply other threads:[~2025-01-06 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:26 [syzbot] [netfs?] KASAN: slab-use-after-free Read in iov_iter_revert syzbot
2024-11-30 0:21 ` syzbot
2025-01-02 20:18 ` Miklos Szeredi
2025-01-02 20:18 ` syzbot
2025-01-02 20:19 ` Miklos Szeredi
2025-01-02 20:19 ` syzbot
2025-01-03 23:11 ` Joanne Koong
2025-01-03 23:11 ` syzbot
2025-01-06 17:23 ` Joanne Koong
2025-01-06 17:42 ` syzbot [this message]
2025-01-02 20:32 ` [syzbot] " syzbot
[not found] <CAJfpeguwka-DuMo9zYNFVOX8Tff2w7bpazmSamGN3P2tv+9hJg@mail.gmail.com>
2025-01-02 20:51 ` [syzbot] [fuse?] " syzbot
2025-01-02 21:12 ` Miklos Szeredi
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=677c15ed.050a0220.3b3668.0016.GAE@google.com \
--to=syzbot+2625ce08c2659fb9961a@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=netfs@lists.linux.dev \
--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