All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	"Xiubo Li" <xiubli@redhat.com>,
	"Luís Henriques" <lhenriques@suse.de>
Subject: Re: [PATCH] mm: BUG if filemap_alloc_folio gives us a folio with a non-NULL ->private
Date: Fri, 13 May 2022 15:47:54 +0100	[thread overview]
Message-ID: <Yn5vmh0WbhczfURJ@casper.infradead.org> (raw)
In-Reply-To: <20220513142952.27853-1-jlayton@kernel.org>

On Fri, May 13, 2022 at 10:29:52AM -0400, Jeff Layton wrote:
> We've seen some instances where we call __filemap_get_folio and get back
> one with a ->private value that is non-NULL. Let's have the allocator
> bug if that happens.

Oh, I meant for this to be a debugging aid for your case, rather than
be something we put into upstream.  If we do find out that the page
allocator is returning pages with page->private non-NULL, we should
discuss what the guarantee is that the page allocator provides -- does
it guarantee that page->private is NULL, or is that something the page
cache should zero out itself.

If we do end up changing filemap_alloc_folio(), we need to remember to
change the one in pagemap.h too.

> URL: https://tracker.ceph.com/issues/55421
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Xiubo Li <xiubli@redhat.com>
> Cc: Luís Henriques <lhenriques@suse.de>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>  mm/filemap.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> It might not hurt to merge this into mainline. If it pops then we know
> something is very wrong.
> 
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 9a1eef6c5d35..74c3fb062ef7 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -990,10 +990,12 @@ struct folio *filemap_alloc_folio(gfp_t gfp, unsigned int order)
>  			n = cpuset_mem_spread_node();
>  			folio = __folio_alloc_node(gfp, order, n);
>  		} while (!folio && read_mems_allowed_retry(cpuset_mems_cookie));
> -
> -		return folio;
> +	} else {
> +		folio = folio_alloc(gfp, order);
>  	}
> -	return folio_alloc(gfp, order);
> +	if (folio)
> +		VM_BUG_ON_FOLIO(folio->private, folio);
> +	return folio;
>  }
>  EXPORT_SYMBOL(filemap_alloc_folio);
>  #endif
> -- 
> 2.36.1
> 

      reply	other threads:[~2022-05-13 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 14:29 [PATCH] mm: BUG if filemap_alloc_folio gives us a folio with a non-NULL ->private Jeff Layton
2022-05-13 14:47 ` Matthew Wilcox [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=Yn5vmh0WbhczfURJ@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jlayton@kernel.org \
    --cc=lhenriques@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=xiubli@redhat.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 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.