[Dev] upgrading systemd, upgrading kernel
casey.schaufler at intel.com
Tue Dec 24 07:53:56 GMT 2013
> -----Original Message-----
> From: Wu, Zhiwen
> Sent: Monday, December 23, 2013 6:45 PM
> To: Schaufler, Casey; artem.bityutskiy at linux.intel.com; ?ukasz Stelmach
> Cc: dev at lists.tizen.org
> Subject: RE: [Dev] upgrading systemd, upgrading kernel
> >-----Original Message-----
> >From: dev-bounces at lists.tizen.org [mailto:dev-bounces at lists.tizen.org]
> >On Behalf Of Schaufler, Casey
> >Sent: Saturday, December 21, 2013 7:07 AM
> >To: artem.bityutskiy at linux.intel.com; Łukasz Stelmach
> >Cc: dev at lists.tizen.org
> >Subject: Re: [Dev] upgrading systemd, upgrading kernel
> >> -----Original Message-----
> >> From: dev-bounces at lists.tizen.org
> >> [mailto:dev-bounces at lists.tizen.org]
> >> On Behalf Of Artem Bityutskiy
> >> Sent: Friday, December 20, 2013 4:06 AM
> >> To: Łukasz Stelmach
> >> Cc: dev at lists.tizen.org
> >> Subject: Re: [Dev] upgrading systemd, upgrading kernel
> >> On Fri, 2013-12-20 at 11:33 +0100, Łukasz Stelmach wrote:
> >> > I'd like to ask everyone here (and please pass this request to
> >> > those who are not yet subscribed) to take more care when you
> >> > upgrade
> >> something.
> >> > Especially if the upgraded software depends on components (kernel
> >> > in this case) that may differ between profiles.
> >> I am not sure it is correct to say in this case that systemd depends
> >> on new kernel.
> >> It is the Tizen security infrastructure which requires several
> >> components to be patched, including systemd and the kernel.
> >Before we go too far down the "blame security" path it should be noted
> >that the kernel changes made to the ivi kernel were, with one
> >exception, done for Mobile and are supposed to be present in the Tizen
> >2.2 kernel. The only one that was not done for Mobile relates to
> >cgroups, and it does not appear from what I've seen that the problems it
> solves had been encountered yet.
> [ Wu, Zhiwen] Do you mean that the "Failed to create root cgroup hierarchy:
> Permission denied Failed " problem had not been encountered yet on the
> environment including Tizen 2.2 mobile kernel and v208 systemd ?
Too many "and"s in the preceding statement.
We know that the Smack cgroup kernel change is necessary for the v208 systemd.
We don't know that it is necessary for Tizen 2.2.
If you put the v208 systemd into Tizen2.2 you are likely to encounter a number of problems unrelated to Smack.
More information about the Dev