Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Alan Maxwell <amaxwell@fedex.com>
To:     "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: nfsv4 client idmapper issue
Thread-Topic: nfsv4 client idmapper issue
Thread-Index: AdjN5dNv/53QmQ7mSiWe6weV81FGkQ==
Date:   Wed, 21 Sep 2022 18:13:21 +0000
Message-ID: <DS0PR12MB6486987EC76AD88C7A80D229C84F9@DS0PR12MB6486.namprd12.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
dlp-version: 11.6.300.5
dlp-reaction: no-action
dlp-product: dlpe-windows
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?RbxUpPe62K3Jvbv9dp5M55HkfZ6vACEw1PtB0Mm0PAsbcX75E6vFynjXSXO3?=
 =?us-ascii?Q?bJkBZrPgusYTNqc6D3guIdWTmzZSDg9kxjCgnYM6fatKx1rjNgcH5O+jBkce?=
 =?us-ascii?Q?37wKzPw/PrOHfE1i4vciWr+YrKsp46q+T3a2Lk04kVp9zrf0wELUkVMIvai8?=
 =?us-ascii?Q?aItFvJNz3McPCtlJWWDDsAMAWqvq1bWOlPWdi6UyZuWCTG8i4Ovv580kcUX3?=
 =?us-ascii?Q?iEHvyUe0MSIZ5EDoMJOHk7ipUPlrflUBWj7fZQswPtQUDJmKU86yNPTnFkRx?=
 =?us-ascii?Q?/CtfNRsiYo5RWbB6VLU9WanE7c1JU5PFKLblXL44mzC9Sdg9nl9SLnZF4dOf?=
 =?us-ascii?Q?fuw7355NOKc4Wht+io9lJFZkniF5kweMpoA0E2EHMqqPfgATNDV/PbJrD3hy?=
 =?us-ascii?Q?KYj0L0KJz+OQTGFJWQCxF+B5zt0utfFaeBPA8iUArb7BBQwbIPNhSof96EJ5?=
 =?us-ascii?Q?3lxuJpQAnW9lckSBlVi6CY27yICXVpbtRBla7FGMKS7c9A/RBQpk1oMB2ANm?=
 =?us-ascii?Q?GCF+KviKQYtr2LWd+HJ7CzhiBXBH1g8CRYCWUVUtnnACW7bZVj3p6QkdzaJa?=
 =?us-ascii?Q?GIN9A3G780Mk+DayVBYX1AVrGwra9CIUO4ljLfabUPRpnW1o4Hyi6B9g3zY/?=
 =?us-ascii?Q?YGcDUHxm6j/NWicF1oYQgoZ/acs9+tFECIqtk4dZBBK4eRfB0rDiRCacAG6C?=
 =?us-ascii?Q?Tn6V+AtO16njKLmxQMwftihsOn84qO/X5natrnj90FhhIJddgy6PCZYOV+ny?=
 =?us-ascii?Q?0olK8LmPfz5Zws0Vfmbk4virUJmKkVvsx4KUNVvXY9/wJ51ODAD/BsYI94r5?=
 =?us-ascii?Q?WCEgZYxKJxzbCAvVY2pBQpVbbTiuchD5vG7pMEnEJ5lKAj/7ygU4b3oUNI/L?=
 =?us-ascii?Q?9r5NjzPenPlZZOM2BoqllFS+5xC/vbebhlXvIjb/ihes1dnr+Syox/hRKoHm?=
 =?us-ascii?Q?sWorS2jjpL8wq4+opa76D/47w5B8bI0kHcx/AsxUX0VKkuP5StWDUYO2p/J3?=
 =?us-ascii?Q?MtxiUamiFSITGOhOebGYS8456BYvIg/k7eYh9FhaXF7I3CVS5+M+5X25s0/u?=
 =?us-ascii?Q?uAqeIc4+EgnuJFQ11Mgyb5CvFAMKFv/6DliAc+Y22Xg9CD139Ht748CuUmnb?=
 =?us-ascii?Q?GRzSiQ6T4i1xFUh9Cu2yBqaWNgAGUUdEAMtIQ5ldCYFSarZk5ijLo0Oe4O84?=
 =?us-ascii?Q?Xyh/UQyclyUHhEVWF4viHMwD5EzgjV1fMuC+/HUig7zxxPEV4WIkE/YG/M0r?=
 =?us-ascii?Q?cGWxpDgaONyddfy7kwaOUn4KCbxOTdEqogHu8LkTKvz92BGaJZvnVDHXOMja?=
 =?us-ascii?Q?68OkYTjcpZoqdoMrFlWmPPeI5LFK4Tl5pGgsx4TYIGyVsSp7XnL6Rd3eMNVw?=
 =?us-ascii?Q?p/wS73IeTnVUMHCEUUSDeTAWdIYEnwyl4bJrnPYBoO7sTKIcMTOtcsQ/ynO8?=
 =?us-ascii?Q?/gjH/aFvdZN0prvAl7yzeoVFmGuwoQCSAvdUE5pA1hZpUv7bZLxzFK47n8gy?=
 =?us-ascii?Q?B4N2Yvu+74e73jzFfg6sJTIY62wkKjFgCWn+L3Iukn8gf44jGkxtJhtCr8wt?=
 =?us-ascii?Q?0tsPybdxbYDPExC6iFmnuk5gAzzFYmmWXpQ4BJgB?=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: fedex.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DS0PR12MB6486.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bc167d6f-5b60-468c-8fd8-08da9bfcf77b
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Sep 2022 18:13:21.2011
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b945c813-dce6-41f8-8457-5a12c2fe15bf
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Qv+CE+gmjwus7meA6bEBAM8f9nsZ/VdlFUVHFeaBPbwpzh5qpC2uQ0ct9WWUSg1F2tDCsllVe9kcMUWMcrBF0g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL1PR12MB5825
X-Proofpoint-ORIG-GUID: 8R5r-gT3EMJoMND4-WoGnKL96vlT8Fjs
X-Proofpoint-GUID: 8R5r-gT3EMJoMND4-WoGnKL96vlT8Fjs
X-Proofpoint-Virus-Version: vendor=baseguard
 engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.528,FMLib:17.11.122.1
 definitions=2022-09-21_09,2022-09-20_02,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 malwarescore=0
 bulkscore=0 mlxscore=0 spamscore=0 mlxlogscore=999 priorityscore=1501
 phishscore=0 clxscore=1015 suspectscore=0 adultscore=0 lowpriorityscore=0
 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2209130000
 definitions=main-2209210122
X-Spam-Status: No, score=-18.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,
        DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
        ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,
        USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham
        autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
        lindbergh.monkeyblade.net
Precedence: bulk
List-ID: <linux-nfs.vger.kernel.org>
X-Mailing-List: linux-nfs@vger.kernel.org

I am reporting an issue, not a fault or bugreport.
NFS client : Redhat 7 kernel: 3.10.0-1160.71.1.el7.x86_64.
The issue lies with the feature that nfs client that: if an nfs server reje=
cts an unmapped uid or gid, then the client will automatically switch back =
to using the idmapper.

Our particular configuration of nfsv4 server and client are based on using =
numeric uidNumber and gidNumber communication.  The nfs server we are using=
 , OneFS (Dell/EMC/Isilon) has a setting explicitly for this use: "Do not s=
end names".  We have this set and our testing showed working 100% with our =
nfs client.  The main driver for us using this feature is that our uid's ar=
e numeric.  That causes issues with commands like chown and apparently NFS =
setattr.  Once we realized that, we set the numeric setting and everything =
worked as planned.
Our problem with the feature comes due to a  simple mistake made by an Admi=
n:
 chgrp groupnotvalid file
When the admin issued a chgrp, but that group does not exist in the directo=
ry service for the NFS server, the NFS server rejected the change.  Then th=
e feature kicked in that "client will automatically switch back to using th=
e idmapper. " Which did make changes, the /proc/self/mountstats showing the=
 caps=3D0x7fff instead of 0xffff.
The only solution to get the mount to work as originally configured is to u=
mount/mount the share.
Bottom line: Our environment can not support idmapping.  Having the feature=
 to disable it and that disable be forceful and not something the kernel ca=
n decide to re-enable.
We would envision that if an invalid chown/chgrp were issued, to simply ret=
urn an error, report that the chown/chgrp were not applied and simply leave=
 the nfsmount as is.

Alan Maxwell | Sr. System Programmer | Platinum Infrastructure|20 FedEx Pkw=
y 1st Fl Vert,Collierville, TN 38017