cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] return an ERR_PTR from __filemap_get_folio v2
Date: Thu, 30 Mar 2023 01:56:15 +0200	[thread overview]
Message-ID: <20230329235615.GA2012@lst.de> (raw)
In-Reply-To: <20230328160433.4f3dc32b480239bce9e2f9ef@linux-foundation.org>

On Tue, Mar 28, 2023 at 04:04:33PM -0700, Andrew Morton wrote:
> > Note that the shmem patches in here are non-trivial and need some
> > careful review and testing.
> 
> How are we going with the review and testing.  I assume that
> we're now OK on the runtime testing front, but do you feel that
> review has been adequate?

Yes, I think we're fine, mostly due to Hugh.  I'm a little sad about
the simplification / descoping from him, but at least we get the main
objective done.  Maybe at some point we can do another pass at
cleaning up the shmem page finding/reading mess.


      reply	other threads:[~2023-03-29 23:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  6:57 [Cluster-devel] return an ERR_PTR from __filemap_get_folio v2 Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 1/7] mm: don't look at xarray value entries in split_huge_pages_in_file Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 2/7] mm: make mapping_get_entry available outside of filemap.c Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 3/7] mm: use filemap_get_entry in filemap_get_incore_folio Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 4/7] shmem: remove shmem_get_partial_folio Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 5/7] shmem: open code the page cache lookup in shmem_get_folio_gfp Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 6/7] mm: remove FGP_ENTRY Christoph Hellwig
2023-01-21  6:57 ` [Cluster-devel] [PATCH 7/7] mm: return an ERR_PTR from __filemap_get_folio Christoph Hellwig
2023-01-21 11:52   ` kernel test robot
2023-01-21 14:28     ` Christoph Hellwig
2023-01-23 15:44   ` David Sterba
2023-01-26 17:24   ` Ryusuke Konishi
2023-03-10  4:31   ` Naoya Horiguchi
2023-03-10  7:00     ` Christoph Hellwig
2023-03-10  8:02       ` Naoya Horiguchi
2023-01-22  1:06 ` [Cluster-devel] return an ERR_PTR from __filemap_get_folio v2 Andrew Morton
2023-01-22  7:20   ` Christoph Hellwig
2023-01-23 18:59     ` Andrew Morton
2023-01-23 19:18       ` Christoph Hellwig
2023-03-28 23:04 ` Andrew Morton
2023-03-29 23:56   ` Christoph Hellwig [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=20230329235615.GA2012@lst.de \
    --to=hch@lst.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).