From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>, Stable <stable@vger.kernel.org>
Subject: [PATCH 0/1] FSCTL write support
Date: Thu, 11 Apr 2019 12:20:16 +1000 [thread overview]
Message-ID: <20190411022017.24942-1-lsahlber@redhat.com> (raw)
Steve,
This patch adds code to allow us to do fsctl passthrough for fsctl types that
need to pass data to the server.
This not only needs to pass the blob to the server but also need to decode
the access-type part of the fsctl code and change the arguments to the CREATE
accordingly.
The values for the access are from wireshark traces of win16 -> win16.
For now I only implement the special handling we need for
FILE_READ_WRITE_ACCESS.
We can add the others as needed and as we we discover them while adding
new functions to smbinfo.
next reply other threads:[~2019-04-11 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 2:20 Ronnie Sahlberg [this message]
2019-04-11 2:20 ` [PATCH] cifs: Add support for FSCTL passthrough that write data to the server Ronnie Sahlberg
2019-04-11 2:48 ` Steve French
2019-04-11 17:49 ` Pavel Shilovsky
2019-04-11 18:56 ` Steve French
2019-04-11 20:02 ` ronnie sahlberg
2019-04-11 20:00 ` ronnie sahlberg
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=20190411022017.24942-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.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 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.