From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening]
Date: Mon, 16 Nov 2015 00:45:09 -0500 [thread overview]
Message-ID: <56496D65.8030903@gmail.com> (raw)
In-Reply-To: <56496AB0.5070905@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
> I really can't see Linus and others being okay with any GCC
> plugins with alterations to the semantics of C rather than just codegen
> like the KERNEXEC plugin.
Oh and REFCOUNT is basically the same situation. I can't see any
possibility of that landing without switching to having a refcount_t
type and having separate functions for working with it, with a
configuration option like DEBUG_REFCOUNT to flip on overflow checks.
It's a whole bunch of busy-work and since it will touch so much code it
will run into the same problems that the previous attempts to upstream
constification did.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-16 5:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 15:43 [kernel-hardening] west suhanic
2015-11-13 22:23 ` [kernel-hardening] Valdis.Kletnieks
2015-11-13 23:21 ` [kernel-hardening] David Windsor
2015-11-15 20:59 ` [kernel-hardening] Richard Weinberger
2015-11-16 5:33 ` [kernel-hardening] Daniel Micay
2015-11-16 5:45 ` Daniel Micay [this message]
2015-11-16 6:38 ` [kernel-hardening] David Windsor
2015-11-16 22:03 ` [kernel-hardening] Daniel Micay
2015-11-16 23:20 ` [kernel-hardening] Kees Cook
2015-11-16 23:17 ` [kernel-hardening] Kees Cook
2015-11-16 12:13 ` [kernel-hardening] Richard Weinberger
2015-11-17 7:41 ` [kernel-hardening] Daniel Micay
2015-11-17 10:32 ` [kernel-hardening] Richard Weinberger
2015-11-16 23:14 ` [kernel-hardening] Kees Cook
2015-11-17 8:09 ` [kernel-hardening] Daniel Micay
2015-11-17 17:30 ` [kernel-hardening] 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=56496D65.8030903@gmail.com \
--to=danielmicay@gmail.com \
--cc=kernel-hardening@lists.openwall.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.