From: Johannes Weiner <hannes@cmpxchg.org>
To: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: Nhat Pham <nphamcs@gmail.com>,
akpm@linux-foundation.org, chengming.zhou@linux.dev,
linux-mm@kvack.org, kernel-team@meta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] zswap: do not crash the kernel on decompression failure
Date: Wed, 26 Feb 2025 23:31:41 -0500 [thread overview]
Message-ID: <20250227043141.GB110982@cmpxchg.org> (raw)
In-Reply-To: <Z7-9o81kBfw4tFSz@google.com>
On Thu, Feb 27, 2025 at 01:19:31AM +0000, Yosry Ahmed wrote:
> On Wed, Feb 26, 2025 at 04:14:45PM -0800, Nhat Pham wrote:
> > if (WARN_ON_ONCE(folio_test_large(folio)))
> > return true;
> >
> > + entry = xa_load(tree, offset);
> > + if (!entry)
> > + return false;
> > +
>
> A small comment here pointing out that we are deliberatly not setting
> uptodate because of the failure may make things more obvious, or do you
> think that's not needed?
>
> > + if (!zswap_decompress(entry, folio))
> > + return true;
How about an actual -ev and have this in swap_read_folio():
ret = zswap_load(folio);
if (ret != -ENOENT) {
folio_unlock(folio);
goto finish;
}
read from swapfile...
Then in zswap_load(), move uptodate further up like this (I had
previously suggested this):
if (!zswap_decompress(entry, folio))
return -EIO;
folio_mark_uptodate(folio);
and I think it would be clear, even without or just minimal comments.
next prev parent reply other threads:[~2025-02-27 4:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:14 Nhat Pham
2025-02-27 1:19 ` Yosry Ahmed
2025-02-27 4:31 ` Johannes Weiner [this message]
2025-02-27 5:44 ` Yosry Ahmed
2025-02-27 6:16 ` Johannes Weiner
2025-02-27 7:11 ` Yosry Ahmed
2025-02-27 7:29 ` Yosry Ahmed
2025-02-27 16:05 ` Johannes Weiner
2025-02-27 18:01 ` Yosry Ahmed
2025-02-27 22:35 ` Nhat Pham
2025-02-27 21:46 ` Nhat Pham
2025-02-27 21:55 ` Yosry Ahmed
2025-03-01 2:08 ` Nhat Pham
2025-03-01 2:20 ` Yosry Ahmed
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=20250227043141.GB110982@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--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