From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] f2fs: remove folio_detach_private() in .invalidate_folio and .release_folio
Date: Tue, 11 Apr 2023 16:34:05 +0800 [thread overview]
Message-ID: <b05d7ce8-ef98-a7ef-9873-4403ec0858c1@kernel.org> (raw)
In-Reply-To: <ZDRWdJxP6QzcIU7G@google.com>
On 2023/4/11 2:33, Jaegeuk Kim wrote:
> On 04/10, Chao Yu wrote:
>> We have maintain PagePrivate and page_private and page reference
>> w/ {set,clear}_page_private_*, it doesn't need to call
>> folio_detach_private() in the end of .invalidate_folio and
>> .release_folio, remove it and use f2fs_bug_on instead.
>>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> fs/f2fs/data.c | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>> index 4946df6dd253..8b179b4bdc03 100644
>> --- a/fs/f2fs/data.c
>> +++ b/fs/f2fs/data.c
>> @@ -3737,7 +3737,8 @@ void f2fs_invalidate_folio(struct folio *folio, size_t offset, size_t length)
>> inode->i_ino == F2FS_COMPRESS_INO(sbi))
>> clear_page_private_data(&folio->page);
>>
>> - folio_detach_private(folio);
>> + f2fs_bug_on(sbi, PagePrivate(&folio->page));
>> + f2fs_bug_on(sbi, page_private(&folio->page));
>
> I think we can just check page_private() only.
Why? how about the case PagePrivate was set, but page_private was't? It must
be a bug as well?
Thanks,
>
>> }
>>
>> bool f2fs_release_folio(struct folio *folio, gfp_t wait)
>> @@ -3759,7 +3760,9 @@ bool f2fs_release_folio(struct folio *folio, gfp_t wait)
>> clear_page_private_reference(&folio->page);
>> clear_page_private_gcing(&folio->page);
>>
>> - folio_detach_private(folio);
>> + f2fs_bug_on(sbi, PagePrivate(&folio->page));
>> + f2fs_bug_on(sbi, page_private(&folio->page));
>> +
>> return true;
>> }
>>
>> --
>> 2.25.1
next prev parent reply other threads:[~2023-04-11 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 2:24 Chao Yu
2023-04-10 2:24 ` [PATCH 2/2] f2fs: clean up with {attach,detach}_page_private() Chao Yu
2023-04-10 18:47 ` Jaegeuk Kim
2023-04-11 8:37 ` Chao Yu
2023-04-10 18:33 ` [PATCH 1/2] f2fs: remove folio_detach_private() in .invalidate_folio and .release_folio Jaegeuk Kim
2023-04-11 8:34 ` Chao Yu [this message]
2023-04-11 16:58 ` Jaegeuk Kim
2023-04-12 16:16 ` [f2fs-dev] " Jaegeuk Kim
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=b05d7ce8-ef98-a7ef-9873-4403ec0858c1@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®