From: James Montgomery <james_montgomery@disroot.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-cifs@vger.kernel.org, Steve French <smfrench@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Tom Talpey <tom@talpey.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ksmbd: defer destroy_previous_session() until after NTLM authentication
Date: Fri, 03 Jul 2026 15:26:32 -0400 [thread overview]
Message-ID: <66a2f0233be32a443d8c6ed2eb662f7e@disroot.org> (raw)
In-Reply-To: <CAKYAXd-t2Oz4ZM8BWkJ7uKciaGo=akTMPUEFy2_Z3cx0abHptQ@mail.gmail.com>
On Fri, 3 Jul 2026, Namjae Jeon wrote:
> Is there any specific reason for not moving this line together?
No, there is no specific reason. You are right. I'll send a v2 with
both the assignment and the condition moved together after auth.
Thanks for the review.
James
prev parent reply other threads:[~2026-07-03 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 15:54 [PATCH] ksmbd: defer destroy_previous_session() until after NTLM authentication James Montgomery
2026-07-03 5:01 ` Namjae Jeon
2026-07-03 19:26 ` James Montgomery [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=66a2f0233be32a443d8c6ed2eb662f7e@disroot.org \
--to=james_montgomery@disroot.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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