linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: Sidhartha Kumar <sidhartha.kumar@oracle.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, usama.anjum@collabora.com,
	jiaqiyan@google.com, linmiaohe@huawei.com,
	naoya.horiguchi@nec.com, shy828301@gmail.com,
	jthoughton@google.com, jane.chu@oracle.com,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] fs/hugetlbfs/inode.c: mm/memory-failure.c: fix hugetlbfs hwpoison handling
Date: Mon, 15 Jan 2024 15:08:10 +0000	[thread overview]
Message-ID: <ZaVKWox1/yTLThma@casper.infradead.org> (raw)
In-Reply-To: <03168121-080f-41e4-a242-02638f5787f7@linux.dev>

On Mon, Jan 15, 2024 at 08:02:51PM +0800, Muchun Song wrote:
> On 2024/1/13 02:08, Sidhartha Kumar wrote:
> > has_extra_refcount() makes the assumption that the page cache adds a ref
> > count of 1 and subtracts this in the extra_pins case. Commit a08c7193e4f1
> > (mm/filemap: remove hugetlb special casing in filemap.c) modifies
> > __filemap_add_folio() by calling folio_ref_add(folio, nr); for all cases
> > (including hugtetlb) where nr is the number of pages in the folio. We
> > should adjust the number of references coming from the page cache by
> > subtracing the number of pages rather than 1.
> > 
> > In hugetlbfs_read_iter(), folio_test_has_hwpoisoned() is testing the wrong
> > flag as, in the hugetlb case, memory-failure code calls
> > folio_test_set_hwpoison() to indicate poison. folio_test_hwpoison() is the
> > correct function to test for that flag.
> > 
> > After these fixes, the hugetlb hwpoison read selftest passes all cases.
> > 
> > Fixes: a08c7193e4f1 ("mm/filemap: remove hugetlb special casing in filemap.c")
> > Closes: https://lore.kernel.org/linux-mm/20230713001833.3778937-1-jiaqiyan@google.com/T/#m8e1469119e5b831bbd05d495f96b842e4a1c5519
> > Cc: <stable@vger.kernel.org> # 6.7+
> > Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
> > Reported-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> > ---
> > 
> > v1 -> v2:
> >      move ref_count adjustment to if(extra_pins) block as that represents
> >      ref counts from the page cache per Miaohe Lin.
> > 
> >   fs/hugetlbfs/inode.c | 2 +-
> >   mm/memory-failure.c  | 2 +-
> >   2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> > index 36132c9125f9..3a248e4f7e93 100644
> > --- a/fs/hugetlbfs/inode.c
> > +++ b/fs/hugetlbfs/inode.c
> > @@ -340,7 +340,7 @@ static ssize_t hugetlbfs_read_iter(struct kiocb *iocb, struct iov_iter *to)
> >   		} else {
> >   			folio_unlock(folio);
> > -			if (!folio_test_has_hwpoisoned(folio))
> > +			if (!folio_test_hwpoison(folio))
> >   				want = nr;
> >   			else {
> >   				/*
> > diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> > index d8c853b35dbb..ef7ae73b65bd 100644
> > --- a/mm/memory-failure.c
> > +++ b/mm/memory-failure.c
> > @@ -976,7 +976,7 @@ static bool has_extra_refcount(struct page_state *ps, struct page *p,
> >   	int count = page_count(p) - 1;
> >   	if (extra_pins)
> > -		count -= 1;
> > +		count -= folio_nr_pages(page_folio(p));
> 
> IIUC, It seems than this also fix shmem of THP, because has_extra_refcount()
> is called
> from me_pagecache_clean(), right?

Usually we split THPs before we get to this point, but we always poison
an entire hugetlb page.  This should probably change, but it's not high
on my list of things to do.

  reply	other threads:[~2024-01-15 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 18:08 [PATCH v2] fs/hugetlbfs/inode.c: mm/memory-failure.c: fix hugetlbfs hwpoison handling Sidhartha Kumar
2024-01-15  7:49 ` Muhammad Usama Anjum
2024-01-15 12:02 ` Muchun Song
2024-01-15 15:08   ` Matthew Wilcox [this message]
2024-01-16  2:36 ` Miaohe Lin
2024-01-16  2:43 ` Muchun Song

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=ZaVKWox1/yTLThma@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=jane.chu@oracle.com \
    --cc=jiaqiyan@google.com \
    --cc=jthoughton@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=naoya.horiguchi@nec.com \
    --cc=shy828301@gmail.com \
    --cc=sidhartha.kumar@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).