From: Tom Talpey <tom@talpey.com>
To: Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>,
COMMON INTERNET FILE SYSTEM SERVER
<linux-cifsd-devel@lists.sourceforge.net>
Subject: Re: Processing ASYNC responses
Date: Tue, 22 Jun 2021 14:31:03 -0400 [thread overview]
Message-ID: <bf9d559d-e309-aac2-8406-e151453d8dae@talpey.com> (raw)
In-Reply-To: <CAH2r5mvUXZtY3=LNzt8_icDfUAAeZpzjUK3sEErzpCksFDX2WA@mail.gmail.com>
On 6/22/2021 1:45 PM, Steve French wrote:
> I noticed that the client isn't checking for SMB2_FLAGS_ASYNC_COMMAND
> in the header flags field in the response processing. Are there
> cases where we should be checking for this? See section 3.2.5.1.5 of
> MS-SMB2
The header format is different when this flag is set. Looking
at smb2pdu.h, I don't even see a structure declaration for the
async header! How/where do async responses get processed??
Tom.
prev parent reply other threads:[~2021-06-22 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 17:45 Processing ASYNC responses Steve French
2021-06-22 18:31 ` Tom Talpey [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=bf9d559d-e309-aac2-8406-e151453d8dae@talpey.com \
--to=tom@talpey.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.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