From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Sona Sarmadi <sona.sarmadi@enea.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: kernel patches
Date: Fri, 22 Aug 2014 08:49:24 -0400 [thread overview]
Message-ID: <53F73C54.60803@windriver.com> (raw)
In-Reply-To: <3230301C09DEF9499B442BBE162C5E48256DB954@SESTOEX04.enea.se>
On 14-08-22 08:17 AM, Sona Sarmadi wrote:
> Hi all,
>
> I wonder how you handle the kernel patches?
>
> I want to apply a security kernel patch to Linux-yocto 3.10 which is used by Romely:
>
> meta-inte/meta-romley/conf/machine/romley-ivb.conf:PREFERRED_VERSION_linux-yocto ?= "3.10%"
>
> For me the obvious way to fix this is:
> 1) Create >> "poky/meta/recipes-kernel/linux/files" directory and add the patch file there
>
> 2) modify: poky/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>
>
> -SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
> +FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta \
> + file://Fix_for_CVE-2014-0196_pty_layer_race_condition.patch \
> + "
>
> Please let me know if this is the correct way. And also let me know if I upstream this kernel patch to yocto, will yocto accept it (if the patch looks correct of course). Please let me know if you prefer to apply security patches to kernels in some different way.
If this is for your own local builds, a layer with a bbappend and the
patches is a better idea.
For the main linux-yocto recipes, everything is maintained in the
git repositories, not patched at build time, so changes go to the
linux-yocto mailing list, and I merge them from there.
On this particular topic, I already track all the -stable updates for
our linux-yocto kernels, and CVEs are picked up by -stable. So there's
a process in place to get security related fixes into the linux-yocto
trees.
I'm a few releases behind at the moment, due to a 2 week vacation,
but 3.4, 3.10 and 3.14 will all be updated shortly.
If you do notice a CVE that isn't part of the k.org -stable updates,
that is or more interest, and we should nominate it for -stable upstream
and have it flow to all kernels via that process.
Bruce
>
> Thanks
> BR - Sona
>
next prev parent reply other threads:[~2014-08-22 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:17 kernel patches Sona Sarmadi
2014-08-22 12:49 ` Bruce Ashfield [this message]
2014-08-22 16:02 ` Sona Sarmadi
2014-08-22 16:27 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 17:26 Chris Babcock
2003-05-12 17:55 ` Russell Coker
2003-05-12 18:48 ` Stephen Smalley
2002-03-08 17:23 Kernel patches Jacky Lam
2002-03-08 17:42 ` Andreas Dilger
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=53F73C54.60803@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=sona.sarmadi@enea.com \
--cc=yocto@yoctoproject.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.