linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nhat Pham <nphamcs@gmail.com>
To: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
	chengming.zhou@linux.dev,  linux-mm@kvack.org,
	kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] page_io: return proper error codes for swap_read_folio_zeromap()
Date: Fri, 7 Mar 2025 09:03:33 -0800	[thread overview]
Message-ID: <CAKEwX=P+Oh+a0Pducc9v1EGsGVG4vi1RT4xywkvhnnA2hEpzCw@mail.gmail.com> (raw)
In-Reply-To: <Z8oy0A-vBbGI6ux9@google.com>

On Thu, Mar 6, 2025 at 3:42 PM Yosry Ahmed <yosry.ahmed@linux.dev> wrote:
>
> > + *
> > + *  -EINVAL: some of the subpages in the folio are zeromaped, but not all of
> > + *  them. This is an error because we don't currently support a large folio
> > + *  that is partially in the zeromap. The folio is unlocked, but NOT marked
> > + *  up-to-date, so that an IO error is emitted (e.g. do_swap_page() will
> > + *  sigbus).
>
> This is a bit repetitive. Maybe:
>
>  *  -EINVAL: The folio is partially in the zeromap, which is not
>  *  currently supported. The folio is unlocked, but NOT marked
>  *  up-to-date, so that an IO error is emitted (e.g. do_swap_page() will
>  *  sigbus).
>
>
>
> I would drop this whole comment now because it's mostly repeating what's
> now documneted above.
>
> With the comments fixed up:
>
> Reviewed-by: Yosry Ahmed <yosry.ahmed@linux.dev>
>

Ah I like both suggestions :) Gimme one sec to send out a fixlet.

Thanks, Yosry!


  reply	other threads:[~2025-03-07 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 23:00 Nhat Pham
2025-03-06 23:42 ` Yosry Ahmed
2025-03-07 17:03   ` Nhat Pham [this message]
2025-03-07  1:38 ` Johannes Weiner
2025-03-07  3:08 ` Chengming Zhou
2025-03-07 23:34 ` [PATCH] page_io: return proper error codes for swap_read_folio_zeromap() (fix) Nhat Pham
2025-04-01 18:55 ` [PATCH] page_io: return proper error codes for swap_read_folio_zeromap() Nhat Pham
2025-04-01 19:01   ` Andrew Morton

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='CAKEwX=P+Oh+a0Pducc9v1EGsGVG4vi1RT4xywkvhnnA2hEpzCw@mail.gmail.com' \
    --to=nphamcs@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chengming.zhou@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yosry.ahmed@linux.dev \
    /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