A flaw was found in the way splitting two extents in ext4_ext_convert_to_initialized() worked. Althrough ex has been updated in memory, it is not dirtied both in ext4_ext_convert_to_initialized() and ext4_ext_insert_extent(). The disk layout is corrupted. Then it will meet with a BUG_ON() when writting at the start of that extent again. Introduced in: 56055d3ae4cc7fa6d2b10885f20269de8a989ed7 Upstream fix: 667eff35a1f56fa74ce98a0c7c29a40adc1ba4e3
Created kernel tracking bugs for this issue Affects: fedora-all [bug 747948]
Statement: This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for EXT4 filesystem. It did not affect the Linux kernel as shipped with Red Hat Enterprise MRG as it has backported the upstream commit 667eff35 that addressed this issue. This has been addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2012-0107.html and https://rhn.redhat.com/errata/RHSA-2011-1530.html.
(In reply to comment #0) > A flaw was found in the way splitting two extents in > ext4_ext_convert_to_initialized() worked. Althrough ex has been updated in > memory, it is not dirtied both in ext4_ext_convert_to_initialized() and > ext4_ext_insert_extent(). The disk layout is corrupted. Then it will meet with > a BUG_ON() when writting at the start of that extent again. > > Introduced in: > 667eff35a1f56fa74ce98a0c7c29a40adc1ba4e3 > > Upstream fix: > 667eff35a1f56fa74ce98a0c7c29a40adc1ba4e3 That's the same hash for both. Perhaps the upstream fix one is incorrectly listed?
> That's the same hash for both. Perhaps the upstream fix one is incorrectly > listed? You are right, it's already fixed.
Are you saying this is fixed in upstream but not in Fedora or RHEL? Thanks!
(In reply to comment #9) > Are you saying this is fixed in upstream but not in Fedora or RHEL? RHEL should be affected. If Fedora kernels containt the upstream patch in comment #0, they are not affected.
(In reply to comment #11) > (In reply to comment #9) > > Are you saying this is fixed in upstream but not in Fedora or RHEL? > > RHEL should be affected. If Fedora kernels containt the upstream patch in > comment #0, they are not affected. Right. It should be fixed in upstream and F15-rawhide, as 667eff35a1f56fa74ce98a0c7c29a40adc1ba4e3 is contained in the 3.0 kernel release. I'll address F14 in the fedora bug.
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2011:1530 https://rhn.redhat.com/errata/RHSA-2011-1530.html
Acknowledgements: Red Hat would like to thank Zheng Liu for reporting this issue.
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2012:0107 https://rhn.redhat.com/errata/RHSA-2012-0107.html
This issue has been addressed in following products: Red Hat Enterprise Linux 6.1 EUS - Server Only Via RHSA-2012:0116 https://rhn.redhat.com/errata/RHSA-2012-0116.html
This issue has been addressed in following products: Red Hat Enterprise Linux 5.6 EUS - Server Only Via RHSA-2012:0517 https://rhn.redhat.com/errata/RHSA-2012-0517.html