Linux nfsd always returns { .minor=0, .major=0 } for FATTR4_WORD0_FSID, why?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Linux nfsd always returns { .minor=0, .major=0 } for FATTR4_WORD0_FSID, why?
From: Lionel Cons <lionelcons1972@xxxxxxxxx>
Date: Mon, 20 Jan 2025 15:09:54 +0100

Does anyone know why the per-fileobjet attribute FATTR4_WORD0_FSID
 always returns { .minor=0, .major=0 } for a Linux nfsd?
This does not sound right.

Ref https://datatracker.ietf.org/doc/html/rfc5661#section-5.8.1.9

Lionel

Follow-Ups:
- Re: Linux nfsd always returns { .minor=0, .major=0 } for FATTR4_WORD0_FSID, why?
  - From: Lionel Cons

Prev by Date: Re: [RFC PATCH 03/24] crypto: Add 'krb5enc' hash and cipher AEAD algorithm
Next by Date: Re: [RFC PATCH 03/24] crypto: Add 'krb5enc' hash and cipher AEAD algorithm
Previous by thread: [PATCH] NFSv4: harden nfs4_get_uniquifier() function
Next by thread: Re: Linux nfsd always returns { .minor=0, .major=0 } for FATTR4_WORD0_FSID, why?
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux USB Development] [Linux Media Development] [Video for Linux] [Linux NILFS] [Linux Audio Users] [Yosemite Info] [Linux SCSI]

Powered by Linux