From: Trond Myklebust <trondmy@hammerspace.com>
To: "ovt@google.com" <ovt@google.com>
Cc: "anna@kernel.org" <anna@kernel.org>,
"jbongio@google.com" <jbongio@google.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] NFSv4: fix a mount deadlock in NFS v4.1 client
Date: Thu, 26 Sep 2024 20:02:04 +0000 [thread overview]
Message-ID: <b34ad21a057198601a82edd0b7f24baf2700a1d7.camel@hammerspace.com> (raw)
In-Reply-To: <CACGj0ChbuJ=p6WT62rYWarB=E6Uf3Cs_rz7icDPo5uH3GgVpmQ@mail.gmail.com>
Hi Oleksandr
On Mon, 2024-09-23 at 13:15 -0700, Oleksandr Tymoshenko wrote:
> Hi Trond,
>
> Following up on this: do you have plans to submit the patch you
> proposed
> or do you want me to rework my submission along the lines you
> proposed?
Let's just merge the patch I proposed. I've sent a "clean" copy to Anna
to send upstream in the next bugfix pull.
Thanks!
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2024-09-26 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 0:57 [PATCH] NFSv4: fix a mount deadlock in NFS v4.1 client Oleksandr Tymoshenko
2024-09-06 0:58 ` kernel test robot
2024-09-08 16:48 ` Trond Myklebust
2024-09-09 16:36 ` [PATCH 6.1.y] net: tls: handle backlogging of crypto requests Oleksandr Tymoshenko
2024-09-09 17:56 ` Trond Myklebust
2024-09-09 23:06 ` [PATCH] NFSv4: fix a mount deadlock in NFS v4.1 client Oleksandr Tymoshenko
2024-09-10 0:22 ` Trond Myklebust
2024-09-10 21:08 ` Oleksandr Tymoshenko
2024-09-23 20:15 ` Oleksandr Tymoshenko
2024-09-26 20:02 ` Trond Myklebust [this message]
2024-09-09 17:46 ` Oleksandr Tymoshenko
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=b34ad21a057198601a82edd0b7f24baf2700a1d7.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna@kernel.org \
--cc=jbongio@google.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ovt@google.com \
--cc=stable@vger.kernel.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