Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jane.chu@oracle.com
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Cc: Muchun Song <muchun.song@linux.dev>,
	Oscar Salvador <osalvador@suse.de>,
	David Hildenbrand <david@kernel.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/4] Use generic_file_read_iter() in hugetlbfs
Date: Wed, 8 Jul 2026 16:31:48 -0700	[thread overview]
Message-ID: <f879bb87-0267-451b-bfed-a3e4b475b9ea@oracle.com> (raw)
In-Reply-To: <20260707181713.208282-1-willy@infradead.org>



On 7/7/2026 11:17 AM, Matthew Wilcox (Oracle) wrote:
> This set of patches are separated out from Jane's earlier series.
> https://lore.kernel.org/linux-mm/20260617172534.1740152-1-jane.chu@oracle.com/
> I feel that they represent a reasonable amount of change to send
> separately, although I'm going to keep looking at the rest of the sseries
> because I actually need it to do a further improvement that I'm working on.
> 
> I'm not 100% confident in all of this, so I'd appreciate feedback.
> I've run the libhugetlbfs test suite against it and observe no new
> failures, but I'm not sure it's thoroughly exercising the read() path,
> and I'm absolutely certain it's not exercising the memory-failure paths.

I can help testing memory-failure once I finish the stuff at hand.

-jane

> 
> Jane Chu (2):
>    filemap: add hwpoison handling to filemap_read()
>    hugetlbfs: replace hugetlbfs_read_iter() with generic_file_read_iter()
> 
> Matthew Wilcox (Oracle) (2):
>    hugetlbfs: Set mapping folio order
>    mm: Handle hugetlb correctly in is_page_hwpoison()
> 
>   fs/hugetlbfs/inode.c       | 122 ++++---------------------------------
>   include/linux/hugetlb.h    |   5 --
>   include/linux/page-flags.h |  24 ++++++--
>   mm/filemap.c               |  31 ++++++++++
>   mm/memory-failure.c        |   9 ++-
>   5 files changed, 66 insertions(+), 125 deletions(-)
> 



  parent reply	other threads:[~2026-07-08 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 18:17 [PATCH 0/4] Use generic_file_read_iter() in hugetlbfs Matthew Wilcox (Oracle)
2026-07-07 18:17 ` [PATCH 1/4] hugetlbfs: Set mapping folio order Matthew Wilcox (Oracle)
2026-07-07 18:17 ` [PATCH 2/4] mm: Handle hugetlb correctly in is_page_hwpoison() Matthew Wilcox (Oracle)
2026-07-07 18:17 ` [PATCH 3/4] filemap: add hwpoison handling to filemap_read() Matthew Wilcox (Oracle)
2026-07-07 18:17 ` [PATCH 4/4] hugetlbfs: replace hugetlbfs_read_iter() with generic_file_read_iter() Matthew Wilcox (Oracle)
2026-07-08 23:31 ` jane.chu [this message]
2026-07-09  3:07   ` [PATCH 0/4] Use generic_file_read_iter() in hugetlbfs Matthew Wilcox
2026-07-09  5:56     ` jane.chu

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=f879bb87-0267-451b-bfed-a3e4b475b9ea@oracle.com \
    --to=jane.chu@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox