From: "Chuck Lever" <cel@kernel.org>
To: "Cen Zhang (Microsoft Security FORGE Labs)"
<cenzhang@linux.microsoft.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: AutonomousCodeSecurity@microsoft.com,
"Dai Ngo" <Dai.Ngo@oracle.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Jeff Layton" <jlayton@kernel.org>,
kys@microsoft.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, NeilBrown <neil@brown.name>,
"Olga Kornievskaia" <okorniev@redhat.com>,
stable@vger.kernel.org, tgopinath@linux.microsoft.com,
"Tom Talpey" <tom@talpey.com>,
xmei5@asu.edu
Subject: Re: [PATCH] nfsd: hold cl_lock in client_has_state()
Date: Fri, 04 Sep 2026 12:36:47 -0400 [thread overview]
Message-ID: <6962f43d-10c4-4530-807a-def951c4eb9c@app.fastmail.com> (raw)
In-Reply-To: <20260904151213.44891-1-cenzhang@linux.microsoft.com>
On Fri, Sep 4, 2026, at 11:12 AM, Cen Zhang (Microsoft Security FORGE Labs) wrote:
> On Fri, Aug 28, 2026 at 07:29:11AM +0200, Greg KH wrote:
>> Please use your microsoft.com email address, and not a random gmail.com
>> address. It's kind of odd that Microsoft would have to rely on Google
>> to send kernel patches :)
>
> Thanks for pointing this out. I now have cenzhang@linux.microsoft.com
> set up and will use it for future kernel submissions.
>
> Chuck, since the patch is already in nfsd-testing, please let me know if
> I should send a v2 from this address to update the author email.
I don't see a need to resend, but I'm sure someone will explain it to
me if I'm incorrect. :-)
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next prev parent reply other threads:[~2026-09-04 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 4:19 Cen Zhang (Microsoft Security FORGE Labs)
2026-08-28 5:29 ` Greg KH
2026-08-28 12:33 ` Cen Zhang (Microsoft)
2026-08-28 13:45 ` Chuck Lever
2026-08-29 5:52 ` Greg Kroah-Hartman
2026-09-04 15:12 ` Cen Zhang (Microsoft Security FORGE Labs)
2026-09-04 16:36 ` Chuck Lever [this message]
2026-08-29 15:53 ` Chuck Lever
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=6962f43d-10c4-4530-807a-def951c4eb9c@app.fastmail.com \
--to=cel@kernel.org \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=Dai.Ngo@oracle.com \
--cc=bfields@fieldses.org \
--cc=cenzhang@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tgopinath@linux.microsoft.com \
--cc=tom@talpey.com \
--cc=xmei5@asu.edu \
/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
all inboxes | Powered by JetHome®