From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Jeuk Kim <jeuk20.kim@gmail.com>
Cc: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
hui81 qi <hui81.qi@samsung.com>,
j-young choi <j-young.choi@samsung.com>,
peng yun <peng.yun@samsung.com>,
qian01 li <qian01.li@samsung.com>,
xing1 he <xing1.he@samsung.com>,
jeuk20 kim <jeuk20.kim@samsung.com>
Subject: Re: [PATCH 0/2] NFSv4/flexfiles: support loosely coupled data servers
Date: Thu, 6 Aug 2026 14:19:55 +0200 (CEST) [thread overview]
Message-ID: <212778944.5657888.1786018795534.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <20260708074433.390161-1-jeuk20.kim@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
----- Original Message -----
> From: "Jeuk Kim" <jeuk20.kim@gmail.com>
> To: "Trond Myklebust" <trondmy@kernel.org>, "Anna Schumaker" <anna@kernel.org>
> Cc: "linux-nfs" <linux-nfs@vger.kernel.org>, "linux-kernel" <linux-kernel@vger.kernel.org>, "Tigran Mkrtchyan"
> <tigran.mkrtchyan@desy.de>, "hui81 qi" <hui81.qi@samsung.com>, "j-young choi" <j-young.choi@samsung.com>, "peng yun"
> <peng.yun@samsung.com>, "qian01 li" <qian01.li@samsung.com>, "xing1 he" <xing1.he@samsung.com>, "jeuk20 kim"
> <jeuk20.kim@samsung.com>
> Sent: Wednesday, 8 July, 2026 09:44:31
> Subject: [PATCH 0/2] NFSv4/flexfiles: support loosely coupled data servers
> RFC 8435 allows a flexfiles data server to be loosely coupled, i.e. an
> NFS server that does not advertise EXCHGID4_FLAG_USE_PNFS_DS via
> EXCHANGE_ID. The client currently ignores the ffdv_tightly_coupled flag
> and treats every DS as tightly coupled, so NFSv4.1+ I/O to a loosely
> coupled DS fails during DS setup.
>
> Patch 2 threads the decoded tightly_coupled flag down to the DS connect
> path and, when it is false, skips the NFS_CS_PNFS flag and the
> is_ds_client() check.
>
> Patch 1 fixes pre-existing NFSv4.0 DS crashes on the same path (the DS
> client has no session).
>
> Jeuk Kim (2):
> NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers
> NFSv4/flexfiles: support loosely coupled data servers
>
> fs/nfs/filelayout/filelayoutdev.c | 2 +-
> fs/nfs/flexfilelayout/flexfilelayout.c | 3 ++-
> fs/nfs/flexfilelayout/flexfilelayoutdev.c | 3 ++-
> fs/nfs/internal.h | 3 ++-
> fs/nfs/nfs4client.c | 5 +++--
> fs/nfs/nfs4session.c | 21 ++++++++++++++-------
> fs/nfs/nfs4session.h | 3 ++-
> fs/nfs/pnfs.h | 3 ++-
> fs/nfs/pnfs_nfs.c | 14 +++++++++-----
> 9 files changed, 37 insertions(+), 20 deletions(-)
>
> --
> 2.43.0
Just checked that the tightly coupled servers configuration is still ok.
Tested-by: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2309 bytes --]
prev parent reply other threads:[~2026-08-06 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 7:44 [PATCH 0/2] NFSv4/flexfiles: support loosely coupled data servers Jeuk Kim
2026-07-08 7:44 ` [PATCH 1/2] NFSv4/flexfiles: fix NULL dereference for NFSv4.0 " Jeuk Kim
2026-07-08 7:44 ` [PATCH 2/2] NFSv4/flexfiles: support loosely coupled " Jeuk Kim
2026-08-06 12:19 ` Mkrtchyan, Tigran [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=212778944.5657888.1786018795534.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=anna@kernel.org \
--cc=hui81.qi@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jeuk20.kim@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peng.yun@samsung.com \
--cc=qian01.li@samsung.com \
--cc=trondmy@kernel.org \
--cc=xing1.he@samsung.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