From: Trond Myklebust <trondmy@hammerspace.com>
To: "wanghai38@huawei.com" <wanghai38@huawei.com>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 4/4] Revert "SUNRPC: attempt AF_LOCAL connect on setup"
Date: Sat, 30 Apr 2022 00:56:43 +0000 [thread overview]
Message-ID: <e10869294d391c9521f35c8564c73a45c21131b5.camel@hammerspace.com> (raw)
In-Reply-To: <20220429173629.621418-4-trondmy@kernel.org>
On Fri, 2022-04-29 at 13:36 -0400, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> This reverts commit 7073ea8799a8cf73db60270986f14e4aae20fa80.
>
> We must not try to connect the socket while the transport is under
> construction, because the mechanisms to safely tear it down are not
> in
> place.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Sorry. I intended to add a
"Reported-by: wanghai (M) <wanghai38@huawei.com>"
That has been added to the version in my "testing" branch.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-04-30 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 17:36 [PATCH v2 1/4] SUNRPC: Don't leak sockets in xs_local_connect() trondmy
2022-04-29 17:36 ` [PATCH v2 2/4] SUNRPC: Ensure timely close of disconnected AF_LOCAL sockets trondmy
2022-04-29 17:36 ` [PATCH v2 3/4] SUNRPC: Ensure gss-proxy connects on setup trondmy
2022-04-29 17:36 ` [PATCH v2 4/4] Revert "SUNRPC: attempt AF_LOCAL connect on setup" trondmy
2022-04-30 0:56 ` Trond Myklebust [this message]
2022-05-05 9:19 ` wanghai (M)
2022-05-05 14:54 ` wanghai (M)
2022-05-09 10:28 ` [PATCH v2 3/4] SUNRPC: Ensure gss-proxy connects on setup wanghai (M)
2022-05-09 11:22 ` wanghai (M)
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=e10869294d391c9521f35c8564c73a45c21131b5.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=wanghai38@huawei.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 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.