From: "Aurélien Aptel" <aaptel@suse.com>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH] CIFS: fix FSCTL_SET_REPARSE_POINT SMB2_ioctl() call
Date: Tue, 05 Mar 2019 12:47:46 +0100 [thread overview]
Message-ID: <87woldmtjx.fsf@suse.com> (raw)
In-Reply-To: <CAH2r5msqeMuatKpE2Kg6A+935zJ+yeocVHQTipQechbbgNrEXw@mail.gmail.com>
Steve French <smfrench@gmail.com> writes:
> Without this change the ioctl() fails with INVALID_PARAMETER.
> Since SET_REPARSE_POINT has no output, set the max output response
> size to zero.
Note that this is more of a work around, I didn't intend to send this
yet. I haven't tried to figure out which cases we were violating and
where was the underlying issue.
> If either InputCount, MaxInputResponse, or MaxOutputResponse is
> greater than Connection.MaxTransactSize, the server SHOULD<306> fail
> the request with STATUS_INVALID_PARAMETER.
possible
> The server MUST fail the request with STATUS_INVALID_PARAMETER in the following cases:
>
> * If InputOffset is greater than zero but less than (size of SMB2
> header + size of the SMB2 IOCTL request not including Buffer) or
> if InputOffset is greater than (size of SMB2 header + size of the
> SMB2 IOCTL request).
input related, nope
> * If OutputOffset is greater than zero but less than (size of SMB2
> header + size of the SMB2 IOCTL request not including Buffer) or if
> OutputOffset is greater than (size of SMB2 header + size of the SMB2
> IOCTL request).
doesn't involve MaxOutputResponse, nope
> * If (InputOffset + InputCount) is greater than (size of SMB2 header +
> size of the SMB2 IOCTL request).
input related, nope
> * If (OutputOffset + OutputCount) is greater than (size of SMB2 header
> + size of the SMB2 IOCTL request).
doesn't involve MaxOutputResponse, nope
> * If OutputCount is greater than zero and OutputOffset is less
> than (InputOffset + InputCount).
doesn't involve MaxOutputResponse, nope
So it seems to me only possible explanation is the first, i.e.
MaxOutputResponse > Connection.MaxTransactSize, somehow.
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-03-05 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 6:14 [PATCH] CIFS: fix FSCTL_SET_REPARSE_POINT SMB2_ioctl() call Steve French
2019-03-05 6:56 ` ronnie sahlberg
2019-03-05 11:47 ` Aurélien Aptel [this message]
2019-03-05 15:00 ` Aurélien Aptel
2019-03-05 15:40 ` Aurélien Aptel
2019-03-05 15:49 ` 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=87woldmtjx.fsf@suse.com \
--to=aaptel@suse.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