From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, yuwen.chen@xjmz.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to truncate preallocated blocks in f2fs_file_open()
Date: Wed, 12 Jun 2024 15:55:57 +0000 [thread overview]
Message-ID: <171820775747.32393.11994963596959116040.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240529100103.329778-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 29 May 2024 18:01:03 +0800 you wrote:
> chenyuwen reports a f2fs bug as below:
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011
> fscrypt_set_bio_crypt_ctx+0x78/0x1e8
> f2fs_grab_read_bio+0x78/0x208
> f2fs_submit_page_read+0x44/0x154
> f2fs_get_read_data_page+0x288/0x5f4
> f2fs_get_lock_data_page+0x60/0x190
> truncate_partial_data_page+0x108/0x4fc
> f2fs_do_truncate_blocks+0x344/0x5f0
> f2fs_truncate_blocks+0x6c/0x134
> f2fs_truncate+0xd8/0x200
> f2fs_iget+0x20c/0x5ac
> do_garbage_collect+0x5d0/0xf6c
> f2fs_gc+0x22c/0x6a4
> f2fs_disable_checkpoint+0xc8/0x310
> f2fs_fill_super+0x14bc/0x1764
> mount_bdev+0x1b4/0x21c
> f2fs_mount+0x20/0x30
> legacy_get_tree+0x50/0xbc
> vfs_get_tree+0x5c/0x1b0
> do_new_mount+0x298/0x4cc
> path_mount+0x33c/0x5fc
> __arm64_sys_mount+0xcc/0x15c
> invoke_syscall+0x60/0x150
> el0_svc_common+0xb8/0xf8
> do_el0_svc+0x28/0xa0
> el0_svc+0x24/0x84
> el0t_64_sync_handler+0x88/0xec
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to truncate preallocated blocks in f2fs_file_open()
https://git.kernel.org/jaegeuk/f2fs/c/298b1e4182d6
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:[~2024-06-12 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 10:01 [PATCH v2] f2fs: fix to truncate preallocated blocks in f2fs_file_open() Chao Yu
2024-06-12 15:55 ` 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=171820775747.32393.11994963596959116040.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuwen.chen@xjmz.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