From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Sanan Hasanov <Sanan.Hasanov@ucf.edu>,
"xiang@kernel.org" <xiang@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"huyue2@coolpad.com" <huyue2@coolpad.com>,
"jefflexu@linux.alibaba.com" <jefflexu@linux.alibaba.com>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "syzkaller@googlegroups.com" <syzkaller@googlegroups.com>,
"contact@pgazz.com" <contact@pgazz.com>
Subject: Re: kernel BUG in erofs_iget
Date: Wed, 13 Sep 2023 08:38:46 +0800 [thread overview]
Message-ID: <7f11496e-ef18-1dcd-bd85-68663531f50d@linux.alibaba.com> (raw)
In-Reply-To: <BL0PR11MB3106CA52AA8E2978AF2756B6E1EEA@BL0PR11MB3106.namprd11.prod.outlook.com>
On 2023/9/13 07:02, Sanan Hasanov wrote:
> Good day, dear maintainers,
>
> We found a bug using a modified kernel configuration file used by syzbot.
>
> We enhanced the coverage of the configuration file using our tool, klocalizer.
1) Please don't enable CONFIG_EROFS_FS_DEBUG=y when fuzzing. This configuration
is just for developper debugging, not for daily use or fuzzing.
2) Please don't use random -next version, I don't even find this version in
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/refs/tags
now. Although it seems
198 bogusimode:
199 erofs_err(inode->i_sb, "bogus i_mode (%o) @ nid %llu",
200 inode->i_mode, vi->nid);
201 err = -EFSCORRUPTED;
202 err_out:
203> DBG_BUGON(1);
204 kfree(copied);
205 erofs_put_metabuf(buf);
206 return ERR_PTR(err);
when I check Linux v6.3 source code. Please use upstream or latest tree for
fuzzing, thanks!
Thanks,
Gao Xiang
>
> Kernel Branch: 6.3.0-next-20230426
> Kernel Config: https://drive.google.com/file/d/1rGIKWTEfoMed0JL5jWFws4GJ0VNSVgw8/view?usp=sharing
> Reproducer: https://drive.google.com/file/d/1ceAFcx9hhevq_ivDNPkXmEGYsr26yB4N/view?usp=sharing
> Thank you!
>
> Best regards,
> Sanan Hasanov
>
prev parent reply other threads:[~2023-09-13 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 23:02 Sanan Hasanov
2023-09-13 0:38 ` Gao Xiang [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=7f11496e-ef18-1dcd-bd85-68663531f50d@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=Sanan.Hasanov@ucf.edu \
--cc=chao@kernel.org \
--cc=contact@pgazz.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=xiang@kernel.org \
/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®