lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <25817189-49a7-c64f-26ee-78d4a27496b6@huawei.com>
Date:   Tue, 8 Sep 2020 16:01:48 +0800
From:   Xiaoming Ni <nixiaoming@...wei.com>
To:     <jack@...e.cz>, <amir73il@...il.com>
CC:     <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        <wangle6@...wei.com>
Subject: Question: Why is there no notification when a file is opened using
 filp_open()?

The file opening action on the system may be from user-mode sys_open() 
or kernel-mode filp_open().
Currently, fsnotify_open() is invoked in do_sys_openat2().
But filp_open() is not notified. Why? Is this an omission?

Do we need to call fsnotify_open() in filp_open() or  do_filp_open() to 
ensure that both user-mode and kernel-mode file opening operations can 
be notified?

Thanks
Xiaoming Ni

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ