Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: linux-cifs@vger.kernel.org
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Ronnie Sahlberg <ronniesahlberg@gmail.com>,
	Shyam Prasad N <sprasad@microsoft.com>,
	Tom Talpey <tom@talpey.com>, Bharath SM <bharathsm@microsoft.com>,
	stable@vger.kernel.org
Subject: [PATCH v2 5/5] smb: client: fix reparse point file type corruption
Date: Sun,  6 Sep 2026 15:15:40 -0300	[thread overview]
Message-ID: <20260906181540.647469-5-pc@manguebit.org> (raw)
In-Reply-To: <20260906181540.647469-1-pc@manguebit.org>

wsl_to_fattr() and posix_reparse_to_fattr() set the file type from
reparse point tags (e.g. fattr->cf_mode |= S_IFCHR).  When cf_mode
already has S_IFMT bits set by the caller, this corrupts the file
type.

For example, smb311_posix_info_to_fattr() sets cf_mode via
wire_mode_to_posix() which includes S_IFREG, then calls
cifs_reparse_point_to_fattr().  If the reparse tag indicates a
character device, the result is S_IFREG | S_IFCHR = S_IFLNK,
incorrectly turning the inode into a symlink.

Fix both functions by clearing the S_IFMT bits before the switch
statement, so the reparse point tag can set the correct file type
without interference from previously set bits.

Closes: https://sashiko.dev/#/patchset/20260906172005.627163-1-pc%40manguebit.org
Signed-off-by: Paulo Alcantara <pc@manguebit.org>
Cc: Namjae Jeon <linkinjeon@kernel.org>
Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: Shyam Prasad N <sprasad@microsoft.com>
Cc: Tom Talpey <tom@talpey.com>
Cc: Bharath SM <bharathsm@microsoft.com>
Cc: stable@vger.kernel.org
---
 fs/smb/client/reparse.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/fs/smb/client/reparse.c b/fs/smb/client/reparse.c
index 10ef82d46d86..773ad2e21b47 100644
--- a/fs/smb/client/reparse.c
+++ b/fs/smb/client/reparse.c
@@ -1146,6 +1146,7 @@ static bool wsl_to_fattr(struct cifs_open_info_data *data,
 	fattr->cf_uid = cifs_sb->ctx->linux_uid;
 	fattr->cf_gid = cifs_sb->ctx->linux_gid;
 
+	fattr->cf_mode &= ~S_IFMT;
 	switch (tag) {
 	case IO_REPARSE_TAG_LX_SYMLINK:
 		fattr->cf_mode |= S_IFLNK;
@@ -1234,6 +1235,7 @@ static bool posix_reparse_to_fattr(struct cifs_sb_info *cifs_sb,
 		return false;
 	}
 
+	fattr->cf_mode &= ~S_IFMT;
 	switch (le64_to_cpu(buf->InodeType)) {
 	case NFS_SPECFILE_CHR:
 		if (le16_to_cpu(buf->ReparseDataLength) != sizeof(buf->InodeType) + 8) {
-- 
2.55.0


      parent reply	other threads:[~2026-09-06 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 18:15 [PATCH v2 1/5] smb: client: fix uid/gid override in getattr with posix extensions Paulo Alcantara
2026-09-06 18:15 ` [PATCH v2 2/5] smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid Paulo Alcantara
2026-09-06 18:15 ` [PATCH v2 3/5] smb: client: fix WSL reparse point uid/gid override Paulo Alcantara
2026-09-06 18:15 ` [PATCH v2 4/5] smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() Paulo Alcantara
2026-09-06 18:15 ` Paulo Alcantara [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260906181540.647469-5-pc@manguebit.org \
    --to=pc@manguebit.org \
    --cc=bharathsm@microsoft.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=sprasad@microsoft.com \
    --cc=stable@vger.kernel.org \
    --cc=tom@talpey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox