Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Hadrien Grasland
	<grasland-dJj/bURytuEtnUBFBimtzg@public.gmane.org>
Cc: "linux-cifs\@vger.kernel.org"
	<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Share mounts in SMBv1 mode, but fails to mount in SMBv2 mode
Date: Tue, 17 Oct 2017 11:28:38 +0200	[thread overview]
Message-ID: <mps7evuunqx.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <CAH2r5mt+pRqKa+drXNUEZwhK4bJBH9AYyu048QpSkBnqd_XXgw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Yes.  One option we have is to fall back to a lower, less complete info level
> to work around this server bug.

Ok

What do you think about the extra null byte and the wrong offset in the
query info request? It definitely looks like an error to me.

-- 
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)

  parent reply	other threads:[~2017-10-17  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  7:59 Share mounts in SMBv1 mode, but fails to mount in SMBv2 mode Hadrien Grasland
     [not found] ` <144390dd-e0fc-ae98-a645-5972f11d635d-dJj/bURytuEtnUBFBimtzg@public.gmane.org>
2017-10-16 10:11   ` Aurélien Aptel
     [not found]     ` <mpsd15nv1up.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-10-16 11:35       ` Hadrien Grasland
     [not found]         ` <0b17f092-5c81-3b2e-5e48-b2a4c5b4145a-dJj/bURytuEtnUBFBimtzg@public.gmane.org>
2017-10-16 14:51           ` Aurélien Aptel
     [not found]             ` <mpsa80ruowd.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-10-16 16:05               ` Hadrien Grasland
     [not found]                 ` <9e6bb290-6375-2dfe-8d5b-2128fcc9538d-dJj/bURytuEtnUBFBimtzg@public.gmane.org>
2017-10-16 16:37                   ` Steve French
     [not found]                     ` <CAH2r5mt+pRqKa+drXNUEZwhK4bJBH9AYyu048QpSkBnqd_XXgw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-17  9:28                       ` Aurélien Aptel [this message]
2017-10-17  9:44                   ` Aurélien Aptel
2017-10-17 12:47               ` [PATCH] CIFS: do not send invalid input buffer on QUERY_INFO requests Aurelien Aptel
     [not found]                 ` <20171017124717.25955-1-aaptel-IBi9RG/b67k@public.gmane.org>
2017-10-17 13:41                   ` Hadrien Grasland
     [not found]                     ` <f87e7391-b2f0-feaf-3489-686d0368fe64-dJj/bURytuEtnUBFBimtzg@public.gmane.org>
2017-10-18 14:50                       ` Aurélien Aptel
     [not found]                         ` <mpspo9ktsr5.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-10-18 20:20                           ` Hadrien Grasland
2017-10-18 16:53                   ` Steve French
2017-11-21  1:10                   ` Pavel Shilovsky

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=mps7evuunqx.fsf@aaptelpc.suse.de \
    --to=aaptel-ibi9rg/b67k@public.gmane.org \
    --cc=grasland-dJj/bURytuEtnUBFBimtzg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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