From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+d371efea57d5aeab877b@syzkaller.appspotmail.com,
lihongbo22@huawei.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to avoid NULL pointer dereference in f2fs_check_quota_consistency()
Date: Tue, 02 Sep 2025 20:20:12 +0000 [thread overview]
Message-ID: <175684441250.425353.3302301690844852179.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818020939.3529802-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 18 Aug 2025 10:09:38 +0800 you wrote:
> syzbot reported a f2fs bug as below:
>
> Oops: gen[ 107.736417][ T5848] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
> CPU: 1 UID: 0 PID: 5848 Comm: syz-executor263 Tainted: G W 6.17.0-rc1-syzkaller-00014-g0e39a731820a #0 PREEMPT_{RT,(full)}
> RIP: 0010:strcmp+0x3c/0xc0 lib/string.c:284
> Call Trace:
> <TASK>
> f2fs_check_quota_consistency fs/f2fs/super.c:1188 [inline]
> f2fs_check_opt_consistency+0x1378/0x2c10 fs/f2fs/super.c:1436
> __f2fs_remount fs/f2fs/super.c:2653 [inline]
> f2fs_reconfigure+0x482/0x1770 fs/f2fs/super.c:5297
> reconfigure_super+0x224/0x890 fs/super.c:1077
> do_remount fs/namespace.c:3314 [inline]
> path_mount+0xd18/0xfe0 fs/namespace.c:4112
> do_mount fs/namespace.c:4133 [inline]
> __do_sys_mount fs/namespace.c:4344 [inline]
> __se_sys_mount+0x317/0x410 fs/namespace.c:4321
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to avoid NULL pointer dereference in f2fs_check_quota_consistency()
https://git.kernel.org/jaegeuk/f2fs/c/930a9a6ee8e7
- [f2fs-dev,2/2] f2fs: fix to allow removing qf_name
https://git.kernel.org/jaegeuk/f2fs/c/ff11d8701b77
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-02 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:09 Chao Yu
2025-08-18 2:09 ` [PATCH 2/2] f2fs: fix to allow removing qf_name Chao Yu
2025-08-18 8:06 ` Hongbo Li
2025-08-18 8:28 ` Chao Yu
2025-08-19 1:16 ` Hongbo Li
2025-08-19 1:15 ` [PATCH 1/2] f2fs: fix to avoid NULL pointer dereference in f2fs_check_quota_consistency() Hongbo Li
2025-09-02 20:20 ` patchwork-bot+f2fs [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=175684441250.425353.3302301690844852179.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d371efea57d5aeab877b@syzkaller.appspotmail.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®