Patch "cifs: check MaxPathNameComponentLength != 0 before using it" has been added to the 4.13-stable tree
This is a note to let you know that I've just added the patch titled
cifs: check MaxPathNameComponentLength != 0 before using it
to the 4.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
cifs-check-maxpathnamecomponentlength-0-before-using-it.patch
and it can be found in the queue-4.13 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
f74bc7c6679200a4a83156bb89cbf6c229fe8ec0Mon Sep 17 00:00:00 2001
From: Ronnie Sahlberg <[email protected]>
Date: Mon, 30 Oct 2017 13:28:03 +1100
Subject: cifs: check MaxPathNameComponentLength != 0 before using it
From: Ronnie Sahlberg <[email protected]>
commit f74bc7c6679200a4a83156bb89cbf6c229fe8ec0 upstream.
And fix tcon leak in error path.
--- fs/cifs/dir.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
fs/cifs/dir.c +3 -2
@@ -204,7 +204,8 @@ check_name(struct dentry *direntry, strustruct cifs_sb_info *cifs_sb =CIFS_SB (direntry->d_sb);int i; -if (unlikely (direntry->d_name.len > +if (unlikely (tcon->fsAttrInfo.MaxPathNameComponentLength && + direntry->d_name.len >le32_to_cpu (tcon->fsAttrInfo.MaxPathNameComponentLength)))return -ENAMETOOLONG ;
@@ -520,7 +521,7 @@ cifs_atomic_open(struct inode *inode, st rc =check_name (direntry, tcon);if (rc) - goto out_free_xid; + goto out; server = tcon->ses->server;
Patches currently in stable-queue which might be from [email protected] are
queue-4.13/cifs-check-maxpathnamecomponentlength-0-before-using-it.patch