All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: change the set_page_extent_mapped() call into an ASSERT()
Date: Tue, 27 Jul 2021 18:29:08 +0800	[thread overview]
Message-ID: <68e6284c-3bac-8fb8-af82-1f717bffd3dc@suse.com> (raw)
In-Reply-To: <20210727013942.83531-1-wqu@suse.com>



On 2021/7/27 上午9:39, Qu Wenruo wrote:
> Btrfs uses set_page_extent_mapped() to properly setup a page.
> 
> That function would set PagePrivate, and populate needed structure for
> subpage.
> The timing of calling set_page_extent_mapped() happens before reading a
> page or dirtying a page.
> Thus when we got a page to write back, if it doesn't have PagePrivate,
> it is a big problem in code logic.
> 
> Calling set_page_extent_mapped() for such page would just mask the
> problem.
> Furthermore, for subpage case, we call subpage error helper to clear the
> page error bit before calling set_page_extent_mapped().
> If we really got a page without Private bit, it can call kernel NULL
> pointer dereference.
> 
> So change the set_page_extent_mapped() call to an ASSERT(), and move the
> check before any page status update call.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Please discard the patch.

Although I haven't hit any problem testing the patch, it's still 
possible that we have a special page that would need cow fixup.

Such page will be:

- Dirty

- Not Private
   Thus no page->private, this could still cause problem for subpage case
   though

- No EXTENT_DELALLOC flags set for any range inside the page
   Thus writepage_delalloc() will not find a delalloc range inside the
   page.

Such page will be caught by btrfs_writepage_cow_fixup(), but it will 
trigger the ASSERT() added by this patch.

Thanks,
Qu

> ---
>   fs/btrfs/extent_io.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 62f0ed2de2b9..219add264acf 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -4099,6 +4099,12 @@ static int __extent_writepage(struct page *page, struct writeback_control *wbc,
>   
>   	WARN_ON(!PageLocked(page));
>   
> +	/*
> +	 * All dirty page to be written should have PagePrivate set by
> +	 * set_page_extent_mapped() when creating the page.
> +	 */
> +	ASSERT(PagePrivate(page));
> +
>   	btrfs_page_clear_error(btrfs_sb(inode->i_sb), page,
>   			       page_offset(page), PAGE_SIZE);
>   
> @@ -4115,12 +4121,6 @@ static int __extent_writepage(struct page *page, struct writeback_control *wbc,
>   		flush_dcache_page(page);
>   	}
>   
> -	ret = set_page_extent_mapped(page);
> -	if (ret < 0) {
> -		SetPageError(page);
> -		goto done;
> -	}
> -
>   	if (!epd->extent_locked) {
>   		ret = writepage_delalloc(BTRFS_I(inode), page, wbc,
>   					 &nr_written);
> 


  reply	other threads:[~2021-07-27 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  1:39 [PATCH] btrfs: change the set_page_extent_mapped() call into an ASSERT() Qu Wenruo
2021-07-27 10:29 ` Qu Wenruo [this message]
2021-07-27 14:23   ` David Sterba

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=68e6284c-3bac-8fb8-af82-1f717bffd3dc@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.