Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Olga Kornievskaia <okorniev@redhat.com>,
	jlayton@kernel.org, linux-nfs@vger.kernel.org,
	Dai.Ngo@oracle.com, tom@talpey.com, NeilBrown <neilb@suse.de>
Subject: Re: [PATCH 3/3] nfsd: reset access mask for NLM calls in nfsd_permission
Date: Mon, 31 Mar 2025 10:49:18 -0400	[thread overview]
Message-ID: <f9c6169d-edc6-47be-b6db-ec7eaaeb33cc@oracle.com> (raw)
In-Reply-To: <174337981427.9342.10894606812592381794@noble.neil.brown.name>

On 3/30/25 8:10 PM, NeilBrown wrote:
> On Mon, 31 Mar 2025, Olga Kornievskaia wrote:
>>
>> This code would also make the behaviour consistent with prior to
>> 4cc9b9f2bf4d. But now I question whether or not the new behaviour is
>> what is desired going forward or not?
>>
>> Here's another thing to consider: the same command done over nfsv4
>> returns an error. I guess nobody ever complained that flock over v3
>> was successful but failed over v4?
> 
> That is useful.  Given that:
>  - exclusive flock without write access over v4 never worked
>  - As Tom notes, new man pages document that exclusive flock without write access
>    isn't expected to work over NFS
>  - it is hard to think of a genuine use case for exclusive flock without
>    write access
> 
> I'm inclined to leave this code as it is and declare your failing test
> to no longer be invalid.

For the record, which test exactly is failing? Is there a BugLink?


> That is technically a regression, but
> regressions only matter if people notice them (and complain to Linus).
> No harm - no fowl.

-- 
Chuck Lever

  reply	other threads:[~2025-03-31 14:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22  0:13 [PATCH 0/3] access checking fixes for NLM under security policies Olga Kornievskaia
2025-03-22  0:13 ` [PATCH 1/3] nfsd: fix access checking for NLM under XPRTSEC policies Olga Kornievskaia
2025-04-07 19:44   ` Jeff Layton
2025-03-22  0:13 ` [PATCH 2/3] nfsd: adjust nfsd4_spo_must_allow checking order Olga Kornievskaia
2025-04-07 15:36   ` Jeff Layton
2025-04-07 15:56     ` Olga Kornievskaia
2025-04-07 15:59       ` Jeff Layton
2025-04-07 17:17         ` Olga Kornievskaia
2025-04-07 17:47           ` Jeff Layton
2025-04-07 18:02             ` Olga Kornievskaia
2025-03-22  0:13 ` [PATCH 3/3] nfsd: reset access mask for NLM calls in nfsd_permission Olga Kornievskaia
2025-03-27 23:54   ` NeilBrown
2025-03-28  0:36     ` Olga Kornievskaia
2025-03-28  1:43       ` NeilBrown
2025-03-28 12:43         ` Chuck Lever
2025-03-28 15:13         ` Olga Kornievskaia
2025-03-28 21:53           ` NeilBrown
2025-03-28 23:29             ` Tom Talpey
2025-03-30 16:17               ` Chuck Lever
2025-03-30 16:12             ` Olga Kornievskaia
2025-03-31  0:10               ` NeilBrown
2025-03-31 14:49                 ` Chuck Lever [this message]
2025-03-31 18:24                   ` Olga Kornievskaia
2025-04-01 22:24                     ` NeilBrown
2025-04-01 22:57                       ` Olga Kornievskaia
2025-04-01 23:18                         ` NeilBrown
2025-04-07 15:57             ` Jeff Layton
2025-04-08 20:40               ` Benjamin Coddington
2025-03-22 15:08 ` [PATCH 0/3] access checking fixes for NLM under security policies cel
2025-03-28  0:07 ` 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=f9c6169d-edc6-47be-b6db-ec7eaaeb33cc@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=aglo@umich.edu \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.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