From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening]
Date: Tue, 17 Nov 2015 03:09:45 -0500 [thread overview]
Message-ID: <564AE0C9.9040706@gmail.com> (raw)
In-Reply-To: <CAGXu5jJLcJBjyA+2xMA63tCr_xg7xxEoLk=RHKXRXM7L23AD7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
> AOSP isn't enough, and even if people did submit them there, I would
> be one of the AOSP reviewers asking that they be upstreamed instead.
> ;)
Sure, but it's a way to proving to upstream that the features are useful
and work well. For example, lets say x86 Android adopted the
segmentation-based KERNEXEC/UDEREF. Lets say it actually shipped in the
next version of Android. I am pretty sure Linus would change his
attitude towards it. You're not going to convince him by words rather
than actions though. Not that improving Linux on a dying architecture
should be the priority, but it's a good example.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-17 8:09 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 ` [kernel-hardening] Daniel Micay
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 ` Daniel Micay [this message]
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=564AE0C9.9040706@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.