Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Ralph Boehme <slow@samba.org>
To: Paulo Alcantara <pc@manguebit.com>, smfrench@gmail.com
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH v2 3/3] smb: client: set correct file type from NFS reparse points
Date: Mon, 20 Nov 2023 06:49:09 +0100	[thread overview]
Message-ID: <ebade998-7c7e-422f-a1fe-680571b1310e@samba.org> (raw)
In-Reply-To: <20231119214450.23779-3-pc@manguebit.com>


[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]

Hi Paulo,

On 11/19/23 22:44, Paulo Alcantara wrote:
> Handle all file types in NFS reparse points as specified in MS-FSCC
> 2.1.2.6 Network File System (NFS) Reparse Data Buffer.
> 
> The client is now able to set all file types based on the parsed NFS
> reparse point, which used to support only symlinks.  This works for
> SMB1+.
any plans to also implement this for SMB3 UNIX Extensions?

Cheers!
-slow

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-11-20  6:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19 18:22 [PATCH 1/3] smb: client: implement ->query_reparse_point() for SMB1 Paulo Alcantara
2023-11-19 18:22 ` [PATCH 2/3] smb: client: introduce ->parse_reparse_point() Paulo Alcantara
2023-11-19 18:22 ` [PATCH 3/3] smb: client: set correct file type from NFS reparse points Paulo Alcantara
2023-11-19 21:44 ` [PATCH v2 1/3] smb: client: implement ->query_reparse_point() for SMB1 Paulo Alcantara
2023-11-19 21:44   ` [PATCH v2 2/3] smb: client: introduce ->parse_reparse_point() Paulo Alcantara
2023-11-19 21:44   ` [PATCH v2 3/3] smb: client: set correct file type from NFS reparse points Paulo Alcantara
2023-11-20  5:49     ` Ralph Boehme [this message]
2023-11-20 14:17       ` Paulo Alcantara
2023-11-20 14:27         ` Ralph Boehme
2023-11-21 23:12 ` [PATCH 1/7] smb: client: implement ->query_reparse_point() for SMB1 Paulo Alcantara
2023-11-21 23:12   ` [PATCH 2/7] smb: client: introduce ->parse_reparse_point() Paulo Alcantara
2023-11-21 23:12   ` [PATCH 3/7] smb: client: set correct file type from NFS reparse points Paulo Alcantara
2023-11-21 23:12   ` [PATCH 4/7] smb: client: introduce cifs_sfu_make_node() Paulo Alcantara
2023-11-21 23:12   ` [PATCH 5/7] smb: client: allow creating special files via reparse points Paulo Alcantara
2023-11-22 15:16     ` Paulo Alcantara
2023-11-21 23:12   ` [PATCH 6/7] smb: client: allow creating symlinks " Paulo Alcantara
2023-11-21 23:12   ` [PATCH 7/7] smb: client: handle reparse points over SMB3 POSIX Paulo Alcantara

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=ebade998-7c7e-422f-a1fe-680571b1310e@samba.org \
    --to=slow@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.com \
    --cc=smfrench@gmail.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