ext4: fix inline data / extent status truncation bug
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ext4: remove extent cache entries when truncating inline datafs/ | +19 | 0 replies | |
| 2/2 | ext4: enforce buffer head state assertion in ext4_da_map_blocksfs/ | +9 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] ext4: fix inline data / extent status truncation bug
If ext4 converts an inline file to extents when applying writes under delayed allocation that exceed the available inline storage, one or more delayed allocated extents may be stored in the extent status cache with an accompanying increase in the reserved block count. If the file is subsequently truncated before writeback occurs, that inode's delayed allocated extents will not be removed from the extent status cache and the reserved block count will not be reduced as required after truncation. At minimum, unexpected ENOSPC conditions can occur.
Eric Whitney (2):
ext4: remove extent cache entries when truncating inline data
ext4: enforce buffer head state assertion in ext4_da_map_blocks
fs/ext4/inline.c | 19 +++++++++++++++++++ fs/ext4/inode.c | 15 +++++++++------ 2 files changed, 28 insertions(+), 6 deletions(-)
Signature · 1 line
2.20.1