From: Eric Biggers <ebiggers@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
dm-devel@lists.linux.dev, Ondrej Kozina <okozina@redhat.com>,
Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH] dm-verity: fix unreliable memory allocation
Date: Fri, 21 Nov 2025 01:46:31 +0000 [thread overview]
Message-ID: <20251121014631.GA3078357@google.com> (raw)
In-Reply-To: <0da5850a-05ee-6cff-3c25-e2c9037c52eb@redhat.com>
On Mon, Nov 17, 2025 at 09:42:02PM +0100, Mikulas Patocka wrote:
> GFP_NOWAIT allocation may fail anytime. It needs to be changed to
> GFP_NOIO. There's no need to handle an error because mempool_alloc with
> GFP_NOIO can't fail.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable@vger.kernel.org
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
prev parent reply other threads:[~2025-11-21 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:42 [PATCH] dm-verity: fix unreliable memory allocation Mikulas Patocka
2025-11-21 1:46 ` Eric Biggers [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=20251121014631.GA3078357@google.com \
--to=ebiggers@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=gmazyland@gmail.com \
--cc=mpatocka@redhat.com \
--cc=okozina@redhat.com \
--cc=samitolvanen@google.com \
--cc=snitzer@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.