From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: =?utf-8?b?6buE5L2z55S3IDxodWFuZ2ppYW5hbkB4aWFvbWkuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: shengyong1@xiaomi.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
wanghui33@xiaomi.com
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: avoid reading already updated pages during GC
Date: Thu, 05 Mar 2026 19:10:13 +0000 [thread overview]
Message-ID: <177273781304.3248266.12940471035367152097.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305011810.4189655-1-huangjianan@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 5 Mar 2026 09:18:10 +0800 you wrote:
> We found the following issue during fuzz testing:
>
> page: refcount:3 mapcount:0 mapping:00000000b6e89c65 index:0x18b2dc pfn:0x161ba9
> memcg:f8ffff800e269c00
> aops:f2fs_meta_aops ino:2
> flags: 0x52880000000080a9(locked|waiters|uptodate|lru|private|zone=1|kasantag=0x4a)
> raw: 52880000000080a9 fffffffec6e17588 fffffffec0ccc088 a7ffff8067063618
> raw: 000000000018b2dc 0000000000000009 00000003ffffffff f8ffff800e269c00
> page dumped because: VM_BUG_ON_FOLIO(folio_test_uptodate(folio))
> page_owner tracks the page as allocated
> post_alloc_hook+0x58c/0x5ec
> prep_new_page+0x34/0x284
> get_page_from_freelist+0x2dcc/0x2e8c
> __alloc_pages_noprof+0x280/0x76c
> __folio_alloc_noprof+0x18/0xac
> __filemap_get_folio+0x6bc/0xdc4
> pagecache_get_page+0x3c/0x104
> do_garbage_collect+0x5c78/0x77a4
> f2fs_gc+0xd74/0x25f0
> gc_thread_func+0xb28/0x2930
> kthread+0x464/0x5d8
> ret_from_fork+0x10/0x20
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: avoid reading already updated pages during GC
https://git.kernel.org/jaegeuk/f2fs/c/5d143972155e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-03-05 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 1:18 [f2fs-dev] [PATCH v2] f2fs: avoid reading already updated pages during GC Jianan Huang via Linux-f2fs-devel
2026-03-05 1:38 ` Chao Yu via Linux-f2fs-devel
2026-03-05 19:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=177273781304.3248266.12940471035367152097.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc==?utf-8?b?6buE5L2z55S3IDxodWFuZ2ppYW5hbkB4aWFvbWkuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=shengyong1@xiaomi.com \
--cc=wanghui33@xiaomi.com \
/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