From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Jan-Marek Glogowski
<glogow-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Fix SMB2_TREE_CONNECT requests with the wrong TreeId
Date: Fri, 17 Feb 2017 19:37:48 +0100 [thread overview]
Message-ID: <mpsfujchddv.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <41c29ddb-eafa-dc03-ab2b-864919aa4192-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
I have reproduced the issue and can confirm your latest patch fixes it.
Reviewed-by: Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>
Tested-by: Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>
--
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)
prev parent reply other threads:[~2017-02-17 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 17:44 Fix SMB2_TREE_CONNECT requests with the wrong TreeId Jan-Marek Glogowski
[not found] ` <25f3edd0-3abf-f541-d7f8-54ae1dbac081-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
2017-02-13 8:14 ` Aurélien Aptel
[not found] ` <066cc0b2-0e63-8cf6-7d46-578e524cf3bf@fbihome.de>
[not found] ` <066cc0b2-0e63-8cf6-7d46-578e524cf3bf-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
2017-02-14 16:02 ` Aurélien Aptel
[not found] ` <mpszihohiad.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-02-14 16:39 ` Jan-Marek Glogowski
[not found] ` <1a130ab9-84bf-82cb-8c23-e071c286822c-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
2017-02-15 13:05 ` Aurélien Aptel
[not found] ` <mpswpcrhaet.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-02-15 14:24 ` Jan-Marek Glogowski
[not found] ` <461c47b3-a4ae-c21c-26c5-b33dd19f2b37-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
2017-02-17 10:55 ` Jan-Marek Glogowski
[not found] ` <41c29ddb-eafa-dc03-ab2b-864919aa4192-iG8UcmBuX++ELgA04lAiVw@public.gmane.org>
2017-02-17 18:37 ` Aurélien Aptel [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=mpsfujchddv.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=glogow-iG8UcmBuX++ELgA04lAiVw@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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 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.