[Buildroot] [PATCH] linux: don't check hashes for user-supplied patches

Simon van der Veldt simon.vanderveldt at gmail.com
Sat Feb 16 23:14:57 UTC 2019


On Sat, Feb 16, 2019 at 7:34 PM Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
>
> We have virtually no way to know the hashes for user-supplied patches,
> so we should just ignore them.
>
> Reported-by: Simon van der Veldt <simon.vanderveldt at gmail.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
Tested-by: Simon van der Veldt <simon.vanderveldt at gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
> Cc: Arnout Vandecappelle <arnout at mind.be>
> Cc: Peter Korsgaard <peter at korsgaard.com>
>
> ---
> Peter: this is a candidate for backporting to 2018.11.x and 2018.02.x
> ---
>  linux/linux.mk | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 8c21bad067..2b5d096e14 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -55,6 +55,9 @@ endif
>
>  LINUX_PATCHES = $(call qstrip,$(BR2_LINUX_KERNEL_PATCH))
>
> +# We have no way to know the hashes for user-supplied patches.
> +BR_NO_CHECK_HASH_FOR += $(notdir $(LINUX_PATCHES))
> +
>  # We rely on the generic package infrastructure to download and apply
>  # remote patches (downloaded from ftp, http or https). For local
>  # patches, we can't rely on that infrastructure, because there might
> --
> 2.14.1
>

Did a test build with this patch applied and the kernel patches are
now correctly applied without failing the hash check :)
Thanks for the quick fix!

Simon


More information about the buildroot mailing list