Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Steve French <sfrench@samba.org>,
	Paulo Alcantara <pc@manguebit.com>,
	Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] cifs: Handle all name surrogate reparse points
Date: Sun, 23 Feb 2025 23:23:06 +0100	[thread overview]
Message-ID: <20250223222306.plgy3bpy5mjojfve@pali> (raw)
In-Reply-To: <20241222145845.23801-1-pali@kernel.org>

Hello Steve, I see that you have merged first two changes (1/4 and 2/4)
from this patch series, but the remaining (3/4 and 4/4). Is there any
reason why 3/4 and 4/4 was not taken?

On Sunday 22 December 2024 15:58:41 Pali Rohár wrote:
> Name surrogate reparse point represents another named entity in the system.
> 
> If the name surrogate reparse point is not handled by Linux SMB client
> and it is of directory type then treat it as a new mount point.
> 
> Cleanup code for all explicit surrogate reparse points (like reparse
> points with tag IO_REPARSE_TAG_MOUNT_POINT) as they are handled by
> generic name surrogate reparse point code.
> 
> Pali Rohár (4):
>   cifs: Throw -EOPNOTSUPP error on unsupported reparse point type from
>     parse_reparse_point()
>   cifs: Treat unhandled directory name surrogate reparse points as mount
>     directory nodes
>   cifs: Remove explicit handling of IO_REPARSE_TAG_MOUNT_POINT in
>     inode.c
>   cifs: Improve handling of name surrogate reparse points in reparse.c
> 
>  fs/smb/client/inode.c    | 17 +++++++++++++----
>  fs/smb/client/reparse.c  | 24 ++++++++++--------------
>  fs/smb/common/smbfsctl.h |  3 +++
>  3 files changed, 26 insertions(+), 18 deletions(-)
> 
> -- 
> 2.20.1
> 

  parent reply	other threads:[~2025-02-23 22:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22 14:58 [PATCH 0/4] cifs: Handle all name surrogate reparse points Pali Rohár
2024-12-22 14:58 ` [PATCH 1/4] cifs: Throw -EOPNOTSUPP error on unsupported reparse point type from parse_reparse_point() Pali Rohár
2024-12-22 14:58 ` [PATCH 2/4] cifs: Treat unhandled directory name surrogate reparse points as mount directory nodes Pali Rohár
2024-12-22 14:58 ` [PATCH 3/4] cifs: Remove explicit handling of IO_REPARSE_TAG_MOUNT_POINT in inode.c Pali Rohár
2024-12-22 14:58 ` [PATCH 4/4] cifs: Improve handling of name surrogate reparse points in reparse.c Pali Rohár
2025-02-23 22:23 ` Pali Rohár [this message]
2025-02-24  0:48   ` [PATCH 0/4] cifs: Handle all name surrogate reparse points Steve French
2025-03-02 12:24     ` Pali Rohár
2025-03-03  1:01       ` Steve French
2025-03-04 20:37         ` Pali Rohár

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=20250223222306.plgy3bpy5mjojfve@pali \
    --to=pali@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pc@manguebit.com \
    --cc=ronniesahlberg@gmail.com \
    --cc=sfrench@samba.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