linux-kernel - Re: [PATCH v4 01/11] nfsd: fix initial getattr on write delegation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87ba8ce7-7c2a-4a9a-b91b-69d016d8e951@oracle.com>
Date: Fri, 27 Dec 2024 12:59:51 -0500
From: Chuck Lever <chuck.lever@...cle.com>
To: Cedric Blancher <cedric.blancher@...il.com>
Cc: linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 01/11] nfsd: fix initial getattr on write delegation

On 12/27/24 2:53 AM, Cedric Blancher wrote:
> On Thu, 5 Sept 2024 at 14:42, Jeff Layton <jlayton@...nel.org> wrote:
>>
>> At this point in compound processing, currentfh refers to the parent of
>> the file, not the file itself. Get the correct dentry from the delegation
>> stateid instead.
>>
>> Signed-off-by: Jeff Layton <jlayton@...nel.org>
>> ---
>>   fs/nfsd/nfs4state.c | 31 +++++++++++++++++++++++--------
>>   1 file changed, 23 insertions(+), 8 deletions(-)
>>
>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>> index df69dc6af467..db90677fc016 100644
>> --- a/fs/nfsd/nfs4state.c
>> +++ b/fs/nfsd/nfs4state.c
> 
> Is this commit going to be backported to Linux 6.6 LTS?

The quoted patch is

  
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/fs/nfsd/nfs4state.c?id=bf92e5008b17f935a6de8b708551e02c2294121c

in the master branch of Linus' tree. This commit has the following tag:

   Fixes: c5967721e106 ("NFSD: handle GETATTR conflict with write 
delegation")

Commit c5967721e106 was merged in 6.9. Thus bf92e5008b17 won't be
backported to kernels earlier than 6.9 unless they also have commit
c5967721e106. It looks like 6.6 LTS does not have that commit.


-- 
Chuck Lever