fs: ext4fs: Fix: Data abort in ext4fs_log_gdt()
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | fs: ext4fs: Fix: Data abort in ext4fs_log_gdt()fs/ | +7 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] fs: ext4fs: Fix: Data abort in ext4fs_log_gdt()
Currently, the number of EXT4 journal entries is defined as a constant, MAX_JOURNAL_ENTRIES = 100. When the HDD is greater than 2TB in capacity, the number of blocks per gdt (no_blk_pergdt) is a lot larger than 100. So the function ext4fs_log_gdt causes an array index out-of-bound in the journal log (journal_ptr[MAX_JOURNAL_ENTRIES]), and results in a data abort.
This was tested with the Synology DS116 (32-bit Armada 385 SoC) board, and a 4TB Seagate HDD.
Tony Dinh (1):
fs: ext4fs: Fix: Data abort in ext4fs_log_gdt()
fs/ext4/ext4_journal.c | 7 +++++++ 1 file changed, 7 insertions(+)
Signature · 4 lines
2.39.5 base-commit: e9f852f7fd2481579bb3521c13663d33a7f22eef branch: master