The patch titled
Subject: hfs: fix BUG on bnode parent update
has been added to the -mm tree. Its filename is
hfs-fix-bug-on-bnode-parent-update.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/hfs-fix-bug-on-bnode-parent-update.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/hfs-fix-bug-on-bnode-parent-update.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
Binary file patches/hfs-fix-bug-on-bnode-parent-update.patch matches
Subject: hfs: fix BUG on bnode parent update
hfs_brec_update_parent() may hit BUG_ON() if the first record of both a
leaf node and its parent are changed, and if this forces the parent to
be split. It is not possible for this to happen on a valid hfs
filesystem because the index nodes have fixed length keys.
For reasons I ignore, the hfs module does have support for a number of
hfsplus features. A corrupt btree header may report variable length
keys and trigger this BUG, so it's better to fix it.
Link: http://lkml.kernel.org/r/cf9b02d57f806217a2b1bf5db8c3e39730d8f603.1535682463.git.ernesto.mnd.fernandez@xxxxxxxxx
Signed-off-by: Ernesto A. Fern�ez <ernesto.mnd.fernandez@xxxxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
diff -puN fs/hfs/brec.c~hfs-fix-bug-on-bnode-parent-update fs/hfs/brec.c
--- a/fs/hfs/brec.c~hfs-fix-bug-on-bnode-parent-update
+++ a/fs/hfs/brec.c
@@ -445,6 +445,7 @@ skip:
/* restore search_key */
hfs_bnode_read_key(node, fd->search_key, 14);
}
+ new_node = NULL;
}
if (!rec && node->parent)
_
Patches currently in -mm which might be from ernesto.mnd.fernandez@xxxxxxxxx are
