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]
Date:   Tue, 28 Sep 2021 06:19:17 +0200
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Steve French <sfrench@...ba.org>,
        Steve French <stfrench@...rosoft.com>,
        Namjae Jeon <linkinjeon@...nel.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Hyunchul Lee <hyc.lee@...il.com>, linux-cifs@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: No fs/cifs_common directory in kernel tree

Dear Steve, dear Namjae,

I am tracking consistency of the MAINTAINERS file and noticed:

Commit 332c404a55ef ("cifs: add cifs_common directory to MAINTAINERS
file") and commit e9e3d5f9e34c ("MAINTAINERS: ksmbd: add cifs_common
directory to ksmbd entry") add the file entry fs/cifs_common/ to the
sections COMMON INTERNET FILE SYSTEM CLIENT (CIFS) and KERNEL SMB3
SERVER (KSMBD).

However, as of now, there is no fs/cifs_common/ directory in the
mainline tree or in the latest linux-next tree.

Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:

  warning: no file matches    F:    fs/cifs_common/

Are there more commits to come that will add or move files to
fs/cifs_common/, or did you decide against introducing fs/cifs_common/
in the course of the development and these commits are left-over from
a previous development?

Best regards,

Lukas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ