From: Paulo Alcantara <pc@manguebit.com>
To: "Steinbeißer, Sebastian" <Sebastian.Steinbeisser@lrz.de>,
"tom@talpey.com" <tom@talpey.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "smfrench@gmail.com" <smfrench@gmail.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Potential smb/dfs regression introduced in kernel 6.6
Date: Thu, 01 Aug 2024 13:25:28 -0300 [thread overview]
Message-ID: <c095559def052b738f040ffb52400e75@manguebit.com> (raw)
In-Reply-To: <7be5122d65dabd96a28a71678ca0efb93cbe749f.camel@lrz.de>
Hi Sebastian,
Steinbeißer, Sebastian <Sebastian.Steinbeisser@lrz.de> writes:
> thank you! I've poked our NetApp rep. again hoping to get some
> technical answers out of them finally ;)
No worries. I've been there :-)
> With the additional patch applied I can access signed & encrypted
> shares as well as the test share from which the logs are attached.
Thanks! This just confirms that FSCTL_GET_REPARSE_POINT against NetApp
indeed requires the FILE_READ_EA bit being set and it has never worked
since then.
I'll send an additional fix shortly to make FSCTL_GET_REPARSE_POINT work
against NetApp. I've tested it against Windows Server 2022 and it works
with FILE_READ_EA bit set as well.
next prev parent reply other threads:[~2024-08-01 16:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 13:28 Potential smb/dfs regression introduced in kernel 6.6 Steinbeißer, Sebastian
2024-06-27 13:37 ` Greg KH
[not found] ` <f3a02647b6fcb27a70da4c334930ad3c@manguebit.com>
2024-06-28 8:19 ` Steinbeißer, Sebastian
2024-07-11 6:20 ` Steinbeißer, Sebastian
2024-07-11 7:27 ` gregkh
2024-07-11 15:20 ` Christian Heusel
2024-07-14 19:12 ` Paulo Alcantara
2024-07-15 5:41 ` Steinbeißer, Sebastian
2024-07-15 12:21 ` Paulo Alcantara
2024-07-15 13:26 ` Steinbeißer, Sebastian
2024-07-15 14:24 ` Paulo Alcantara
2024-07-16 6:14 ` Steinbeißer, Sebastian
2024-07-17 18:24 ` Paulo Alcantara
2024-07-17 20:03 ` Tom Talpey
2024-07-18 5:43 ` Steinbeißer, Sebastian
2024-07-25 1:28 ` Paulo Alcantara
2024-07-26 8:19 ` Steinbeißer, Sebastian
2024-07-26 18:00 ` Paulo Alcantara
2024-07-29 5:57 ` Steinbeißer, Sebastian
2024-07-29 12:34 ` Paulo Alcantara
2024-07-30 5:25 ` Steinbeißer, Sebastian
2024-07-31 2:35 ` Paulo Alcantara
2024-07-31 5:02 ` Steinbeißer, Sebastian
2024-07-31 5:07 ` Steinbeißer, Sebastian
2024-07-31 14:25 ` Paulo Alcantara
2024-08-01 13:07 ` Steinbeißer, Sebastian
2024-08-01 16:25 ` Paulo Alcantara [this message]
2024-08-01 19:02 ` Tom Talpey
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=c095559def052b738f040ffb52400e75@manguebit.com \
--to=pc@manguebit.com \
--cc=Sebastian.Steinbeisser@lrz.de \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.