Re: RFC: Locked down sstate cache usage

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2013-12-02 at 17:28 -0600, Mark Hatle wrote:
> On 12/2/13, 4:57 PM, Richard Purdie wrote:
> > I've been giving things some thought, specifically why sstate doesn't
> > get used more and why we have people requesting external toolchains. I'm
> > guessing the issue is that people don't like how often sstate can change
> > and the lack of an easy way to lock it down.
> 
> While I haven't fully looked into this.  I've got two cases where people want to 
> lock down the sstate.
> 
> The first is they simply want to lock it down, either what they're building is 
> in the sstate-cache --or-- it's an error.  (Then they could whitelist specific 
> items that they want built from source -- expecting these would be their custom 
> recipes.)

That would be easy enough to do from the sstate hash validation code
path since you can tell if it was found in the cache or not.

> The second is a case similar to what you have below, they want specific packages 
> to come from specific hashes.  My concern though is if the user changes 
> something to do with the signature(s), i.e. picks a different distribution flag 
> or something, which would normally cause a toolchain component to invalidate and 
> be rebuilt.  (In this case, I'd like a way to identify that they changed 
> something in an incompatible way.)  Not exactly sure how I would do that in this 
> case.

Well, you can call the main hash function and see what it returns,
compare it to the locked value and error if its different.

> > Locking it down is actually quite easy so I thought I'd share a quick
> > proof of concept of how you can do this (for example to a specific
> > toolchain). With an addition like this to local.conf (or wherever):
> >
> > SIGGEN_LOCKEDSIGS = "\
> > gcc-cross:do_populate_sysroot:a8d91b35b98e1494957a2ddaf4598956 \
> > eglibc:do_populate_sysroot:13e8c68553dc61f9d67564f13b9b2d67 \
> > eglibc:do_packagedata:bfca0db1782c719d373f8636282596ee \
> > gcc-cross:do_packagedata:4b601ff4f67601395ee49c46701122f6 \
> > "
> >
> > the code at the end of the email will force the hashes to those values
> > for the recipes mentioned. The system would then find and use those
> > specific objects from the sstate cache instead of trying to build
> > anything.
> >
> > Obviously this is a little simplistic, you might need to put an override
> > against this to only apply those revisions for a specific architecture
> > for example. You'd also probably want to put code in the sstate hash
> > validation code to ensure it really did install these from sstate since
> > if it didn't you'd want to abort the build.
> >
> > Anyhow, I thought I'd put this out there and see if there is interest in
> > better supporting this kind of usage of sstate?
> 
> If there was a simply way we could run a validation of specific options, and 
> then set the value to one of many? potential options that would work I think.

This is harder since its difficult to know which options to make fuzzy
and how they should be fuzzy. You'd probably be better off excluding the
specific options from the sstate cache signatures in the first place for
this to work.

Cheers,

Richard