From: Chao Yu <chao@kernel.org>
To: Ye Bin <yebin@huaweicloud.com>, jaegeuk@kernel.org
Cc: Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, zhangxiaoxu5@huawei.com
Subject: Re: [PATCH] f2fs: fix null-ptr-deref in f2fs_submit_page_bio()
Date: Sat, 12 Oct 2024 10:42:48 +0800 [thread overview]
Message-ID: <64487878-21fb-4679-ac1c-ce24c02a3e64@kernel.org> (raw)
In-Reply-To: <20241011164450.3366215-1-yebin@huaweicloud.com>
On 2024/10/12 0:44, Ye Bin wrote:
> From: Ye Bin <yebin10@huawei.com>
>
> There's issue as follows when concurrently installing the f2fs.ko
> module and mounting the f2fs file system:
> KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
> RIP: 0010:__bio_alloc+0x2fb/0x6c0 [f2fs]
> Call Trace:
> <TASK>
> f2fs_submit_page_bio+0x126/0x8b0 [f2fs]
> __get_meta_page+0x1d4/0x920 [f2fs]
> get_checkpoint_version.constprop.0+0x2b/0x3c0 [f2fs]
> validate_checkpoint+0xac/0x290 [f2fs]
> f2fs_get_valid_checkpoint+0x207/0x950 [f2fs]
> f2fs_fill_super+0x1007/0x39b0 [f2fs]
> mount_bdev+0x183/0x250
> legacy_get_tree+0xf4/0x1e0
> vfs_get_tree+0x88/0x340
> do_new_mount+0x283/0x5e0
> path_mount+0x2b2/0x15b0
> __x64_sys_mount+0x1fe/0x270
> do_syscall_64+0x5f/0x170
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> Above issue happens as the biset of the f2fs file system is not
> initialized before register "f2fs_fs_type".
> To address above issue just register "f2fs_fs_type" at the last in
> init_f2fs_fs(). Ensure that all f2fs file system resources are
> initialized.
>
> Fixes: f543805fcd60 ("f2fs: introduce private bioset")
> Signed-off-by: Ye Bin <yebin10@huawei.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-10-12 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 16:44 Ye Bin
2024-10-12 2:42 ` Chao Yu [this message]
2024-10-28 17:40 ` [f2fs-dev] " patchwork-bot+f2fs
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=64487878-21fb-4679-ac1c-ce24c02a3e64@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin@huaweicloud.com \
--cc=zhangxiaoxu5@huawei.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
all inboxes | Powered by JetHome®