Aw: Re: linux git init/clone on Netapp NTFS security style volumes

From: github@online.ms <github@online.ms>
Date: Jul 8, 2024, 16:50 UTC
Message-ID: <trinity-3d633a4a-10c6-444e-9e5c-79330941ddb6-1720457458565@3c-app-webde-bap34>
In-Reply-To: <ZoryWtGqsD9iIafI@tapette.crustytoothpaste.net>

Show 30 quoted lines

> Gesendet: Sonntag, 07. Juli 2024 um 21:54 Uhr
> Von: "brian m. carlson" <sandals@crustytoothpaste.net>
> An: github@online.ms
> Cc: git@vger.kernel.org
> Betreff: Re: linux git init/clone on Netapp NTFS security style volumes
>
> On 2024-07-06 at 19:35:30, github@online.ms wrote:
> > Hello,
> >  
> > I'm trying to execute git init and git clone operations on a linux
> > client that mounts a Netapp volume with NTFS Security Style. Meaning
> > the client is Linux based but the filesystem is managed from Windows
> > side - especially linux chmod operations are not permitted.
> >  
> > Maybe a new CLI option might be helpful to skip those chmod operations.
> 
> I'm not surprised by this, because Windows volumes under WSL also have
> the same problem.  However, I don't see the behaviour you describe when
> creating a new file system with NTFS on Linux and using ntfs-3g to
> mount with default options.  In my case, everything works just fine.
> 
> Note that I didn't try using the old non-FUSE driver because that's
> deprecated and I don't believe it's available anymore in Debian sid.
> 
> What OS (including version) are you using and how are you mounting the
> file system?
> -- 
> brian m. carlson (they/them or he/him)
> Toronto, Ontario, CA
>

The feature is very specific to Netapp. The (Netapp) volume is mounted using NFSv4, but chmod operations are not allowed as permissions have to be managed using Windows. Currently, OS is ubuntu 22.04. I'm confident that the distribution does not make a difference.

Following section of the code should be skipped for given case. https://github.com/git/git/blob/master/config.c#L3434-L3438

		if (chmod(get_lock_file_path(&lock), st.st_mode & 07777) < 0) {
			error_errno(_("chmod on %s failed"), get_lock_file_path(&lock));
			ret = CONFIG_NO_WRITE;
			goto out_free;
		}

I'm looking for some advice how to best skip or catch this section.

In addition, I came across this Netapp setting which might just ignore the chmod operations without Client side failure. I haven't tested it yet. https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_I_set_UNIX_style_permissions_from_an_NFS_mount_on_an_NTFS_qtree

Thank You

Josef