From: Paulo Alcantara <pc@manguebit.com>
To: Tom Talpey <tom@talpey.com>, David Howells <dhowells@redhat.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: David Disseldorp <ddiss@samba.org>,
David Howells via samba-technical
<samba-technical@lists.samba.org>,
Steve French <sfrench@samba.org>, Jeremy Allison <jra@samba.org>,
linux-cifs@vger.kernel.org
Subject: Re: Bug in Samba's implementation of FSCTL_QUERY_ALLOCATED_RANGES?
Date: Thu, 23 May 2024 12:28:35 -0300 [thread overview]
Message-ID: <af49124840aa5960107772673f807f88@manguebit.com> (raw)
In-Reply-To: <6ea739f6-640a-4f13-a9a9-d41538be9111@talpey.com>
Tom Talpey <tom@talpey.com> writes:
> Yeah, I think this is a Samba server issue. Ronnie is right that it
> should return a partial response and a STATUS_BUFFER_OVERFLOW error
> indicating that it's partial. It's not supposed to return
> STATUS_BUFFER_TOO_SMALL unless the entire buffer is less than one
> entry.
>
> MS-FSA section 2.5.10.22
>
> https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fsa/385dec98-90fe-477f-9789-20a47a7b8467
Yes. I've just tested it against Windows Server 2022 and it correctly
returns STATUS_BUFFER_OVERFLOW.
next prev parent reply other threads:[~2024-05-23 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 23:53 Bug in Samba's implementation of FSCTL_QUERY_ALLOCATED_RANGES? David Howells
2024-05-22 8:53 ` David Disseldorp
2024-05-22 10:36 ` David Howells
2024-05-23 4:54 ` David Disseldorp
2024-05-23 5:05 ` ronnie sahlberg
2024-05-23 6:21 ` David Howells
2024-05-23 6:28 ` ronnie sahlberg
2024-05-23 6:36 ` David Howells
2024-05-23 14:29 ` Tom Talpey
2024-05-23 15:28 ` Paulo Alcantara [this message]
2024-05-23 22:49 ` Jeremy Allison
2024-05-24 7:45 ` Stefan Metzmacher
2024-08-22 22:26 ` David Howells
2024-08-23 13:20 ` David Disseldorp
2024-08-28 10:25 ` David Howells
2024-08-28 10:55 ` David Disseldorp
2024-08-28 11:52 ` David Howells
2024-08-28 12:57 ` David Disseldorp
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=af49124840aa5960107772673f807f88@manguebit.com \
--to=pc@manguebit.com \
--cc=ddiss@samba.org \
--cc=dhowells@redhat.com \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox