Details
-
Improvement
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
There are many conflicts while applying rhel9.4/ext4-introduce-EXT4_BG_TRIMMED-to-optimize-fstrim.patch to RHEL 10.0 kernel 6.12.0-55.28.1.el10_0. This is because the following Linux kernel commits have changed fs/ext4/mballoc.c a lot:
- commit 20cee68f5b44fdc2942d20f3172a262ec247b117 ("ext4: clear EXT4_GROUP_INFO_WAS_TRIMMED_BIT even mount with discard")
- commit fa60629380bbbf0952d2eb906da187b171f54529 ("ext4: don't report EOPNOTSUPP errors from discard")
- commit 172202152a125955367393956acf5f4ffd092e0d ("ext4: do not trim the group with corrupted block bitmap")
- commit 68da4c44b994aea797eb9821acb3a4a36015293e ("ext4: fix inconsistent between segment fstrim and full fstrim")
- commit 7c784d624819acbeefb0018bac89e632467cca5a ("ext4: allow for the last group to be marked as trimmed")
- commit 38b8f70cd28c6ad21192d82f271b9e32bdcb8600 ("ext4: call ext4_mb_mark_context in ext4_mb_clear_bb")
- commit 33e728c67db6b7e72fc8d09f7a38f72302b8a98d ("ext4: Separate block bitmap and buddy bitmap freeing in ext4_mb_clear_bb()")
- commit 5229a658f6453362fbb9da6bf96872ef25a7097e ("ext4: do not let fstrim block system suspend")
- commit 45e4ab320c9b5fa67b1fc3b6a9b381cfcc0c8488 ("ext4: move setting of trimmed bit into ext4_try_to_trim_range()")
Could you please create a rhel10.0/ext4-introduce-EXT4_BG_TRIMMED-to-optimize-fstrim.patch for RHEL 10.0 kernel 6.12.0-55.28.1.el10_0 based on https://review.whamcloud.com/60843 ("LU-18667 kernel: RHEL 10.0 server support")?
