From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4-cip 0/6] Extend user-space ASLR range
Date: Mon, 2 Jan 2017 18:48:22 +0000 [thread overview]
Message-ID: <586AA076.2030108@codethink.co.uk> (raw)
In-Reply-To: <1482511605.1860.200.camel@codethink.co.uk>
Hi,
On 23/12/16 16:46, Ben Hutchings wrote:
> [Sorry for the delay; I haven't been feeling well.]
>
> On Fri, 2016-12-09 at 13:20 +0100, Jan Kiszka wrote:
>> Did you try to discuss the back-port topic with the KSPP folks or other
>> key persons involved in these patches? In the ideal case, the authors
>> can be CC'ed, do not get annoyed by "these crazy people doing legacy
>> stuff", and may even do some reviews.
>
> I would normally cc the upstream developers, but I was hesitant to do so
> for CIP because this is not related to an official stable branch.
> Perhaps I should ask on the KSPP list whether a cc for such feature
> backports would be appreciated?
Please do so.
>
> On Mon, 2016-12-19 at 11:52 +0100, Jan Kiszka wrote:
>> I've chatted with Elena over this last week, and she talked to Kees
>> who
>> pointed out that the Android people are also doing KSPP backports to
>> 4.4
>> (thanks, folks!). I didn't check any details, just a heads-up to avoid
>> duplicate work.
>
> Thanks for letting me know.
>
> Ben.
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-01-02 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 23:56 [cip-dev] [PATCH 4.4-cip 0/6] Extend user-space ASLR range Ben Hutchings
2016-12-08 23:57 ` [cip-dev] [PATCH 4.4-cip 1/6] mm: mmap: add new /proc tunable for mmap_base ASLR Ben Hutchings
2016-12-08 23:57 ` [cip-dev] [PATCH 4.4-cip 2/6] arm: mm: support ARCH_MMAP_RND_BITS Ben Hutchings
2016-12-08 23:57 ` [cip-dev] [PATCH 4.4-cip 3/6] arm64: " Ben Hutchings
2016-12-08 23:58 ` [cip-dev] [PATCH 4.4-cip 4/6] x86: " Ben Hutchings
2016-12-08 23:58 ` [cip-dev] [PATCH 4.4-cip 5/6] drivers: char: random: add get_random_long() Ben Hutchings
2016-12-08 23:58 ` [cip-dev] [PATCH 4.4-cip 6/6] mm: ASLR: use get_random_long() Ben Hutchings
2016-12-09 12:20 ` [cip-dev] [PATCH 4.4-cip 0/6] Extend user-space ASLR range Jan Kiszka
2016-12-19 10:52 ` Jan Kiszka
2017-01-03 23:56 ` Kees Cook
2017-01-04 14:51 ` Agustin Benito Bethencourt
2017-01-12 13:40 ` Ben Hutchings
2016-12-23 16:46 ` Ben Hutchings
2017-01-02 18:48 ` Agustin Benito Bethencourt [this message]
2017-01-16 10:35 ` Agustin Benito Bethencourt
2017-01-16 10:47 ` Agustin Benito Bethencourt
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=586AA076.2030108@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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