From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Features backports
Date: Mon, 28 Nov 2016 15:17:34 +0100 [thread overview]
Message-ID: <583C3C7E.5000904@codethink.co.uk> (raw)
In-Reply-To: <2a7cf15f-4b7b-b23d-5385-e72e16fe465a@siemens.com>
Hi,
On 28/11/16 14:47, Jan Kiszka wrote:
> On 2016-11-18 13:26, Agustin Benito Bethencourt wrote:
>> Hi,
>>
>> as you probably know, the more features we backport, the higher will be
>> the maintenance cost overtime so as a strategy, we need to be very
>> conservative.
>>
>> I sent a mail some days ago about the features backported already by
>> Linaro for their LSK (Linaro Stable Kernel) for your evaluation. I bring
>> today some potential backports related with security features and
>> hardware support that has been identified by Ben H.
>>
>> * UBSAN support:
>> <https://git.kernel.org/linus/c6d308534aef6c99904bf5862066360ae067abc4>
>>
>> * Increased user-space ASLR range for ARM:
>> <https://lwn.net/Articles/667790/>
>>
>> * Page poisoning on free:
>> <https://git.kernel.org/linus/8823b1dbc05fab1a8bec275eeae4709257c2661d>,
>> <https://git.kernel.org/linus/1414c7f4f7d72d138fff35f00151d15749b5beda>
>>
>> * SLAB/SLUB freelist randomisation
>>
>> * Hardened usercopy
>>
>> * Do Members use SLUB? if not, we should take a look at KASAN support
>> for SLAB
>>
>> * drm/tilcdc update? (many bug fixes post-4.4)
>>
>> * AM33xx RTC support:
>>
>> <https://git.kernel.org/linus/461932dfb54ebaf7da438fd8b769a01ce97a9360>,
>> <https://git.kernel.org/linus/b5a553c08bec14a058501df3fa6eb39f63f00a98>
>>
>
> To add two features areas from our requirement list:
>
> - Distributed Switch Architecture, basically the level of 4.8 would be
> sufficient. However, there might be too many dependencies on
> networking core changes. If we pick 4.9 as next SLTS, then this
> becomes obsolete.
>
> - Graphic support for AM57xx from more recent kernels, but things may
> even still depend on TI's vendor kernel (in which case it would be
> too early).
>
> Both are a bit vague yet, but I'm trying to clarify more details.
> Comments are already welcome, of course.
This is good. It allows us to dig a little and provide some light.
>
> Jan
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2016-11-28 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 12:26 [cip-dev] Features backports Agustin Benito Bethencourt
2016-11-28 13:47 ` Jan Kiszka
2016-11-28 14:17 ` Agustin Benito Bethencourt [this message]
2016-11-29 2:57 ` 小口琢夫 / KOGUCHI，TAKUO
2016-11-29 9:01 ` Agustin Benito Bethencourt
2016-12-02 8:44 ` KOBAYASHI Yoshitake
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=583C3C7E.5000904@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 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.