From: Kees Cook <keescook@chromium.org>
To: linux-hardening@vger.kernel.org
Subject: bug scrub
Date: Thu, 16 Sep 2021 08:36:36 -0700 [thread overview]
Message-ID: <202109160827.7F5C1AFC7E@keescook> (raw)
Hi!
I went through the issue tracker and tried to get issues updated, add
some new labels, etc.
Stuff of note:
- "Global flag" label[1], for compiler options to turn on globally in the
top-level Makefile.
https://github.com/KSPP/linux/labels/%5BBuild%5D%20Global%20flag
- Scrubbed per-arch issues, but mostly seemed to update the status of
powerpc.
https://github.com/KSPP/linux/labels/%5BARCH%5D%20powerpc64
- Collected all sub-bugs of the top-level "get rid of fake flex arrays"
issue, so there's a single place to look at status.
https://github.com/KSPP/linux/issues/21
As always, the "good first issue" list of bugs is a nice place for folks
to look through if they want to help out.
https://github.com/KSPP/linux/labels/good%20first%20issue
And if anyone wants to continue the strlcpy removal work, I think it
just needs some rebasing and shepherding of patches through to subsystem
maintainers.
https://github.com/KSPP/linux/issues/89
-Kees
--
Kees Cook
reply other threads:[~2021-09-16 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202109160827.7F5C1AFC7E@keescook \
--to=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox