From: Paulo Alcantara <pc@manguebit.com>
To: Ralph Boehme <slow@samba.org>,
Steven French <Steven.French@microsoft.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Special files broken against Samba master
Date: Mon, 02 Dec 2024 19:40:34 -0300 [thread overview]
Message-ID: <0a8569561645ad202c5cceba02cda93a@manguebit.com> (raw)
In-Reply-To: <458d3314-2010-4271-bb73-bff47e9de358@samba.org>
Ralph Boehme <slow@samba.org> writes:
> I'm also optimizing away unneeded reparse point queries
> (create+fsctl+close) for nfs reparse points where we only need the file
> type which we now get and use via the smb3 posix type.
Awesome! Yeah, we don't need to revalidate the special files with
SMB3.1.1 POSIX as we can already parse file type directly from query dir
response. We could that in separate patches, so no worries. This will
definitely help with getdents(2).
> I'm sure I'm doing things wrong. Can you help me getting this across the
> line?
Patches look good, thanks. It would be great making sure it didn't
regress against NFS server on Windows, but Steve can do that.
Thanks Ralph!
next prev parent reply other threads:[~2024-12-02 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 19:23 Special files broken against Samba master Ralph Boehme
2024-12-02 22:40 ` Paulo Alcantara [this message]
2024-12-03 10:02 ` Ralph Boehme
2024-12-03 19:56 ` Steve French
2024-12-03 20:25 ` Ralph Boehme
2024-12-05 0:06 ` Steve French
2024-12-06 12:11 ` Ralph Boehme
2024-12-06 14:45 ` Steve French
2024-12-09 18:39 ` Pali Rohár
2024-12-09 19:28 ` Paulo Alcantara
2024-12-09 19:34 ` Pali Rohár
2024-12-09 19:42 ` Paulo Alcantara
2024-12-09 19:54 ` Pali Rohár
2024-12-10 13:19 ` Paulo Alcantara
2025-01-01 13:39 ` 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=0a8569561645ad202c5cceba02cda93a@manguebit.com \
--to=pc@manguebit.com \
--cc=Steven.French@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=slow@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