The patch titled Subject: hfs: add sanity check for file name length has been added to the -mm tree. Its filename is hfs-add-sanity-check-for-file-name-length.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/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ From: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Subject: hfs: add sanity check for file name length On a corrupted file system the ->len field could be wrong leading to a buffer overflow. Reported-by: Clement LECIGNE <clement.lecigne@xxxxxxxxxx> Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Cc: Eugene Teo <eugeneteo@xxxxxxxxx> Cc: Eric Sandeen <sandeen@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/hfs/trans.c | 2 ++ 1 file changed, 2 insertions(+) diff -puN fs/hfs/trans.c~hfs-add-sanity-check-for-file-name-length fs/hfs/trans.c --- a/fs/hfs/trans.c~hfs-add-sanity-check-for-file-name-length +++ a/fs/hfs/trans.c @@ -40,6 +40,8 @@ int hfs_mac2asc(struct super_block *sb, src = in->name; srclen = in->len; + if (srclen > HFS_NAMELEN) + srclen = HFS_NAMELEN; dst = out; dstlen = HFS_MAX_NAMELEN; if (nls_io) { _ Subject: Subject: hfs: add sanity check for file name length Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are origin.patch linux-next.patch bio-change-some-signed-vars-to-unsigned.patch paride-fix-potential-information-leak-in-pg_read.patch hfs-add-sanity-check-for-file-name-length.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