[meta-freescale] security patches in the Linux kernel

[zhenhua.luo at freescale.com]

Hello Sona, 

Except what Otavio mentioned(send the Yocto patches to meta-freescale maillist). It will be great if those patches can be sent to kernel upstream(http://patchwork.ozlabs.org/project/linuxppc-dev/list/) directly. 


Best Regards,

Zhenhua

> -----Original Message-----
> From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-
> bounces at yoctoproject.org] On Behalf Of Otavio Salvador
> Sent: Wednesday, July 02, 2014 10:17 PM
> To: Sona Sarmadi
> Cc: meta-freescale at yoctoproject.org; meta-freescale at git.freescale.com
> Subject: Re: [meta-freescale] security patches in the Linux kernel
> 
> Hello Sona,
> 
> On Wed, Jul 2, 2014 at 3:34 AM, Sona Sarmadi <sona.sarmadi at enea.com>
> wrote:
> > My name is Sona Sarmadi and I am responsible for security in Enea Linux.
> 
> Nice to meet you.
> 
> > Our goal is to apply security patches to the Linux kernels in our
> distribution, in order to test and make the patches available for our
> customers as soon as possible. When we apply a patch, we always build an
> image (e.g. for P4080) and run ptest to verify the patch.
> 
> Great.
> 
> > So far we have fixed security patches for chip-vendor-supplied kernels
> in our own layer meta-enea, but we would like to change this policy and
> apply the security patches directly in the hardware-specific layer, e.g.
> meta-fsl-ppc, and upstream them to the layer maintainers. In this way,
> others can also get the patch. There are more advantages with fixing the
> patches in the hardware-specific layer and upstreaming them compared to
> fixing them in our own meta-enea layer.
> >
> > We are very interested in your maintenance policy and your opinion
> about receiving patches from Enea.
> 
> I am very happy to see this initiative from Enea and I look forward to
> see more software vendors adopting same strategy.
> 
> I think you can prepare a patch which includes the fixes (security
> related or not) and send them. Those are going to be reviewed and applied
> accordingly. Regarding the maintenance policy we follow same guidelines
> as the Yocto Project but this does not mean we cannot include fixes for
> previous branches, if someone send them.
> 
> Tomorrow we'll have our monthly meeting[1] and it'd be good if you could
> join us.
> 
> 1. https://lists.yoctoproject.org/pipermail/meta-freescale/2014-
> June/008987.html
> 
> Please note that the time has changed and it'll take place at 14:00 GMT.
> 
> Regards,
> 
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale