public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Krishna Vivek Vitta <kvitta@microsoft.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: Git clone failure
Date: Wed, 25 Sep 2024 21:00:34 +0000	[thread overview]
Message-ID: <ZvR58tnLEMBZC4fa@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <SI2P153MB07185B9AED66870BBAD3C78AD4692@SI2P153MB0718.APCP153.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

On 2024-09-25 at 08:49:11, Krishna Vivek Vitta wrote:
> 
> Hi Brian
> 
> Thanks for the response.
> 
> It is a WSL2 environment with kernel version: 5.15.153. We have used a kernel version 6.6.36.3 as well. Scenario fails there as well.
> 
> root@DESKTOP-OOHD5UG:/sys/kernel/debug/tracing# uname -a Linux DESKTOP-OOHD5UG 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
> 
> Mount point information:
> C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=5,wfd=5)
> 
> We aren't using any sort of file syncing service.
> 
> We have installed a defender software which is marking mount points for FANOTIFY to intercept filesystem events. On removing the marking, git clone succeeds.

My guess is that whatever software you're using to intercept file system
events is causing the "unknown error occurred while reading the
configuration files" message and you should remove that software and
reboot to see if the problem goes away, even though fanotify is enabled.

It's very common that the kind of "defender software" you're using
breaks a variety of software, including Git and Git LFS, and in general,
the recommendation we give in the Git FAQ is that you use only the
system default antivirus (and on Linux or WSL, none, since there is no
default).
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2024-09-25 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 10:47 Git clone failure Krishna Vivek Vitta
2024-09-24 14:20 ` Konstantin Khomoutov
2024-09-24 21:45 ` brian m. carlson
2024-09-25  8:49   ` [EXTERNAL] " Krishna Vivek Vitta
2024-09-25 21:00     ` brian m. carlson [this message]
2024-09-26  7:11       ` Krishna Vivek Vitta
2024-09-26 11:54         ` brian m. carlson

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=ZvR58tnLEMBZC4fa@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=kvitta@microsoft.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