From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Tue, 24 Mar 2026 17:32:08 +0000 [thread overview]
Message-ID: <177437352862.1223048.3815455394287346647.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Patch: [f2fs-dev] f2fs: drop unused ri parameter from truncate_partial_nodes()
Submitter: Yongpeng Yang <monty_pavel@sina.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1069119
Lore link: https://lore.kernel.org/r/20260319083525.603728-3-monty_pavel@sina.com
Series: [f2fs-dev,v3,1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1070733
Lore link: https://lore.kernel.org/r/20260323083834.156393-1-chao@kernel.org
Patches: [f2fs-dev,v3,1/2] f2fs: call f2fs_handle_critical_error() to set cp_error flag
[f2fs-dev,v3,2/2] f2fs: use more generic f2fs_stop_checkpoint()
Patch: [f2fs-dev,v2] f2fs: fix to skip empty sections in f2fs_get_victim
Submitter: Daeho Jeong <daeho43@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1067522
Lore link: https://lore.kernel.org/r/20260316185922.2184759-1-daeho43@gmail.com
Patch: [f2fs-dev,v4] f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io()
Submitter: George Saad <geoo115@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1070857
Lore link: https://lore.kernel.org/r/20260323112123.786090-1-geoo115@gmail.com
Patch: [f2fs-dev,GIT,PULL] fsverity updates for 6.3
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Linus Torvalds <torvalds@linux-foundation.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=723317
Lore link: https://lore.kernel.org/r/Y/KLHT3zaA0QFhVJ@sol.localdomain
Series: [f2fs-dev,v4,1/2] f2fs: fix incorrect multidevice info in trace_f2fs_map_blocks()
Submitter: Yongpeng Yang <monty_pavel@sina.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1070877
Lore link: https://lore.kernel.org/r/20260323120622.3351920-2-monty_pavel@sina.com
Patches: [f2fs-dev,v4,1/2] f2fs: fix incorrect multidevice info in trace_f2fs_map_blocks()
[f2fs-dev,v4,2/2] f2fs: fix fiemap boundary handling when read extent cache is incomplete
Patch: [f2fs-dev] f2fs: fix to do sanity check on dcc->discard_cmd_cnt conditionally
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1065133
Lore link: https://lore.kernel.org/r/20260311133542.1074617-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: support to report fserror
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1070750
Lore link: https://lore.kernel.org/r/20260323090344.219267-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: fix to avoid uninit-value access in f2fs_sanity_check_node_footer
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1063374
Lore link: https://lore.kernel.org/r/20260309022237.1680736-1-chao@kernel.org
Series: [f2fs-dev,v5,1/4] f2fs: refactor f2fs_move_node_folio function
Submitter: Yongpeng Yang <monty_pavel@sina.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1068505
Lore link: https://lore.kernel.org/r/20260318084534.373516-2-monty_pavel@sina.com
Patches: [f2fs-dev,v5,1/4] f2fs: refactor f2fs_move_node_folio function
[f2fs-dev,v5,3/4] f2fs: fix fsck inconsistency caused by FGGC of node block
[f2fs-dev,v5,4/4] f2fs: fix inline data not being written to disk in writeback path
Patch: [f2fs-dev] f2fs: fix false alarm of lockdep on cp_global_sem lock
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1062550
Lore link: https://lore.kernel.org/r/20260306122421.209903-1-chao@kernel.org
Patch: [f2fs-dev,v3] f2fs: fix to freeze GC and discard threads quickly
Submitter: Daeho Jeong <daeho43@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1067523
Lore link: https://lore.kernel.org/r/20260316185954.2185806-1-daeho43@gmail.com
Patch: [f2fs-dev,v2] f2fs: add READ_ONCE() for i_blocks in f2fs_update_inode()
Submitter: Cen Zhang <zzzccc427@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1068459
Lore link: https://lore.kernel.org/r/20260318073253.3108313-1-zzzccc427@gmail.com
Series: f2fs: fix data consistency issue caused by nat_entry flag
Submitter: Yongpeng Yang <monty_pavel@sina.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=1064219
Lore link: https://lore.kernel.org/r/20260310093611.2865092-2-monty_pavel@sina.com
Patches: [f2fs-dev,1/2] f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage
[f2fs-dev,2/2] f2fs: fix data loss caused by incorrect use of nat_entry flag
Total patches: 19
--
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
next reply other threads:[~2026-03-24 17:32 UTC|newest]
Thread overview: 161+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:32 patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 23:30 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11 1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11 1:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-01 4:52 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-18 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-15 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-13 23:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-02 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-03-05 19:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-17 21:14 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-10 21:28 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-30 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-27 2:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-22 23:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-19 13:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-16 3:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-07 3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16 19:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16 0:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-09 17:18 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-03 21:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-02 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-24 18:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-11 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-16 18:24 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-10 16:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 18:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 17:38 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-02 20:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-29 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-02 20:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-08-15 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-30 17:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-28 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-24 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-18 20:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-11 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-11 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-09 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-24 0:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-18 21:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-09 20:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-28 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-14 15:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-08 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-06 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-30 2:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-28 22:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-14 22:57 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-12 17:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-10 4:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-27 21:58 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-18 1:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-14 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-13 18:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-12 15:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 19:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-05 14:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-04 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-01 1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-28 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-21 2:17 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12 3:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12 2:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-06 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-29 0:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-25 1:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-22 21:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-21 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-17 21:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-13 18:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-08 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-12-16 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-23 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-21 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-18 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-07 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-28 17:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-14 20:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-10 20:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-25 3:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-16 21:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-30 20:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-05 23:30 patchwork-bot+f2fs
2024-07-24 2:16 patchwork-bot+f2fs
2024-07-15 14:40 patchwork-bot+f2fs
2024-07-03 15:20 patchwork-bot+f2fs
2024-06-24 17:40 patchwork-bot+f2fs
2024-06-12 15:55 patchwork-bot+f2fs
2024-05-20 21:16 patchwork-bot+f2fs
2024-05-15 4:20 patchwork-bot+f2fs
2024-05-11 0:50 patchwork-bot+f2fs
2024-04-25 15:40 patchwork-bot+f2fs
2024-04-24 17:40 patchwork-bot+f2fs
2024-04-23 17:40 patchwork-bot+f2fs
2024-04-14 15:32 patchwork-bot+f2fs
2024-03-18 20:45 patchwork-bot+f2fs
2024-03-14 16:20 patchwork-bot+f2fs
2024-03-13 1:30 patchwork-bot+f2fs
2024-03-06 17:50 patchwork-bot+f2fs
2024-03-04 18:20 patchwork-bot+f2fs
2024-02-28 22:50 patchwork-bot+f2fs
2024-02-21 18:10 patchwork-bot+f2fs
2024-01-30 20:50 patchwork-bot+f2fs
2024-01-29 20:29 patchwork-bot+f2fs
2024-01-16 19:02 patchwork-bot+f2fs
2023-12-29 19:10 patchwork-bot+f2fs
2023-12-14 20:50 patchwork-bot+f2fs
2023-11-30 18:30 patchwork-bot+f2fs
2023-10-23 15:30 patchwork-bot+f2fs
2023-09-20 15:50 patchwork-bot+f2fs
2023-09-04 18:11 patchwork-bot+f2fs
2023-08-28 17:20 patchwork-bot+f2fs
2023-08-25 17:30 patchwork-bot+f2fs
2023-08-21 19:50 patchwork-bot+f2fs
2023-08-14 20:50 patchwork-bot+f2fs
2023-08-07 20:00 patchwork-bot+f2fs
2023-07-17 17:34 patchwork-bot+f2fs
2023-07-06 0:18 patchwork-bot+f2fs
2023-06-30 23:40 patchwork-bot+f2fs
2023-06-26 13:30 patchwork-bot+f2fs
2023-06-22 7:11 patchwork-bot+f2fs
2023-06-16 23:50 patchwork-bot+f2fs
2023-06-15 18:00 patchwork-bot+f2fs
2023-06-12 20:50 patchwork-bot+f2fs
2023-06-07 17:30 patchwork-bot+f2fs
2023-05-30 23:40 patchwork-bot+f2fs
2023-05-18 1:50 patchwork-bot+f2fs
2023-05-08 18:34 patchwork-bot+f2fs
2023-04-26 23:07 patchwork-bot+f2fs
2023-04-24 18:10 patchwork-bot+f2fs
2023-04-17 21:50 patchwork-bot+f2fs
2023-04-13 23:40 patchwork-bot+f2fs
2023-04-12 16:20 patchwork-bot+f2fs
2023-04-11 17:00 patchwork-bot+f2fs
2023-04-05 16:20 patchwork-bot+f2fs
2023-04-04 21:30 patchwork-bot+f2fs
2023-04-04 1:54 patchwork-bot+f2fs
2023-04-03 18:30 patchwork-bot+f2fs
2023-03-29 22:21 patchwork-bot+f2fs
2023-03-27 16:00 patchwork-bot+f2fs
2023-03-21 16:40 patchwork-bot+f2fs
2023-03-13 20:20 patchwork-bot+f2fs
2023-03-07 17:40 patchwork-bot+f2fs
2023-02-28 1:01 patchwork-bot+f2fs
2023-02-15 18:00 patchwork-bot+f2fs
2023-02-14 18:10 patchwork-bot+f2fs
2023-02-10 21:40 patchwork-bot+f2fs
2023-02-07 19:00 patchwork-bot+f2fs
2023-02-06 3:50 patchwork-bot+f2fs
2023-02-06 3:40 patchwork-bot+f2fs
2023-01-31 19:10 patchwork-bot+f2fs
2023-01-30 23:00 patchwork-bot+f2fs
2023-01-11 19:20 patchwork-bot+f2fs
2023-01-09 22:51 patchwork-bot+f2fs
2023-01-03 18:50 patchwork-bot+f2fs
2023-01-03 17:03 patchwork-bot+f2fs
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=177437352862.1223048.3815455394287346647.git-patchwork-summary@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=patchwork-bot+f2fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.