From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 220951] swapfile activation bug causes data corruption when swapfile < 2MB with fragmented extents
Date: Tue, 13 Jan 2026 06:03:41 +0000 [thread overview]
Message-ID: <bug-220951-202145-3smS9mBnss@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220951-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220951
--- Comment #2 from guoxiaolong2008@gmail.com ---
Hi Chao Yu:
Thanks for your fix, I verified the solution and it does work.
stress-ng-swap-7946 [007] ..... 346.972372: f2fs_map_blocks: dev =
(254,47), ino = 16800, file offset = 0, start blkaddr = 0x77d0d, len = 0x1,
flags = 2, seg_type = 8, may_create = 0, multidevice = 0, flag = 6, err = 0
stress-ng-swap-7946 [007] ..... 346.972376: f2fs_map_blocks: dev =
(254,47), ino = 16800, file offset = 1, start blkaddr = 0x1f6801, len = 0xff,
flags = 2, seg_type = 8, may_create = 0, multidevice = 0, flag = 6, err = 0
stress-ng-swap-7946 [007] ..... 346.972378: f2fs_map_blocks: dev =
(254,47), ino = 16800, file offset = 0, start blkaddr = 0x77d0d, len = 0x1,
flags = 2, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
stress-ng-swap-7946 [007] ..... 346.974392: f2fs_map_blocks: dev =
(254,47), ino = 16800, file offset = 0, start blkaddr = 0x1f6a00, len = 0x100,
flags = 2, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
The swapfile can be mapped correctly.
Thanks.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-01-13 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 2:20 [f2fs-dev] [Bug 220951] New: swapfile activation bug causes data corruption when swapfile < 2MB with fragmented extents bugzilla-daemon--- via Linux-f2fs-devel
2026-01-07 2:30 ` [f2fs-dev] [Bug 220951] " bugzilla-daemon--- via Linux-f2fs-devel
2026-01-12 10:25 ` bugzilla-daemon--- via Linux-f2fs-devel
2026-01-13 6:03 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2026-01-13 6:15 ` bugzilla-daemon--- via Linux-f2fs-devel
2026-01-13 6:17 ` bugzilla-daemon--- via Linux-f2fs-devel
2026-01-14 15:49 ` bugzilla-daemon--- via Linux-f2fs-devel
2026-01-20 9:20 ` bugzilla-daemon--- via Linux-f2fs-devel
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=bug-220951-202145-3smS9mBnss@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@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