From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix kernel crash due to null io->bio
Date: Tue, 07 Feb 2023 19:00:17 +0000 [thread overview]
Message-ID: <167579641779.24576.11865638891088345725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230206034344.724593-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 5 Feb 2023 19:43:44 -0800 you wrote:
> We should return when io->bio is null before doing anything. Otherwise, panic.
>
> BUG: kernel NULL pointer dereference, address: 0000000000000010
> RIP: 0010:__submit_merged_write_cond+0x164/0x240 [f2fs]
> Call Trace:
> <TASK>
> f2fs_submit_merged_write+0x1d/0x30 [f2fs]
> commit_checkpoint+0x110/0x1e0 [f2fs]
> f2fs_write_checkpoint+0x9f7/0xf00 [f2fs]
> ? __pfx_issue_checkpoint_thread+0x10/0x10 [f2fs]
> __checkpoint_and_complete_reqs+0x84/0x190 [f2fs]
> ? preempt_count_add+0x82/0xc0
> ? __pfx_issue_checkpoint_thread+0x10/0x10 [f2fs]
> issue_checkpoint_thread+0x4c/0xf0 [f2fs]
> ? __pfx_autoremove_wake_function+0x10/0x10
> kthread+0xff/0x130
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x2c/0x50
> </TASK>
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix kernel crash due to null io->bio
https://git.kernel.org/jaegeuk/f2fs/c/267c159f9c7b
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:[~2023-02-07 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 3:43 Jaegeuk Kim
2023-02-07 12:35 ` [f2fs-dev] " Chao Yu
2023-02-07 19:00 ` 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=167579641779.24576.11865638891088345725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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®