linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>
Subject: Re: [SMB3] [PATCH] Pass through FSCTL for tools like smbinfo
Date: Thu, 14 Mar 2019 20:09:58 -0500	[thread overview]
Message-ID: <CAH2r5msJmCOYAviUc0u=3ObSoOpz9Yddc8PjtBgWyh-p86dJPA@mail.gmail.com> (raw)
In-Reply-To: <CAN05THRPnkQd2ANuQtHJYVY7ViuTk8y4jo0kbM37gv-Wj9pn6Q@mail.gmail.com>

I think this is going to be very helpful - there are many examples
where I have needed to write a quick script to query debug information
or metadata only available via FSCTL

On Thu, Mar 14, 2019 at 7:42 PM ronnie sahlberg
<ronniesahlberg@gmail.com> wrote:
>
> Note that we pass NULL as indata for SMB2_ioctl_init() so for the time
> being we can only use this for those ioctl/fcntl that does not
> write data to the server. But there are very many of those.
>
> We can start populating smb2info.c with handlers for this and once it
> all looks good we can add support to also write to the server (which
> will be easy to do but it would make the patch bigger)
>
> On Fri, Mar 15, 2019 at 10:21 AM Steve French <smfrench@gmail.com> wrote:
> >
> > Forwarding Ronnie's patch to the broader list
> >
> > For debugging purposes we often have to be able to query
> > additional information only available via SMB3 FSCTL
> > from the server from user space tools (e.g. like
> > cifs-utils's smbinfo).  See MS-FSCC and MS-SMB2 protocol
> > specifications for more details.
> >
> > --
> > Thanks,
> >
> > Steve



-- 
Thanks,

Steve

      reply	other threads:[~2019-03-15  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  0:21 [SMB3] [PATCH] Pass through FSCTL for tools like smbinfo Steve French
2019-03-15  0:42 ` ronnie sahlberg
2019-03-15  1:09   ` Steve French [this message]

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='CAH2r5msJmCOYAviUc0u=3ObSoOpz9Yddc8PjtBgWyh-p86dJPA@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=samba-technical@lists.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;
as well as URLs for NNTP newsgroup(s).