From: Chao Yu <chao@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/2] f2fs: quota: do not use GFP_NOFS in f2fs_quota_read()
Date: Tue, 7 Jul 2026 09:58:08 +0800 [thread overview]
Message-ID: <dcc490cd-01f5-4d11-84e0-f37efd1b6b47@kernel.org> (raw)
In-Reply-To: <akulrzxMUbI5Kr3D@casper.infradead.org>
On 7/6/26 20:55, Matthew Wilcox wrote:
> On Mon, Jul 06, 2026 at 05:59:42PM +0800, Chao Yu wrote:
>> - folio = mapping_read_folio_gfp(mapping, off >> PAGE_SHIFT,
>> - GFP_NOFS);
>> + folio = mapping_read_folio_gfp(mapping, off >> PAGE_SHIFT, 0);
>
> 0? Surely you mean GFP_KERNEL?
Oops, my bad, it should be GFP_KERNEL.
Thanks,
prev parent reply other threads:[~2026-07-07 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:59 Chao Yu
2026-07-06 9:59 ` [PATCH 2/2] f2fs: quota: use memalloc_nofs_{save,restore} instead of FGP_NOFS Chao Yu
2026-07-06 14:18 ` Matthew Wilcox
2026-07-07 9:44 ` Chao Yu
2026-07-07 9:53 ` Chao Yu
2026-07-06 12:55 ` [PATCH 1/2] f2fs: quota: do not use GFP_NOFS in f2fs_quota_read() Matthew Wilcox
2026-07-07 1:58 ` Chao Yu [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=dcc490cd-01f5-4d11-84e0-f37efd1b6b47@kernel.org \
--to=chao@kernel.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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