All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built
Date: Mon, 21 Aug 2017 11:13:59 -0400	[thread overview]
Message-ID: <CADkTA4PdZwrfh_u44auWAR4r0KV2oVp1VJu=56Uvpv6xocEp1g@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4Nx3EAgggD2ohyZJpX2ZGUgKvmQK-KFLTnreJSjO830Zw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4506 bytes --]

On Mon, Aug 21, 2017 at 11:03 AM, Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Mon, Aug 21, 2017 at 11:00 AM, Peter Kjellerstedt <
> peter.kjellerstedt@axis.com> wrote:
>
>> > -----Original Message-----
>> > From: openembedded-core-bounces@lists.openembedded.org
>> > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> > Bruce Ashfield
>> > Sent: den 21 augusti 2017 04:58
>> > To: richard.purdie@linuxfoundation.org
>> > Cc: openembedded-core@lists.openembedded.org
>> > Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
>> > BSPs are built
>> >
>> > 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
>>
>> Use $bsp_definition instead of ${bsp_definition} since it is a
>> shell variable and not a bitbake variable.
>>
>
> I always use ${...}, so I'm going to stay consistent with what is already
> in
> the file.
>
>
>>
>> Actually, after looking at the code in that bbclass, I see this
>> used for a number of shell variables all over the place. This is
>> actually bad, and you should rewrite the code to not use ${variable}
>> for shell variables. The reason this is bad is because these
>> variables unnecessarily end up in the sstate hash for these functions,
>> and if someone actually happens to define a bitbake variable with the
>> same name as one of those shell variables, the result will not be what
>> is expected...
>>
>
> Not something high on my priority list. It's been that way since the
> beginning.
>

.. but I will loop back and take care of the issues before M4 closes. Just
a bit busy
pushing out the new kernels and a slew of bug fixes.

This patch can be ignored (if needed) until I get back around to that.

Cheers,

Bruce


>
> Cheers,
>
> Bruce
>
>
>>
>> > +             bbfatal_log "Could not locate BSP definiton for
>> ${KMACHINE}/${LINUX_KERNEL_TYPE}."
>>
>> Change "definiton" to "definition".
>>
>> > +     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;beginli
>> ne=5;endline=9;md5=a6c2fa8aef1b
>> >
>> >  DEPENDS = "git-native"
>> >
>> > -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
>> > +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
>> >  PR = "r12"
>> >  PV = "0.2+git${SRCPV}"
>> >
>> > --
>> > 2.5.0
>>
>> //Peter
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 8077 bytes --]

  reply	other threads:[~2017-08-21 15:13 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 [this message]
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
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='CADkTA4PdZwrfh_u44auWAR4r0KV2oVp1VJu=56Uvpv6xocEp1g@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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.