The patch titled
hfsplus: fix possible deadlock when handling corrupted extents
has been removed from the -mm tree. Its filename was
hfsplus-fix-possible-deadlock-when-handling-corrupted-extents.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: hfsplus: fix possible deadlock when handling corrupted extents
From: Eric Sesterhenn <snakebyte@xxxxxx>
A corrupted extent for the extent file itself may try to get an impossible
extent, causing a deadlock if I see it correctly.
Check the inode number after the first_blocks checks and fail if it's the
extent file, as according to the spec the extent file should have no
extent for itself.
Signed-off-by: Eric Sesterhenn <snakebyte@xxxxxx>
Cc: Roman Zippel <zippel@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/hfsplus/extents.c | 3 +++
1 file changed, 3 insertions(+)
diff -puN fs/hfsplus/extents.c~hfsplus-fix-possible-deadlock-when-handling-corrupted-extents fs/hfsplus/extents.c
--- a/fs/hfsplus/extents.c~hfsplus-fix-possible-deadlock-when-handling-corrupted-extents
+++ a/fs/hfsplus/extents.c
@@ -199,6 +199,9 @@ int hfsplus_get_block(struct inode *inod
goto done;
}
+ if (inode->i_ino == HFSPLUS_EXT_CNID)
+ return -EIO;
+
mutex_lock(&HFSPLUS_I(inode).extents_lock);
res = hfsplus_ext_read_extent(inode, ablock);
if (!res) {
_
Patches currently in -mm which might be from snakebyte@xxxxxx are
origin.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
