Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Paulo Alcantara <pc@manguebit.org>,
	linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7.3 8/9] cifs: Add support for parsing WSL symlinks in version 1 format
Date: Thu, 29 Oct 2026 00:45:30 +0100	[thread overview]
Message-ID: <20261028234530.2bnbxbotnegss5ll@pali> (raw)
In-Reply-To: <CAKYAXd-hQXxBLxLQ_dr5omw-_xgL+96fNYfgW_poAihXYqDxmA@mail.gmail.com>

On Tuesday 27 October 2026 10:37:45 Namjae Jeon wrote:
...
> > +               oparms = CIFS_OPARMS(cifs_sb, tcon, full_path, FILE_READ_DATA,
> > +                                    FILE_OPEN, CREATE_NOT_DIR | OPEN_REPARSE_POINT,
> > +                                    ACL_NO_MODE);
> > +               oparms.fid = &fid;
> Should we pass initialized fid to ->open()? When SMB2/3 leasing is
> enabled, the open path copies fid->lease_key into the outgoing CREATE
> request, potentially disclosing 16 bytes of stale stack data to the
> server ?

I think that I have copied this pattern from somewhere. So maybe the
same issue is in other parts of the code.

> So, how about updating it like this ?
> 
> struct cifs_fid fid = {};
> ...
> if (tcon->ses->server->ops->new_lease_key)
>     tcon->ses->server->ops->new_lease_key(&fid);

I will look at it.

Anyway this series contains various changes and these last two PATCH8
and PATCH9 are not needed for rest of them. So if there is no issue with
PATCH1-7 I would like if we can process at least first 7 without need to
address issues in 8 and 9. I'm waiting for these changes for a longer
time and mostly I'm just resending 1-7 without any modification, just
rebasing them.

> 
> 
> > +               oplock = tcon->ses->server->oplocks ? REQ_OPLOCK : 0;
> > +               rc = tcon->ses->server->ops->open(xid, &oparms, &oplock, NULL);
> > +               if (rc)
> > +                       goto out;
> > +
> > +               buf_type = CIFS_NO_BUFFER;
> > +               io_parms = (struct cifs_io_parms) {
> > +                       .pid = current->tgid,
> > +                       .tcon = tcon,
> > +                       .offset = 0,
> > +                       .length = symname_utf8_len,
> > +               };
> > +               rc = tcon->ses->server->ops->sync_read(xid, &fid, &io_parms,
> > +                                                      &symname_utf8_len,
> > +                                                      &symname_utf8,
> > +                                                      &buf_type);
> > +               if (!rc && symname_utf8_len != file_size)
> > +                       rc = -EIO;
...

  reply	other threads:[~2026-10-28 23:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 22:25 [PATCH v7.3 0/9] Various changes Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 1/9] cifs: Remove code for querying FILE_INFO_STANDARD via CIFSSMBQPathInfo() Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 2/9] cifs: Remove cifs_backup_query_path_info() and replace it by cifs_query_path_info() Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 3/9] cifs: Fix validation of EAs for WSL reparse points Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 4/9] cifs: Validate presence of EA $LXMOD " Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 5/9] cifs: Check if server supports EAs before trying to set it for WSL Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 6/9] cifs: Extend ->set_EA() callback to allow operate on reparse point Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 7/9] cifs: Create native Window socket file compatible also with WSL subsystem Pali Rohár
2026-10-26 22:25 ` [PATCH v7.3 8/9] cifs: Add support for parsing WSL symlinks in version 1 format Pali Rohár
2026-10-27  1:37   ` Namjae Jeon
2026-10-28 23:45     ` Pali Rohár [this message]
2026-10-29  0:47       ` Namjae Jeon
2026-10-26 22:26 ` [PATCH v7.3 9/9] cifs: Add support for creating " Pali Rohár
2026-10-27  1:38   ` Namjae Jeon
2026-10-27  1:42 ` [PATCH v7.3 0/9] Various changes Namjae Jeon
2026-10-29  0:49 ` Namjae Jeon

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=20261028234530.2bnbxbotnegss5ll@pali \
    --to=pali@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pc@manguebit.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