From: Solar Designer <solar@openwall.com>
To: Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com, Mrinal Pandey <mrinalmni@gmail.com>
Subject: Re: [PATCH] scripts: Add intended executable mode and SPDX license
Date: Thu, 27 Aug 2020 15:06:53 +0200 [thread overview]
Message-ID: <20200827130653.GA25408@openwall.com> (raw)
In-Reply-To: <20200827092405.b6hymjxufn2nvgml@mrinalpandey>
[CC list trimmed]
On Thu, Aug 27, 2020 at 02:54:05PM +0530, Mrinal Pandey wrote:
> mode change 100644 => 100755 scripts/gcc-plugins/gen-random-seed.sh
This is basically the only change relevant to the contribution initially
made via kernel-hardening, and in my opinion (and I am list admin) isn't
worth bringing to the list. Now we have this bikeshed thread in here
(and I'm guilty for adding to it), and would have more (which I hope
this message of mine will prevent) if changes to something else in the
patch(es) are requested (which Greg KH sort of already did).
I recall we previously had lots of "similar" bikeshedding in here when
someone was converting the documentation to rST. The more bikeshedding
we have, the less actual kernel-hardening work is going to happen,
because the list gets the reputation of yet another kernel maintenance
list rather than the place where actual/potential new contributions to
improve the kernel's security are discussed, and because bikeshedding
makes the most capable people unsubscribe or stop paying attention.
How about we remove kernel-hardening from the MAINTAINERS entries it's
currently in? -
GCC PLUGINS
M: Kees Cook <keescook@chromium.org>
R: Emese Revfy <re.emese@gmail.com>
L: kernel-hardening@lists.openwall.com
S: Maintained
F: Documentation/kbuild/gcc-plugins.rst
F: scripts/Makefile.gcc-plugins
F: scripts/gcc-plugin.sh
F: scripts/gcc-plugins/
LEAKING_ADDRESSES
M: Tobin C. Harding <me@tobin.cc>
M: Tycho Andersen <tycho@tycho.ws>
L: kernel-hardening@lists.openwall.com
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tobin/leaks.git
F: scripts/leaking_addresses.pl
Alternatively, would this be acceptable? -
L: kernel-hardening@lists.openwall.com (only for messages focused on core functionality, not for maintenance detail)
I think the latter would be best, if allowed.
Kees, please comment (so that we'd hopefully not need that next time),
and if you agree please make a change to MAINTAINERS.
Mrinal, we appreciate your contribution, and the problem above isn't
yours - it's with the way MAINTAINERS doesn't fit this group well.
Thanks,
Alexander
next prev parent reply other threads:[~2020-08-27 13:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:24 [PATCH] scripts: Add intended executable mode and SPDX license Mrinal Pandey
2020-08-27 9:24 ` [Linux-kernel-mentees] " Mrinal Pandey
2020-08-27 9:34 ` Lukas Bulwahn
2020-08-27 9:34 ` [Linux-kernel-mentees] " Lukas Bulwahn
2020-08-27 9:43 ` Greg KH
2020-08-27 9:43 ` [Linux-kernel-mentees] " Greg KH
2020-08-27 9:49 ` Lukas Bulwahn
2020-08-27 9:49 ` [Linux-kernel-mentees] " Lukas Bulwahn
2020-08-27 10:00 ` Greg KH
2020-08-27 10:00 ` [Linux-kernel-mentees] " Greg KH
2020-08-27 13:06 ` Solar Designer [this message]
2020-08-27 18:02 ` Kees Cook
2020-09-01 0:15 ` Tycho Andersen
2020-09-01 4:24 ` Tobin C. Harding
2020-09-02 12:16 ` Solar Designer
2020-08-27 18:14 ` [Linux-kernel-mentees] " Kees Cook
2020-08-27 18:14 ` Kees Cook
2020-08-31 0:44 ` Andrew Morton
2020-08-31 0:44 ` [Linux-kernel-mentees] " Andrew Morton
2020-08-31 5:45 ` Lukas Bulwahn
2020-08-31 5:45 ` [Linux-kernel-mentees] " Lukas Bulwahn
2020-08-31 19:20 ` Kees Cook
2020-08-31 19:20 ` [Linux-kernel-mentees] " Kees Cook
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=20200827130653.GA25408@openwall.com \
--to=solar@openwall.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=mrinalmni@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.