linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jiaqi Yan <jiaqiyan@google.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: songmuchun@bytedance.com, naoya.horiguchi@nec.com,
	shy828301@gmail.com,  linmiaohe@huawei.com,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org, duenwen@google.com,
	axelrasmussen@google.com,  jthoughton@google.com
Subject: Re: [PATCH v1 2/3] hugetlbfs: improve read HWPOISON hugepage
Date: Fri, 19 May 2023 13:54:21 -0700	[thread overview]
Message-ID: <CACw3F53+Hg4CgFoPj3LLSiURzWfa2egWLO-=12GzfhsNC3XTvQ@mail.gmail.com> (raw)
In-Reply-To: <20230518221808.GC4029@monkey>

On Thu, May 18, 2023 at 3:18 PM Mike Kravetz <mike.kravetz@oracle.com> wrote:
>
> On 05/17/23 16:09, Jiaqi Yan wrote:
> > When a hugepage contains HWPOISON pages, read() fails to read any byte
> > of the hugepage and returns -EIO, although many bytes in the HWPOISON
> > hugepage are readable.
> >
> > Improve this by allowing hugetlbfs_read_iter returns as many bytes as
> > possible. For a requested range [offset, offset + len) that contains
> > HWPOISON page, return [offset, first HWPOISON page addr); the next read
> > attempt will fail and return -EIO.
> >
> > Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
> > ---
> >  fs/hugetlbfs/inode.c | 62 +++++++++++++++++++++++++++++++++++++++-----
> >  1 file changed, 56 insertions(+), 6 deletions(-)
> >
> > diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> > index ecfdfb2529a3..1baa08ec679f 100644
> > --- a/fs/hugetlbfs/inode.c
> > +++ b/fs/hugetlbfs/inode.c
> > @@ -282,6 +282,46 @@ hugetlb_get_unmapped_area(struct file *file, unsigned long addr,
> >  }
> >  #endif
> >
> > +/*
> > + * Someone wants to read @bytes from a HWPOISON hugetlb @page from @offset.
> > + * Returns the maximum number of bytes one can read without touching the 1st raw
> > + * HWPOISON subpage.
> > + *
> > + * The implementation borrows the iteration logic from copy_page_to_iter*.
> > + */
> > +static size_t adjust_range_hwpoison(struct page *page, size_t offset, size_t bytes)
> > +{
> > +     size_t n = 0;
> > +     size_t res = 0;
> > +     struct folio *folio = page_folio(page);
> > +
> > +     folio_lock(folio);
>
> What is the reason for taking folio_lock?

I intended to make this routine (mostly find_raw_hwp_page) to be
serialized with folio_clear_hugetlb_hwpoison() and
hwpoison_user_mappings() in try_memory_failure_hugetlb(). They don't
directly affect the raw_hwp_list. I can remove the lock in v2.

>
> > +
> > +     /* First subpage to start the loop. */
> > +     page += offset / PAGE_SIZE;
> > +     offset %= PAGE_SIZE;
> > +     while (1) {
> > +             if (find_raw_hwp_page(folio, page) != NULL)
> > +                     break;
> > +
> > +             /* Safe to read n bytes without touching HWPOISON subpage. */
> > +             n = min(bytes, (size_t)PAGE_SIZE - offset);
> > +             res += n;
> > +             bytes -= n;
> > +             if (!bytes || !n)
> > +                     break;
> > +             offset += n;
> > +             if (offset == PAGE_SIZE) {
> > +                     page++;
> > +                     offset = 0;
> > +             }
> > +     }
> > +
> > +     folio_unlock(folio);
> > +
> > +     return res;
> > +}
> > +
> >  /*
> >   * Support for read() - Find the page attached to f_mapping and copy out the
> >   * data. This provides functionality similar to filemap_read().
> > @@ -300,7 +340,7 @@ static ssize_t hugetlbfs_read_iter(struct kiocb *iocb, struct iov_iter *to)
> >
> >       while (iov_iter_count(to)) {
> >               struct page *page;
> > -             size_t nr, copied;
> > +             size_t nr, copied, want;
> >
> >               /* nr is the maximum number of bytes to copy from this page */
> >               nr = huge_page_size(h);
> > @@ -328,16 +368,26 @@ static ssize_t hugetlbfs_read_iter(struct kiocb *iocb, struct iov_iter *to)
> >               } else {
> >                       unlock_page(page);
> >
> > -                     if (PageHWPoison(page)) {
> > -                             put_page(page);
> > -                             retval = -EIO;
> > -                             break;
> > +                     if (!PageHWPoison(page))
> > +                             want = nr;
> > +                     else {
> > +                             /*
> > +                              * Adjust how many bytes safe to read without
> > +                              * touching the 1st raw HWPOISON subpage after
> > +                              * offset.
> > +                              */
> > +                             want = adjust_range_hwpoison(page, offset, nr);
> > +                             if (want == 0) {
> > +                                     put_page(page);
> > +                                     retval = -EIO;
> > +                                     break;
> > +                             }
> >                       }
> >
> >                       /*
> >                        * We have the page, copy it to user space buffer.
> >                        */
> > -                     copied = copy_page_to_iter(page, offset, nr, to);
> > +                     copied = copy_page_to_iter(page, offset, want, to);
> >                       put_page(page);
> >               }
> >               offset += copied;
> > --
> > 2.40.1.606.ga4b1b128d6-goog
> >
>
> Code looks fine, just wondering about that folio_lock.
> --
> Mike Kravetz


  reply	other threads:[~2023-05-19 20:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 16:09 [PATCH v1 0/3] Improve hugetlbfs read on HWPOISON hugepages Jiaqi Yan
2023-05-17 16:09 ` [PATCH v1 1/3] mm/hwpoison: find subpage in hugetlb HWPOISON list Jiaqi Yan
2023-05-17 23:53   ` Mike Kravetz
2023-05-19 20:54     ` Jiaqi Yan
2023-05-19 22:42       ` Mike Kravetz
2023-05-22  4:50         ` HORIGUCHI NAOYA(堀口 直也)
2023-05-22 18:22           ` Jiaqi Yan
2023-05-23  2:43             ` HORIGUCHI NAOYA(堀口 直也)
2023-05-26  0:28               ` Jiaqi Yan
2023-06-10  5:48                 ` Jiaqi Yan
2023-06-12  4:19                   ` Naoya Horiguchi
2023-06-16 21:19                     ` Jiaqi Yan
2023-06-16 23:34                       ` Mike Kravetz
2023-06-17  2:18                         ` Jiaqi Yan
2023-06-17 22:59                           ` Mike Kravetz
2023-06-19  8:23                             ` Naoya Horiguchi
2023-06-20 18:05                               ` Mike Kravetz
2023-06-20 22:39                                 ` Mike Kravetz
2023-06-23  0:45                                   ` Jiaqi Yan
2023-06-23  4:19                                     ` Mike Kravetz
2023-06-23 16:40                                       ` Jiaqi Yan
2023-05-17 16:09 ` [PATCH v1 2/3] hugetlbfs: improve read HWPOISON hugepage Jiaqi Yan
2023-05-18 22:18   ` Mike Kravetz
2023-05-19 20:54     ` Jiaqi Yan [this message]
2023-05-17 16:09 ` [PATCH v1 3/3] selftests/mm: add tests for HWPOISON hugetlbfs read Jiaqi Yan
2023-05-23  7:35   ` kernel test robot
2023-05-17 23:30 ` [PATCH v1 0/3] Improve hugetlbfs read on HWPOISON hugepages Mike Kravetz
2023-05-18 16:02   ` Jiaqi Yan
2023-05-18 16:10   ` Jiaqi Yan
2023-05-18 22:24     ` Mike Kravetz

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='CACw3F53+Hg4CgFoPj3LLSiURzWfa2egWLO-=12GzfhsNC3XTvQ@mail.gmail.com' \
    --to=jiaqiyan@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=duenwen@google.com \
    --cc=jthoughton@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=shy828301@gmail.com \
    --cc=songmuchun@bytedance.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