From: "Raphael S. Carvalho" <raphaelsc@scylladb.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
djwong@kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v2] mm: Fix error handling in __filemap_get_folio() with FGP_NOWAIT
Date: Tue, 25 Feb 2025 13:04:04 -0300 [thread overview]
Message-ID: <CAKhLTr1HtH7gnSKSE+8LR9+MpNGYK0PYr8NGSTav-0sgf4y+gw@mail.gmail.com> (raw)
In-Reply-To: <CAKhLTr0bG6Xxvvjai0UQTfEnR53sU2EMWQKsC033QAfbW1OugQ@mail.gmail.com>
On Mon, Feb 24, 2025 at 1:15 PM Raphael S. Carvalho
<raphaelsc@scylladb.com> wrote:
>
> On Mon, Feb 24, 2025 at 1:02 PM Christoph Hellwig <hch@lst.de> wrote:
> >
> > On Mon, Feb 24, 2025 at 03:33:29PM +0000, Matthew Wilcox wrote:
> > > I don't think it needs a comment at all, but the memory allocation
> > > might be for something other than folios, so your suggested comment
> > > is misleading.
> >
> > Then s/folio/memory/
>
> The context of the comment is error handling. ENOMEM can come from
> either folio allocation / addition (there's an allocation for xarray
> node). So is it really wrong to say folios given the context of the
> comment? It's not supposed to be a generic comment, but rather one
> that applies to its context.
>
> Maybe this change:
> - * When NOWAIT I/O fails to allocate folios this could
> + * When NOWAIT I/O fails to allocate memory for folio
>
> Or perhaps just what hch suggested.
Matthew, please let me know what you think, so we can move forward
with this. Thanks.
prev parent reply other threads:[~2025-02-25 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 8:13 Raphael S. Carvalho
2025-02-24 14:17 ` Christoph Hellwig
2025-02-24 15:33 ` Matthew Wilcox
2025-02-24 15:45 ` Raphael S. Carvalho
2025-02-24 15:49 ` Matthew Wilcox
2025-02-24 15:50 ` Raphael S. Carvalho
2025-02-24 15:51 ` Matthew Wilcox
2025-02-24 15:52 ` Raphael S. Carvalho
2025-02-24 15:56 ` Christoph Hellwig
2025-02-24 16:02 ` Christoph Hellwig
2025-02-24 16:15 ` Raphael S. Carvalho
2025-02-25 16:04 ` Raphael S. Carvalho [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=CAKhLTr1HtH7gnSKSE+8LR9+MpNGYK0PYr8NGSTav-0sgf4y+gw@mail.gmail.com \
--to=raphaelsc@scylladb.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--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