From: "Chuck Lever" <cel@kernel.org>
To: NeilBrown <neil@brown.name>
Cc: "Tom Rini" <trini@konsulko.com>, "Jörg Sommer" <joerg@jo-so.de>,
"Jeff Layton" <jlayton@kernel.org>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <dai.ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
linux-nfs@vger.kernel.org, "Chuck Lever" <chuck.lever@oracle.com>
Subject: Re: [PATCH 2/2] NFS: NFSERR_INVAL is not defined by NFSv2
Date: Fri, 28 Aug 2026 19:14:40 -0400 [thread overview]
Message-ID: <8eb7450b-70c2-4354-a92a-7a1296cbd118@app.fastmail.com> (raw)
In-Reply-To: <178795659577.3510150.12183147665128116121@noble.neil.brown.name>
On Fri, Aug 28, 2026, at 6:36 PM, NeilBrown wrote:
> On Sat, 29 Aug 2026, Chuck Lever wrote:
>> I'm talking about changing NFSD to return NFSERR_ISDIR, which would
>> be picked up by the first "if" check above, which already exists
>> in U-Boot.
>
> Good idea.
> That matches what OpenSolaris does, which is the closest thing to a real
> standard for NFSv2.
>
> https://web.archive.org/web/20090216190827/http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/fs/nfs/nfs_srv.c
>
> lines 619-624.
Exactly. Patch coming soon.
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next prev parent reply other threads:[~2026-08-28 23:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 0:28 [PATCH 0/2] Address minor issues with status codes Chuck Lever
2025-12-10 0:28 ` [PATCH 1/2] NFSD: Remove NFSERR_EAGAIN Chuck Lever
2025-12-10 0:28 ` [PATCH 2/2] NFS: NFSERR_INVAL is not defined by NFSv2 Chuck Lever
2026-08-28 8:48 ` Jörg Sommer
2026-08-28 11:33 ` NeilBrown
2026-08-28 11:59 ` Jörg Sommer
2026-08-28 13:27 ` Chuck Lever
2026-08-28 20:51 ` Tom Rini
2026-08-28 21:06 ` Chuck Lever
2026-08-28 21:18 ` Tom Rini
2026-08-28 22:04 ` Chuck Lever
2026-08-28 22:12 ` Tom Rini
2026-08-28 22:36 ` NeilBrown
2026-08-28 23:14 ` Chuck Lever [this message]
2025-12-10 0:49 ` [PATCH 0/2] Address minor issues with status codes Jeff Layton
2025-12-10 1:01 ` NeilBrown
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=8eb7450b-70c2-4354-a92a-7a1296cbd118@app.fastmail.com \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=joerg@jo-so.de \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trini@konsulko.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.