| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-e2fsck-fix-portability-problems-caused-by-unaligned-.patch | [PATCH 1/5] e2fsck: fix portability problems caused by unaligned accesses The on-disk format for the ext4 journal can have unaigned 32-bit integers. This can happen when replaying a journal using a obsolete checksum format (which was never popularly used, since the v3 format replaced v2 while the metadata checksum feature was being stablized), and in the fast commit feature (which landed in the 5.10 kernel, although it is not enabled by default). This commit fixes the following regression tests on some platforms (such as running 32-bit arm architectures on a 64-bit arm kernel): j_recover_csum2_32bit, j_recover_csum2_64bit, j_recover_fast_commit. https://github.com/tytso/e2fsprogs/issues/65 |
Theodore Ts'o <tytso@mit.edu> | no | 2021-05-03 | ||
| 0002-e2fsck-fix-unaligned-accesses-to-ext4_fc_tl-struct.patch | [PATCH 2/5] e2fsck: fix unaligned accesses to ext4_fc_tl struct Fast commit related struct ext4_fc_tl can be unaligned on disk. So, while accessing that we should ensure that the pointers are aligned. This patch fixes unaligned accesses to ext4_fc_tl and also gets rid of macros fc_for_each_tl and ext4_fc_tag_val that may result in unaligned accesses to struct ext4_fc_tl. |
Harshad Shirwadkar <harshadshirwadkar@gmail.com> | no | 2021-05-06 | ||
| 0003-e2fsck-fix-unaligned-accesses-to-ext4_fc_add_range-a.patch | [PATCH 3/5] e2fsck: fix unaligned accesses to ext4_fc_add_range and fc_raw_inode These fast commit related structures can be unaligned on disk. So we need to avoid accessing these structures directly, and first copy them to memory which we know is appropriately aligned. This fixes an e2fsck crash while running the j_recovery_fast_commit regression test on a sparc64 system. |
Theodore Ts'o <tytso@mit.edu> | no | 2021-05-06 | ||
| 0004-libext2fs-fix-missing-mutex-unlock-in-an-error-path-.patch | [PATCH 4/5] libext2fs: fix missing mutex unlock in an error path of the Unix I/O manager Originally from https://github.com/tytso/e2fsprogs/pull/68 |
Alexander Kanavin <alex.kanavin@gmail.com> | no | 2021-04-30 | ||
| 0005-e2image-add-OPTIONS-section-to-man-page.patch | [PATCH 5/5] e2image: add OPTIONS section to man page Reorganize the e2image.8 man page so that the command-line options are listed in a dedicated OPTIONS section, rather than being interspersed among the text in the DESCRIPTION section. Otherwise, it is difficult to determine which options are available, and to find where each option is described. |
Andreas Dilger <adilger@dilger.ca> | no | 2021-03-09 | ||
| 0001-libext2fs-add-sanity-check-to-extent-manipulation.patch | libext2fs: add sanity check to extent manipulation It is possible to have a corrupted extent tree in such a way that a leaf node contains zero extents in it. Currently if that happens and we try to traverse the tree we can end up accessing wrong data, or possibly even uninitialized memory. Make sure we don't do that. Additionally make sure that we have a sane number of bytes passed to memmove() in ext2fs_extent_delete(). Note that e2fsck is currently unable to spot and fix such corruption in pass1. |
Lukas Czerner <lczerner@redhat.com> | no | 2022-04-21 |