Re: linux-module-builder leads to huge store items

[Ludovic Courtès]

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>> So, I can think of the following ways to address that:
>> 
>>   1. Remove for example *.c, assuming the out-of-tree modules we package
>>      only care about *.h + build machinery.
>
> The biggest source files, see above, are header files
> (drivers/gpu/drm/amd/include/asic_reg).
>
>>   2. Don’t add all of the Linux source to the store, or at least not
>>      under a new name each time.  One way to do that would be to unpack
>>      the Linux-libre tree within the build tree of the out-of-tree
>>      module.  We’d be reducing GC stress at the expense of a
>>      (reasonable?) increase in module build time.

[...]

> I checked--that would reduce the size of linux-libre-builder by about 800 MB
> (to 255 MB; see [1][2]).
> That would mean that some modules can't be out-of-tree.  But I guess
> that's okay--and we could not-delete some files later if need be.

Yes, that’s OK.  I’d say let’s delete as much as possible, and then, if
it eventually turns out to be a problem for a new out-of-tree module
package, we can re-add files selectively.

Could you give it a try?

> Btw, linux-libre is currently not reproducible--see bug 43301.
> That could introduce a security problem if the Linux kernel and
> an out-of-tree module are compiled differently (they are) and then loaded
> into the same kernel (even now).

One thing at a time.  :-)

Thanks,
Ludo’.