From: Eric Biggers <ebiggers@kernel.org>
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
"open list:FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT"
<linux-fscrypt@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
willy@infradead.org
Subject: Re: [PATCH 2/4] fscrypto: Remove redundant __GFP_NOWARN
Date: Mon, 11 Aug 2025 10:31:03 -0700 [thread overview]
Message-ID: <20250811173103.GC1268@sol> (raw)
In-Reply-To: <20250803102243.623705-3-rongqianfeng@vivo.com>
On Sun, Aug 03, 2025 at 06:22:40PM +0800, Qianfeng Rong wrote:
> GFP_NOWAIT already includes __GFP_NOWARN, so let's remove
> the redundant __GFP_NOWARN.
>
> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
> ---
> fs/crypto/bio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/crypto/bio.c b/fs/crypto/bio.c
> index 486fcb2ecf13..e92967e20e2a 100644
> --- a/fs/crypto/bio.c
> +++ b/fs/crypto/bio.c
> @@ -148,7 +148,7 @@ int fscrypt_zeroout_range(const struct inode *inode, pgoff_t lblk,
> */
> for (i = 0; i < nr_pages; i++) {
> pages[i] = fscrypt_alloc_bounce_page(i == 0 ? GFP_NOFS :
> - GFP_NOWAIT | __GFP_NOWARN);
> + GFP_NOWAIT);
> if (!pages[i])
> break;
> }
> --
> 2.34.1
>
Applied to https://git.kernel.org/pub/scm/fs/fscrypt/linux.git/log/?h=for-next
Thanks!
- Eric
next prev parent reply other threads:[~2025-08-11 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 10:22 [PATCH 0/4] fs: Remove redundant __GFP_NOWARN Qianfeng Rong
2025-08-03 10:22 ` [PATCH 1/4] bcachefs: " Qianfeng Rong
2025-08-03 17:18 ` Kent Overstreet
2025-08-03 10:22 ` [PATCH 2/4] fscrypto: " Qianfeng Rong
2025-08-11 17:31 ` Eric Biggers [this message]
2025-08-03 10:22 ` [PATCH 3/4] ext4: " Qianfeng Rong
2025-08-03 10:22 ` [PATCH 4/4] fs-writeback: " Qianfeng Rong
2025-08-15 14:06 ` (subset) " Christian Brauner
2025-08-14 14:48 ` [PATCH 0/4] fs: " Theodore Ts'o
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=20250811173103.GC1268@sol \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=tytso@mit.edu \
--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 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.