From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH v2 0/9] reparse points work
Date: Mon, 27 Nov 2023 07:14:23 -0300 [thread overview]
Message-ID: <9b17c94c65cbf7413b78dbea7a6ff5b9@manguebit.com> (raw)
In-Reply-To: <CAH2r5mttTq-JhMVa7uMheJ8gmm9dJjMSCjhAWczuA5yUR4Tr2Q@mail.gmail.com>
Steve French <smfrench@gmail.com> writes:
> tentatively merged to cifs-2.6.git for-next pending more testing and
> review
Please drop patch 8/9 as it is wrong. We can't really do that as the
file could have been changed on server side to a regular file and
therefore the client would keep trying to open it as a reparse point.
That can be easily reproduced.
Yeah, that is the price we get when we don't have such information
directly from query dir responses. Looking forward to having it with
the SMB3 POSIX spec :-)
prev parent reply other threads:[~2023-11-27 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 2:55 [PATCH v2 0/9] reparse points work Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 1/9] smb: client: extend smb2_compound_op() to accept more commands Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 2/9] smb: client: allow creating special files via reparse points Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 3/9] smb: client: allow creating symlinks " Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 4/9] smb: client: optimise reparse point querying Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 5/9] smb: client: fix renaming of reparse points Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 6/9] smb: client: fix hardlinking " Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 7/9] smb: client: cleanup smb2_query_reparse_point() Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 8/9] smb: client: optimise dentry revalidation for reparse points Paulo Alcantara
2023-11-26 2:55 ` [PATCH v2 9/9] smb: client: fix missing mode bits for SMB symlinks Paulo Alcantara
2023-11-27 4:28 ` [PATCH v2 0/9] reparse points work Steve French
2023-11-27 10:14 ` 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=9b17c94c65cbf7413b78dbea7a6ff5b9@manguebit.com \
--to=pc@manguebit.com \
--cc=linux-cifs@vger.kernel.org \
--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