linux-kernel - Re: [PATCH] MAINTAINERS: add new entry for pidfd api

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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 14 Jul 2019 15:10:06 -0700
From:   Joe Perches <joe@...ches.com>
To:     Christian Brauner <christian@...uner.io>,
        linux-kernel@...r.kernel.org
Cc:     davem@...emloft.net, gregkh@...uxfoundation.org,
        mchehab+samsung@...nel.org
Subject: Re: [PATCH] MAINTAINERS: add new entry for pidfd api

On Sun, 2019-07-14 at 21:33 +0200, Christian Brauner wrote:
> Add me as a maintainer for pidfd stuff. This way we can easily see when
> changes come in and people know who to yell at.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
> []
> @@ -12567,6 +12567,18 @@ F:	arch/arm/boot/dts/picoxcell*
>  F:	arch/arm/mach-picoxcell/
>  F:	drivers/crypto/picoxcell*
>  
> +PIDFD API
> +M:	Christian Brauner <christian@...uner.io>
> +L:	linux-kernel@...r.kernel.org
> +S:	Maintained
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git
> +F:	samples/pidfd/
> +F:	tools/testing/selftests/pidfd/
> +K:	(?i)pidfd
> +K:	(?i)clone3

These seem fairly specific without false positives.

> +K:	\b(clone_args|kernel_clone_args)\b
> +N:	pidfd

This one I'd suggest using 2 F: patterns instead
as the patterns are more comprehensive and do not
use git history when looked up with get_maintainer

F:	samples/pidfd/
F:	tools/testing/selftests/pidfd/