Re: [EXTERNAL] Re: Git clone fails in p9 file system marked with FANOTIFY

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

 



On Thu, Sep 26, 2024 at 1:17 PM Krishna Vivek Vitta
<kvitta@xxxxxxxxxxxxx> wrote:
>
> Hi Amir,
>
> Yes, and my guess is that the MDE software running on your machine had reacted
> fanotify_read() error as a threat and removed the .config file, that is why it could not be found by the open syscall??
> >>>>No, that can't  be because I have performed the exercises by uninstalling MDE software running in WSL(5.15 and 6.3).
>
> Git clone succeeds, but the listener terminates as you see in your machine in standard linux. It is the same manifestation.
>
> In MDE software, Fanotify marking was just being done only with CLOSE_WRITE in mask, while the example code(fanotify listener) was having mask OPEN_PERM | CLOSE_WRITE.
>
> I shall include OPEN_PERM in the mask in MDE and then invoke git clone and then see if it succeeds.
>
> Can you explain the significance of OPEN_PERM and its relation with CLOSE_WRITE ?

I cannot explain but anyway the impact of the reference that fanotify
takes in the dentry
is not exactly clear to us yet.

In my test OPEN_PERM | CLOSE_WRITE also got fanotify_read() error ENOENT
see my email.

Thanks,
Amir.





[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux