From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, linux-mm@kvack.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs: initialize page->private when using for our internal use
Date: Mon, 5 Jul 2021 19:33:35 +0800 [thread overview]
Message-ID: <e2fdf628-f25c-7495-cfd1-952899f7ff9a@kernel.org> (raw)
In-Reply-To: <YOLJW0IgCagMk2tF@google.com>
On 2021/7/5 16:56, Jaegeuk Kim wrote:
> On 07/05, Chao Yu wrote:
>> On 2021/7/5 13:22, Jaegeuk Kim wrote:
>>> We need to guarantee it's initially zero. Otherwise, it'll hurt entire flag
>>> operations.
>>
>> Oops, I didn't get the point, shouldn't .private be zero after page was
>> just allocated by filesystem? What's the case we will encounter stall
>> private data left in page?
>
> I'm seeing f2fs_migrate_page() has the newpage with some value without Private
> flag. That causes a kernel panic later due to wrong private flag used in f2fs.
I'm not familiar with that part of codes, so Cc mm mailing list for help.
My question is newpage in .migrate_page() may contain non-zero value in .private
field but w/o setting PagePrivate flag, is it a normal case?
Thanks,
>
>>
>> Cc Matthew Wilcox.
>>
>> Thanks,
>>
>>>
>>> Fixes: b763f3bedc2d ("f2fs: restructure f2fs page.private layout")
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>> fs/f2fs/data.c | 2 ++
>>> fs/f2fs/f2fs.h | 5 ++++-
>>> 2 files changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>>> index 3a01a1b50104..d2cf48c5a2e4 100644
>>> --- a/fs/f2fs/data.c
>>> +++ b/fs/f2fs/data.c
>>> @@ -3819,6 +3819,8 @@ int f2fs_migrate_page(struct address_space *mapping,
>>> get_page(newpage);
>>> }
>>> + /* guarantee to start from no stale private field */
>>> + set_page_private(newpage, 0);
>>> if (PagePrivate(page)) {
>>> set_page_private(newpage, page_private(page));
>>> SetPagePrivate(newpage);
>>> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
>>> index 65befc68d88e..ee8eb33e2c25 100644
>>> --- a/fs/f2fs/f2fs.h
>>> +++ b/fs/f2fs/f2fs.h
>>> @@ -1331,7 +1331,8 @@ enum {
>>> #define PAGE_PRIVATE_GET_FUNC(name, flagname) \
>>> static inline bool page_private_##name(struct page *page) \
>>> { \
>>> - return test_bit(PAGE_PRIVATE_NOT_POINTER, &page_private(page)) && \
>>> + return PagePrivate(page) && \
>>> + test_bit(PAGE_PRIVATE_NOT_POINTER, &page_private(page)) && \
>>> test_bit(PAGE_PRIVATE_##flagname, &page_private(page)); \
>>> }
>>> @@ -1341,6 +1342,7 @@ static inline void set_page_private_##name(struct page *page) \
>>> if (!PagePrivate(page)) { \
>>> get_page(page); \
>>> SetPagePrivate(page); \
>>> + set_page_private(page, 0); \
>>> } \
>>> set_bit(PAGE_PRIVATE_NOT_POINTER, &page_private(page)); \
>>> set_bit(PAGE_PRIVATE_##flagname, &page_private(page)); \
>>> @@ -1392,6 +1394,7 @@ static inline void set_page_private_data(struct page *page, unsigned long data)
>>> if (!PagePrivate(page)) {
>>> get_page(page);
>>> SetPagePrivate(page);
>>> + set_page_private(page, 0);
>>> }
>>> set_bit(PAGE_PRIVATE_NOT_POINTER, &page_private(page));
>>> page_private(page) |= data << PAGE_PRIVATE_MAX;
>>>
next parent reply other threads:[~2021-07-05 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210705052216.831989-1-jaegeuk@kernel.org>
[not found] ` <c32642d6-6de2-eb2d-5771-c7cefa62fab5@kernel.org>
[not found] ` <YOLJW0IgCagMk2tF@google.com>
2021-07-05 11:33 ` Chao Yu [this message]
2021-07-05 11:47 ` Matthew Wilcox
2021-07-05 16:09 ` Chao Yu
2021-07-05 18:06 ` Jaegeuk Kim
2021-07-06 0:16 ` Chao Yu
2021-07-05 18:04 ` Jaegeuk Kim
2021-07-05 18:45 ` Matthew Wilcox
2021-07-06 9:12 ` Mel Gorman
2021-07-07 0:48 ` Chao Yu
2021-07-07 9:57 ` Mel Gorman
2021-07-10 8:11 ` Chao Yu
2021-07-12 6:53 ` Michal Hocko
2021-07-13 0:46 ` Chao Yu
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=e2fdf628-f25c-7495-cfd1-952899f7ff9a@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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