From: syzbot <syzbot+0b1279812c46e48bb0c1@syzkaller.appspotmail.com>
To: hsiangkao@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] general protection fault in fuse_do_readpage
Date: Wed, 13 Nov 2024 21:52:04 -0800 [thread overview]
Message-ID: <67359004.050a0220.2a2fcc.005f.GAE@google.com> (raw)
In-Reply-To: <e22f5b69-0462-41c6-b7a9-b3ae10fa6992@linux.alibaba.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0b1279812c46e48bb0c1@syzkaller.appspotmail.com
Tested-by: syzbot+0b1279812c46e48bb0c1@syzkaller.appspotmail.com
Tested on:
commit: 779014de erofs: fix file-backed mounts over FUSE
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=155294c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2effb62852f5a821
dashboard link: https://syzkaller.appspot.com/bug?extid=0b1279812c46e48bb0c1
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.
prev parent reply other threads:[~2024-11-14 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 18:07 [syzbot] [fuse?] general protection fault in fuse_do_readpage syzbot
2024-11-04 1:37 ` Lizhi Xu
2024-11-04 1:56 ` syzbot
2024-11-14 2:04 ` [PATCH] fuse: check file before running readpage Lizhi Xu
2024-11-14 2:40 ` Gao Xiang
2024-11-14 5:33 ` [syzbot] [fuse?] general protection fault in fuse_do_readpage Gao Xiang
2024-11-14 5:52 ` 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=67359004.050a0220.2a2fcc.005f.GAE@google.com \
--to=syzbot+0b1279812c46e48bb0c1@syzkaller.appspotmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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.