Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: Frank Sorenson <sorenson@redhat.com>, linux-cifs@vger.kernel.org
Cc: linkinjeon@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] smb: client: fix copy-paste error in WSL EA length accounting for $LXDEV
Date: Fri, 21 Aug 2026 14:05:51 -0300	[thread overview]
Message-ID: <ce7cdb05343c5d98dcbdec0d61a0bf6c@manguebit.org> (raw)
In-Reply-To: <20260820212210.1475817-1-sorenson@redhat.com>

Frank Sorenson <sorenson@redhat.com> writes:

> The LXDEV block in cifs_query_path_info() uses SMB2_WSL_XATTR_MODE_SIZE
> (4) instead of SMB2_WSL_XATTR_DEV_SIZE (8), undercounting eas_len by 4
> bytes per $LXDEV EA.
>
> eas_len is used only as a zero/non-zero presence flag so there is no
> current functional impact, but the value is incorrect and misleading.
> ...

Applied.

      parent reply	other threads:[~2026-08-21 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 21:22 [PATCH] smb: client: fix copy-paste error in WSL EA length accounting for $LXDEV Frank Sorenson
2026-08-20 23:53 ` Namjae Jeon
2026-08-21 17:05 ` 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=ce7cdb05343c5d98dcbdec0d61a0bf6c@manguebit.org \
    --to=pc@manguebit.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=sorenson@redhat.com \
    --cc=stable@vger.kernel.org \
    /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