All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built
Date: Wed, 23 Aug 2017 14:31:56 -0400	[thread overview]
Message-ID: <20170823183156.GB26405@denix.org> (raw)
In-Reply-To: <ab92e7d90c416d6e5cdb17cdba269e09ec967607.1503283308.git.bruce.ashfield@windriver.com>

On Sun, Aug 20, 2017 at 10:58:21PM -0400, Bruce Ashfield wrote:
> There was a bug in the search routines responsible for locating
> BSP definitions which returned a valid match if only the ktype
> matched.
> 
> This meant that someone looking for "qemux86foo" (which is an
> invalid definition) would potentially end up building "qemuarm"
> and be none the wiser (until it didn't boot).
> 
> With this fix to the tools search routine, and improved return
> code testing, we will now stop the build and report and error to
> the user.
> 
> [YOCTO: #11878]
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  meta/classes/kernel-yocto.bbclass                       | 3 +++
>  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
> index 1ca0756c4959..3c6df92131bc 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -143,6 +143,9 @@ do_kernel_metadata() {
>  
>  	# expand kernel features into their full path equivalents
>  	bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE} -DKTYPE=${LINUX_KERNEL_TYPE})
> +	if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then
> +		bbfatal_log "Could not locate BSP definiton for ${KMACHINE}/${LINUX_KERNEL_TYPE}."
> +	fi
>  	meta_dir=$(kgit --meta)
>  
>  	# run1: pull all the configuration fragments, no matter where they come from
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index 2217a31076a2..4a78b897d34f 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
>  
>  DEPENDS = "git-native"
>  
> -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
> +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"

My builds last night of poky+meta-ti all failed with:

DEBUG: Running ... git -c core.fsyncobjectfiles=0 clone -s -n /OE/poky-master/downloads/git2/git.yoctoproject.org.yocto-kernel-tools.git/ /OE/poky-master/build/tmp/work/x86_64-linux/kern-tools-native/0.2+gitAUTOINC+0571411cc0-r12/git/
DEBUG: Running ... git -c core.fsyncobjectfiles=0 remote set-url origin git://git.yoctoproject.org/yocto-kernel-tools.git
DEBUG: Running ... git -c core.fsyncobjectfiles=0 checkout -B master 0571411cc033c11df7827508dd786876ce2f8c83
ERROR: Fetcher failure: Fetch command ... git -c core.fsyncobjectfiles=0 checkout -B master 0571411cc033c11df7827508dd786876ce2f8c83 failed with exit code 128, output:
fatal: reference is not a tree: 0571411cc033c11df7827508dd786876ce2f8c83                                                                                                   


>  PR = "r12"
>  PV = "0.2+git${SRCPV}"
>  
> -- 
> 2.5.0
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  parent reply	other threads:[~2017-08-23 18:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  2:58 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2017-08-21  2:58 ` [PATCH 1/9] kernel-yocto: configuration updates: x86 features Bruce Ashfield
2017-08-21  2:58 ` [PATCH 2/9] linux-yocto/4.1: fix fsl-ls10xx sdhci Bruce Ashfield
2017-08-21  2:58 ` [PATCH 3/9] linux-yocto: add usb-net configs by default Bruce Ashfield
2017-08-21  2:58 ` [PATCH 4/9] linux-yocto: introduce 4.12 recipes Bruce Ashfield
2017-08-21  2:58 ` [PATCH 5/9] linux-yocto: remove 4.1 recipes Bruce Ashfield
2017-08-21  2:58 ` [PATCH 6/9] libc-headers: update to 4.12 Bruce Ashfield
2017-08-21  2:58 ` [PATCH 7/9] qemu: bump default version " Bruce Ashfield
2017-08-21  2:58 ` [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built Bruce Ashfield
2017-08-21 15:00   ` Peter Kjellerstedt
2017-08-21 15:03     ` Bruce Ashfield
2017-08-21 15:13       ` Bruce Ashfield
2017-08-21 15:16         ` Peter Kjellerstedt
2017-08-21 15:18           ` Bruce Ashfield
2017-08-23  3:40   ` Khem Raj
2017-08-23 12:37     ` Bruce Ashfield
2017-08-23 14:40       ` Khem Raj
2017-08-23 14:42         ` Bruce Ashfield
2017-08-23 14:58           ` Richard Purdie
2017-08-23 15:00             ` Bruce Ashfield
2017-08-23 15:07             ` Khem Raj
2017-08-23 18:31   ` Denys Dmytriyenko [this message]
2017-08-23 18:56     ` Bruce Ashfield
2017-08-21  2:58 ` [PATCH 9/9] linux-yocto/4.10: CVE & misc fixes Bruce Ashfield
2017-08-21  3:05 ` ✗ patchtest: failure for kernel-yocto: consolidated pull request Patchwork
2017-08-21 11:42 ` [PATCH 0/9] " Richard Purdie
2017-08-21 12:11   ` Bruce Ashfield
2017-08-21 13:01     ` Bruce Ashfield
2017-08-21 15:55 ` Richard Purdie
2017-08-21 15:57   ` Bruce Ashfield
2017-08-21 16:12   ` Bruce Ashfield
2017-08-22 14:24     ` Richard Purdie
2017-08-22 14:54       ` Bruce Ashfield
2017-08-22 15:28         ` Richard Purdie
2017-08-22 15:34           ` Bruce Ashfield
2017-08-22 16:00             ` Richard Purdie
2017-08-22 16:04               ` Bruce Ashfield
2017-08-22 16:07                 ` Richard Purdie
2017-08-22 16:20                   ` Bruce Ashfield
2017-08-22 17:13                   ` Bruce Ashfield
2017-08-22 20:34                   ` Bruce Ashfield
2017-08-22 21:56                     ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170823183156.GB26405@denix.org \
    --to=denis@denix.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.