public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Wenjie Qi <qwjhust@gmail.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, hustqwj@hust.edu.cn,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v1] f2fs: fix NULL pointer dereference in f2fs_submit_page_write()
Date: Mon, 29 Jan 2024 19:16:51 +0800	[thread overview]
Message-ID: <0f356116-9e67-4abb-8bc2-65e63a936c17@kernel.org> (raw)
In-Reply-To: <d379bc01-ca31-41e6-9d85-7fca846af491@kernel.org>

On 2024/1/29 18:27, Chao Yu wrote:
> On 2024/1/16 22:11, Wenjie Qi wrote:
>> BUG: kernel NULL pointer dereference, address: 0000000000000014
>> RIP: 0010:f2fs_submit_page_write+0x6cf/0x780 [f2fs]
>> Call Trace:
>> <TASK>
>> ? show_regs+0x6e/0x80
>> ? __die+0x29/0x70
>> ? page_fault_oops+0x154/0x4a0
>> ? prb_read_valid+0x20/0x30
>> ? __irq_work_queue_local+0x39/0xd0
>> ? irq_work_queue+0x36/0x70
>> ? do_user_addr_fault+0x314/0x6c0
>> ? exc_page_fault+0x7d/0x190
>> ? asm_exc_page_fault+0x2b/0x30
>> ? f2fs_submit_page_write+0x6cf/0x780 [f2fs]
>> ? f2fs_submit_page_write+0x736/0x780 [f2fs]
>> do_write_page+0x50/0x170 [f2fs]
>> f2fs_outplace_write_data+0x61/0xb0 [f2fs]
>> f2fs_do_write_data_page+0x3f8/0x660 [f2fs]
>> f2fs_write_single_data_page+0x5bb/0x7a0 [f2fs]
>> f2fs_write_cache_pages+0x3da/0xbe0 [f2fs]
>> ...
>> It is possible that other threads have added this fio to io->bio
>> and submitted the io->bio before entering f2fs_submit_page_write().
>> At this point io->bio = NULL.
>> If is_end_zone_blkaddr(sbi, fio->new_blkaddr) of this fio is true,
>> then an NULL pointer dereference error occurs at bio_get(io->bio).
>> The original code for determining zone end was after "out:",
>> which would have missed some fio who is zone end. I've moved
>>   this code before "skip:" to make sure it's done for each fio.
>>

Fixes: e067dc3c6b9c ("f2fs: maintain six open zones for zoned devices")

>> Signed-off-by: Wenjie Qi <qwjhust@gmail.com>
> 
> Reviewed-by: Chao Yu <chao@kernel.org>
> 
> Thanks,
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-01-29 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 14:11 [PATCH v1] f2fs: fix NULL pointer dereference in f2fs_submit_page_write() Wenjie Qi
2024-01-16 21:58 ` [f2fs-dev] " Daeho Jeong
2024-01-17  1:39   ` Wenjie Qi
2024-01-17 10:17     ` Yongpeng Yang
2024-01-17 11:27       ` Wenjie Qi
2024-01-29 10:27 ` Chao Yu
2024-01-29 11:16   ` Chao Yu [this message]
2024-01-29 20:29 ` [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=0f356116-9e67-4abb-8bc2-65e63a936c17@kernel.org \
    --to=chao@kernel.org \
    --cc=hustqwj@hust.edu.cn \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qwjhust@gmail.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