[PATCH 0/9] kernel-yocto: consolidated pull request

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here's the collected set of kernel changes that are ready for the M3 builds.

We have some kernel meta data changes:

  kernel-yocto: configuration updates: x86 features
  linux-yocto/4.1: fix fsl-ls10xx sdhci
  linux-yocto: add usb-net configs by default

Some bug fixes:

  kernel-yocto: ensure that only valid BSPs are built
  linux-yocto/4.10: CVE & misc fixes

And the important changes are the addition of the 4.12 kernel + libc headers
and the removal of the 4.1 kernel.

I also have some -stable updates queued for the active kernel versions, but
they will come out once this series has made it into the tree, since I'm
trying to isolate any 4.12 issues from other -stable updates.

I built and booted all the qemu targets for 4.12, and have built for
core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
architectures. My testing didn't pick up any regressions, but I was battling
some other build errors (non kernel related) during my testing, so I can
never be 100% sure.

I've sent patches to poky to remove/bump any references to the 4.1 kernel
.. if I've missed any, I'm sure people will shout.

Cheers,

Bruce


The following changes since commit 04dc76713b57f28457742dd863caa663591d4866:

  devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation. (2017-08-19 22:15:39 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-yocto: configuration updates: x86 features
  linux-yocto/4.1: fix fsl-ls10xx sdhci
  linux-yocto: add usb-net configs by default
  linux-yocto: introduce 4.12 recipes
  linux-yocto: remove 4.1 recipes
  libc-headers: update to 4.12
  qemu: bump default version to 4.12
  kernel-yocto: ensure that only valid BSPs are built
  linux-yocto/4.10: CVE & misc fixes

 meta/classes/kernel-yocto.bbclass                  |  3 +++
 meta/conf/distro/include/tcmode-default.inc        |  2 +-
 meta/conf/machine/include/x86-base.inc             |  2 +-
 meta/conf/machine/qemuarm.conf                     |  2 +-
 .../kern-tools/kern-tools-native_git.bb            |  2 +-
 ...-headers_4.10.bb => linux-libc-headers_4.12.bb} |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   |  4 ++--
 ...inux-yocto-rt_4.1.bb => linux-yocto-rt_4.12.bb} | 12 +++++-----
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb    |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb    |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb |  4 ++--
 ...-yocto-tiny_4.1.bb => linux-yocto-tiny_4.12.bb} | 12 +++++-----
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.10.bb      | 18 +++++++--------
 .../{linux-yocto_4.1.bb => linux-yocto_4.12.bb}    | 26 ++++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb       |  2 +-
 18 files changed, 56 insertions(+), 47 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.10.bb => linux-libc-headers_4.12.bb} (71%)
 rename meta/recipes-kernel/linux/{linux-yocto-rt_4.1.bb => linux-yocto-rt_4.12.bb} (76%)
 rename meta/recipes-kernel/linux/{linux-yocto-tiny_4.1.bb => linux-yocto-tiny_4.12.bb} (52%)
 rename meta/recipes-kernel/linux/{linux-yocto_4.1.bb => linux-yocto_4.12.bb} (56%)

-- 
2.5.0

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Hi all,
> 
> Here's the collected set of kernel changes that are ready for the M3
> builds.
> 
> We have some kernel meta data changes:
> 
>   kernel-yocto: configuration updates: x86 features
>   linux-yocto/4.1: fix fsl-ls10xx sdhci
>   linux-yocto: add usb-net configs by default
> 
> Some bug fixes:
> 
>   kernel-yocto: ensure that only valid BSPs are built
>   linux-yocto/4.10: CVE & misc fixes
> 
> And the important changes are the addition of the 4.12 kernel + libc
> headers
> and the removal of the 4.1 kernel.
> 
> I also have some -stable updates queued for the active kernel
> versions, but
> they will come out once this series has made it into the tree, since
> I'm
> trying to isolate any 4.12 issues from other -stable updates.
> 
> I built and booted all the qemu targets for 4.12, and have built for
> core-image-sato, core-image-kernel-dev, glibc and muslc for all of
> the
> architectures. My testing didn't pick up any regressions, but I was
> battling
> some other build errors (non kernel related) during my testing, so I
> can
> never be 100% sure.
> 
> I've sent patches to poky to remove/bump any references to the 4.1
> kernel
> .. if I've missed any, I'm sure people will shout.

I added an extra patch for the ones you missed in meta-yocto-bsp ;-)

Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
steps/BuildImages_1/logs/stdio

Error: 
 Problem: conflicting requests
  - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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

On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > Hi all,
> >
> > Here's the collected set of kernel changes that are ready for the M3
> > builds.
> >
> > We have some kernel meta data changes:
> >
> >   kernel-yocto: configuration updates: x86 features
> >   linux-yocto/4.1: fix fsl-ls10xx sdhci
> >   linux-yocto: add usb-net configs by default
> >
> > Some bug fixes:
> >
> >   kernel-yocto: ensure that only valid BSPs are built
> >   linux-yocto/4.10: CVE & misc fixes
> >
> > And the important changes are the addition of the 4.12 kernel + libc
> > headers
> > and the removal of the 4.1 kernel.
> >
> > I also have some -stable updates queued for the active kernel
> > versions, but
> > they will come out once this series has made it into the tree, since
> > I'm
> > trying to isolate any 4.12 issues from other -stable updates.
> >
> > I built and booted all the qemu targets for 4.12, and have built for
> > core-image-sato, core-image-kernel-dev, glibc and muslc for all of
> > the
> > architectures. My testing didn't pick up any regressions, but I was
> > battling
> > some other build errors (non kernel related) during my testing, so I
> > can
> > never be 100% sure.
> >
> > I've sent patches to poky to remove/bump any references to the 4.1
> > kernel
> > .. if I've missed any, I'm sure people will shout.
>
> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>
> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
> steps/BuildImages_1/logs/stdio
>
> Error:
>  Problem: conflicting requests
>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>

Hmm. I've built that exact combination on two different builders in the
past week
and have never seen this.

How do I find out about the environment on that machine ? Because I'm not
going
to be able to reproduce it here.

Bruce


>
> Cheers,
>
> Richard
>
>
> --
> _______________________________________________
> 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"

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

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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

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

>
>
> On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> > Hi all,
>> >
>> > Here's the collected set of kernel changes that are ready for the M3
>> > builds.
>> >
>> > We have some kernel meta data changes:
>> >
>> >   kernel-yocto: configuration updates: x86 features
>> >   linux-yocto/4.1: fix fsl-ls10xx sdhci
>> >   linux-yocto: add usb-net configs by default
>> >
>> > Some bug fixes:
>> >
>> >   kernel-yocto: ensure that only valid BSPs are built
>> >   linux-yocto/4.10: CVE & misc fixes
>> >
>> > And the important changes are the addition of the 4.12 kernel + libc
>> > headers
>> > and the removal of the 4.1 kernel.
>> >
>> > I also have some -stable updates queued for the active kernel
>> > versions, but
>> > they will come out once this series has made it into the tree, since
>> > I'm
>> > trying to isolate any 4.12 issues from other -stable updates.
>> >
>> > I built and booted all the qemu targets for 4.12, and have built for
>> > core-image-sato, core-image-kernel-dev, glibc and muslc for all of
>> > the
>> > architectures. My testing didn't pick up any regressions, but I was
>> > battling
>> > some other build errors (non kernel related) during my testing, so I
>> > can
>> > never be 100% sure.
>> >
>> > I've sent patches to poky to remove/bump any references to the 4.1
>> > kernel
>> > .. if I've missed any, I'm sure people will shout.
>>
>> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>>
>> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
>> steps/BuildImages_1/logs/stdio
>> <https://autobuilder.yocto.io/builders/build-appliance/builds/425/steps/BuildImages_1/logs/stdio>
>>
>> Error:
>>  Problem: conflicting requests
>>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>>
>
> Hmm. I've built that exact combination on two different builders in the
> past week
> and have never seen this.
>
> How do I find out about the environment on that machine ? Because I'm not
> going
> to be able to reproduce it here.
>

A little bit more information. Saul fixed this earlier this year, and I'm
still carrying
a patch that ensures that /usr/bin/awk is in the ver_linux script instead
of /bin/awk.
That fix used to satisfy a similar requirement.

That being said, I did notice that Saul's change was accepted upstream and
the
patch I'm carrying is not correctly applied (but it should be an invalid
patch, not
a reference to /bin/awk).

I've fixed that patch, and am building the build-appliance image now.

I will have a new set of SRCREVs for linux-yocto-4.12, but I can't say if
they'll
fix the particular issue that the autobuilder is seeing.

Bruce


>
> Bruce
>
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>> --
>> _______________________________________________
>> 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: 5750 bytes --]

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Here's the collected set of kernel changes that are ready for the M3
> builds.
> 
> We have some kernel meta data changes:
> 
>   kernel-yocto: configuration updates: x86 features
>   linux-yocto/4.1: fix fsl-ls10xx sdhci
>   linux-yocto: add usb-net configs by default
> 
> Some bug fixes:
> 
>   kernel-yocto: ensure that only valid BSPs are built
>   linux-yocto/4.10: CVE & misc fixes
> 
> And the important changes are the addition of the 4.12 kernel + libc headers
> and the removal of the 4.1 kernel.
> 
> I also have some -stable updates queued for the active kernel versions, but
> they will come out once this series has made it into the tree, since I'm
> trying to isolate any 4.12 issues from other -stable updates.
> 
> I built and booted all the qemu targets for 4.12, and have built for
> core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
> architectures. My testing didn't pick up any regressions, but I was battling
> some other build errors (non kernel related) during my testing, so I can
> never be 100% sure.
> 
> I've sent patches to poky to remove/bump any references to the 4.1 kernel
> .. if I've missed any, I'm sure people will shout.

Thanks for the other fix, not got that tested yet as builds are still
ongoing. However there appears to be a perf issue:

https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
[and so on]

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 2017-08-21 11:55 AM, Richard Purdie wrote:
> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> Here's the collected set of kernel changes that are ready for the M3
>> builds.
>>
>> We have some kernel meta data changes:
>>
>>    kernel-yocto: configuration updates: x86 features
>>    linux-yocto/4.1: fix fsl-ls10xx sdhci
>>    linux-yocto: add usb-net configs by default
>>
>> Some bug fixes:
>>
>>    kernel-yocto: ensure that only valid BSPs are built
>>    linux-yocto/4.10: CVE & misc fixes
>>
>> And the important changes are the addition of the 4.12 kernel + libc headers
>> and the removal of the 4.1 kernel.
>>
>> I also have some -stable updates queued for the active kernel versions, but
>> they will come out once this series has made it into the tree, since I'm
>> trying to isolate any 4.12 issues from other -stable updates.
>>
>> I built and booted all the qemu targets for 4.12, and have built for
>> core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
>> architectures. My testing didn't pick up any regressions, but I was battling
>> some other build errors (non kernel related) during my testing, so I can
>> never be 100% sure.
>>
>> I've sent patches to poky to remove/bump any references to the 4.1 kernel
>> .. if I've missed any, I'm sure people will shout.
> 
> Thanks for the other fix, not got that tested yet as builds are still
> ongoing. However there appears to be a perf issue:
> 
> https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
> [and so on]
> 

Again, I'm not going to be much good on fixing this.

I of course have built (and run perf on target) for all the
architectures or I never would have sent the pull request.

I'll see if I can find something wrong on what my building
was producing, but otherwise, I have no way to reproduce it.

Bruce


> Cheers,
> 
> Richard
> 
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 2017-08-21 11:55 AM, Richard Purdie wrote:
> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> Here's the collected set of kernel changes that are ready for the M3
>> builds.
>>
>> We have some kernel meta data changes:
>>
>>    kernel-yocto: configuration updates: x86 features
>>    linux-yocto/4.1: fix fsl-ls10xx sdhci
>>    linux-yocto: add usb-net configs by default
>>
>> Some bug fixes:
>>
>>    kernel-yocto: ensure that only valid BSPs are built
>>    linux-yocto/4.10: CVE & misc fixes
>>
>> And the important changes are the addition of the 4.12 kernel + libc headers
>> and the removal of the 4.1 kernel.
>>
>> I also have some -stable updates queued for the active kernel versions, but
>> they will come out once this series has made it into the tree, since I'm
>> trying to isolate any 4.12 issues from other -stable updates.
>>
>> I built and booted all the qemu targets for 4.12, and have built for
>> core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
>> architectures. My testing didn't pick up any regressions, but I was battling
>> some other build errors (non kernel related) during my testing, so I can
>> never be 100% sure.
>>
>> I've sent patches to poky to remove/bump any references to the 4.1 kernel
>> .. if I've missed any, I'm sure people will shout.
> 
> Thanks for the other fix, not got that tested yet as builds are still
> ongoing. However there appears to be a perf issue:
> 
> https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
> [and so on]
> 

Aha. There's a difference in the clibrary that I was using. I'll have
a closer look once my switch over and build gets going.

Bruce

> Cheers,
> 
> Richard
> 
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Mon, 2017-08-21 at 12:12 -0400, Bruce Ashfield wrote:
> On 2017-08-21 11:55 AM, Richard Purdie wrote:
> > 
> > On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > > 
> > > Here's the collected set of kernel changes that are ready for the
> > > M3
> > > builds.
> > > 
> > > We have some kernel meta data changes:
> > > 
> > >    kernel-yocto: configuration updates: x86 features
> > >    linux-yocto/4.1: fix fsl-ls10xx sdhci
> > >    linux-yocto: add usb-net configs by default
> > > 
> > > Some bug fixes:
> > > 
> > >    kernel-yocto: ensure that only valid BSPs are built
> > >    linux-yocto/4.10: CVE & misc fixes
> > > 
> > > And the important changes are the addition of the 4.12 kernel +
> > > libc headers
> > > and the removal of the 4.1 kernel.
> > > 
> > > I also have some -stable updates queued for the active kernel
> > > versions, but
> > > they will come out once this series has made it into the tree,
> > > since I'm
> > > trying to isolate any 4.12 issues from other -stable updates.
> > > 
> > > I built and booted all the qemu targets for 4.12, and have built
> > > for
> > > core-image-sato, core-image-kernel-dev, glibc and muslc for all
> > > of the
> > > architectures. My testing didn't pick up any regressions, but I
> > > was battling
> > > some other build errors (non kernel related) during my testing,
> > > so I can
> > > never be 100% sure.
> > > 
> > > I've sent patches to poky to remove/bump any references to the
> > > 4.1 kernel
> > > .. if I've missed any, I'm sure people will shout.
> > Thanks for the other fix, not got that tested yet as builds are
> > still
> > ongoing. However there appears to be a perf issue:
> > 
> > https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/42
> > 9/steps/BuildImages/logs/stdio
> > https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
> > s/77/steps/BuildImages/logs/stdio
> > https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
> > s/77/steps/BuildImages_1/logs/stdio
> > https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
> > s/77/steps/BuildImages_2/logs/stdio
> > [and so on]
> > 
> Aha. There's a difference in the clibrary that I was using. I'll have
> a closer look once my switch over and build gets going.

Thanks, I think you got that one but the /bin/awk issue remained after
your changes. Its easy to reproduce with "bitbake core-image-sato-sdk", 
or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this change
to fix it:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=a28acfa6c5890df4f5cb09962ef0c53837ac3b37

which I appreciate you won't like but it illustrates the problem. Any
preference on what to do with that patch?

We do also have a boot test issue on mips64:

https://autobuilder.yocto.io/builders/nightly-mips64/builds/423/steps/Running%20Sanity%20Tests/logs/stdio

and mips:

https://autobuilder.yocto.io/builders/nightly-mips/builds/425/steps/Running%20Sanity%20Tests/logs/stdio

I assume we just have to whitelist that error message?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 10:24 AM, Richard Purdie wrote:
> On Mon, 2017-08-21 at 12:12 -0400, Bruce Ashfield wrote:
>> On 2017-08-21 11:55 AM, Richard Purdie wrote:
>>>
>>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>>>>
>>>> Here's the collected set of kernel changes that are ready for the
>>>> M3
>>>> builds.
>>>>
>>>> We have some kernel meta data changes:
>>>>
>>>>     kernel-yocto: configuration updates: x86 features
>>>>     linux-yocto/4.1: fix fsl-ls10xx sdhci
>>>>     linux-yocto: add usb-net configs by default
>>>>
>>>> Some bug fixes:
>>>>
>>>>     kernel-yocto: ensure that only valid BSPs are built
>>>>     linux-yocto/4.10: CVE & misc fixes
>>>>
>>>> And the important changes are the addition of the 4.12 kernel +
>>>> libc headers
>>>> and the removal of the 4.1 kernel.
>>>>
>>>> I also have some -stable updates queued for the active kernel
>>>> versions, but
>>>> they will come out once this series has made it into the tree,
>>>> since I'm
>>>> trying to isolate any 4.12 issues from other -stable updates.
>>>>
>>>> I built and booted all the qemu targets for 4.12, and have built
>>>> for
>>>> core-image-sato, core-image-kernel-dev, glibc and muslc for all
>>>> of the
>>>> architectures. My testing didn't pick up any regressions, but I
>>>> was battling
>>>> some other build errors (non kernel related) during my testing,
>>>> so I can
>>>> never be 100% sure.
>>>>
>>>> I've sent patches to poky to remove/bump any references to the
>>>> 4.1 kernel
>>>> .. if I've missed any, I'm sure people will shout.
>>> Thanks for the other fix, not got that tested yet as builds are
>>> still
>>> ongoing. However there appears to be a perf issue:
>>>
>>> https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/42
>>> 9/steps/BuildImages/logs/stdio
>>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
>>> s/77/steps/BuildImages/logs/stdio
>>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
>>> s/77/steps/BuildImages_1/logs/stdio
>>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build
>>> s/77/steps/BuildImages_2/logs/stdio
>>> [and so on]
>>>
>> Aha. There's a difference in the clibrary that I was using. I'll have
>> a closer look once my switch over and build gets going.
> 
> Thanks, I think you got that one but the /bin/awk issue remained after
> your changes. Its easy to reproduce with "bitbake core-image-sato-sdk",
> or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this change
> to fix it:

Yah, I noticed all of those references as well. Saul had dealt with
the one that hit us before, but I wasn't able to trigger any installs
of the other parts in the images I built .. so they were being left
be for now, just to keep our footprint low.

> 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=a28acfa6c5890df4f5cb09962ef0c53837ac3b37
> 
> which I appreciate you won't like but it illustrates the problem. Any
> preference on what to do with that patch?

I can merge it directly into linux-yocto, since that is what we did
with Saul's change before, and at the same time, we can submit it
upstream and drop it next release.

> 
> We do also have a boot test issue on mips64:
> 
> https://autobuilder.yocto.io/builders/nightly-mips64/builds/423/steps/Running%20Sanity%20Tests/logs/stdio
> 
> and mips:
> 
> https://autobuilder.yocto.io/builders/nightly-mips/builds/425/steps/Running%20Sanity%20Tests/logs/stdio
> 
> I assume we just have to whitelist that error message?

Yep. It is something that has been around for a while and comes from
the general open firmware support. It is a warning only (obviously)
and can safely be ignored. We keep the OF support on for compatibility
so live with a few warnings like that.

Bruce

> 
> Cheers,
> 
> Richard
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
> On 08/22/2017 10:24 AM, Richard Purdie wrote:
> > 
> > Thanks, I think you got that one but the /bin/awk issue remained
> > after
> > your changes. Its easy to reproduce with "bitbake core-image-sato-
> > sdk",
> > or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this
> > change
> > to fix it:
> Yah, I noticed all of those references as well. Saul had dealt with
> the one that hit us before, but I wasn't able to trigger any installs
> of the other parts in the images I built .. so they were being left
> be for now, just to keep our footprint low.
> 
> > 
> > 
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=
> > a28acfa6c5890df4f5cb09962ef0c53837ac3b37
> > 
> > which I appreciate you won't like but it illustrates the problem.
> > Any
> > preference on what to do with that patch?
> I can merge it directly into linux-yocto, since that is what we did
> with Saul's change before, and at the same time, we can submit it
> upstream and drop it next release.

Ok, Should I merge my patch for now and you and then deal with it in
due course or do you want to do that directly?

I can take care of the mips issue but we have one final problem:

"oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"

is failing, it works with 4.10, fails with 4.12. Did some key config
option for booting isos go missing?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 11:28 AM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 10:24 AM, Richard Purdie wrote:
>>>   
>>> Thanks, I think you got that one but the /bin/awk issue remained
>>> after
>>> your changes. Its easy to reproduce with "bitbake core-image-sato-
>>> sdk",
>>> or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this
>>> change
>>> to fix it:
>> Yah, I noticed all of those references as well. Saul had dealt with
>> the one that hit us before, but I wasn't able to trigger any installs
>> of the other parts in the images I built .. so they were being left
>> be for now, just to keep our footprint low.
>>
>>>
>>>
>>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=
>>> a28acfa6c5890df4f5cb09962ef0c53837ac3b37
>>>
>>> which I appreciate you won't like but it illustrates the problem.
>>> Any
>>> preference on what to do with that patch?
>> I can merge it directly into linux-yocto, since that is what we did
>> with Saul's change before, and at the same time, we can submit it
>> upstream and drop it next release.
> 
> Ok, Should I merge my patch for now and you and then deal with it in
> due course or do you want to do that directly?

I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me to do.

.. but if it isn't for you, go ahead and do the merge and I'll
sort it out in a follow up.

> 
> I can take care of the mips issue but we have one final problem:
> 
> "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
> 
> is failing, it works with 4.10, fails with 4.12. Did some key config
> option for booting isos go missing?

Not that I'm aware of, but I admit that I've never done any ISO
booting of the images so wouldn't see it.

I'll diff the configs here and see if anything jumps out. Otherwise,
I'll do a boot test myself and debug from there.

Bruce

> 
> Cheers,
> 
> Richard
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> I can send you a v4 of the 4.12 patch in the next half an hour,
> that's easiest for me to do.
> 
> .. but if it isn't for you, go ahead and do the merge and I'll
> sort it out in a follow up.

The above works, I'm still trying to get to the bottom of the other
issues that are going on.

> > I can take care of the mips issue but we have one final problem:
> > 
> > "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
> > 
> > is failing, it works with 4.10, fails with 4.12. Did some key
> > config
> > option for booting isos go missing?
> Not that I'm aware of, but I admit that I've never done any ISO
> booting of the images so wouldn't see it.
> 
> I'll diff the configs here and see if anything jumps out. Otherwise,
> I'll do a boot test myself and debug from there.

After running the failing test case, I was able to manually boot with:

tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -cdrom tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822154904.iso -no-reboot -vga vmware -show-cursor -usb -device usb-tablet -device virtio-rng-pci  -nographic   -cpu core2duo -m 256

and then quickly "down, enter" to select the serial console option
which gave me this:

[    4.980303] netconsole: network logging started
[    4.980981] rtc_cmos 00:00: setting system clock to 2017-08-22 15:56:12 UTC (1503417372)
[    5.036130] Freeing unused kernel memory: 1440K
[    5.036320] Write protecting the kernel read-only data: 14336k
[    5.039206] Freeing unused kernel memory: 864K
[    5.072281] Freeing unused kernel memory: 1232K
[    5.173842] usb 1-1: new full-speed USB device number 2 using uhci_hcd
starting version 234
[    5.349596] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
[    5.361353] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
[    5.504201] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[    6.408140] BUG: unable to handle kernel NULL pointer dereference at           (null)
[    6.408651] IP: ide_cdrom_prep_fn+0x63/0x180
[    6.408802] PGD beed067 
[    6.408834] P4D beed067 
[    6.408935] PUD 0 
[    6.409028] 
[    6.409251] Oops: 0002 [#1] PREEMPT SMP
[    6.409524] Modules linked in:
[    6.409811] CPU: 0 PID: 117 Comm: udevd Not tainted 4.12.7-yocto-standard #4
[    6.410012] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
[    6.410399] task: ffff9366cbd87080 task.stack: ffff9778c0304000
[    6.410613] RIP: 0010:ide_cdrom_prep_fn+0x63/0x180
[    6.410749] RSP: 0018:ffff9778c0307ad8 EFLAGS: 00000002
[    6.410902] RAX: 0000000000000002 RBX: ffff9366cc3ef800 RCX: 0000000000000000
[    6.411089] RDX: 0000000000000000 RSI: ffff9366cbf1ec00 RDI: 000000000000a1fc
[    6.411318] RBP: ffff9778c0307ad8 R08: 0000000000000000 R09: 0000000000000001
[    6.411510] R10: 0000000000000020 R11: 0000000020112a00 R12: ffff9366cbf1ec00
[    6.411717] R13: 00000000ffffff87 R14: 00000000fffffffb R15: 0000000000000000
[    6.411938] FS:  00007fd6fa79e300(0000) GS:ffff9366cf200000(0000) knlGS:0000000000000000
[    6.412153] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    6.412351] CR2: 0000000000000000 CR3: 000000000beec000 CR4: 00000000000006f0
[    6.412686] Call Trace:
[    6.413793]  blk_peek_request+0x189/0x2d0
[    6.414010]  blk_fetch_request+0x12/0x30
[    6.414142]  ? _raw_spin_unlock_irq+0x23/0x30
[    6.414276]  do_ide_request+0x37d/0x660
[    6.414382]  ? cfq_group_service_tree_add+0x94/0xc0
[    6.414559]  ? cfq_service_tree_add+0x258/0x300
[    6.414695]  ? ktime_get+0x40/0xa0
[    6.414800]  __blk_run_queue+0x33/0x40
[    6.414908]  queue_unplugged+0x2f/0xc0
[    6.415017]  blk_flush_plug_list+0x1f9/0x240
[    6.415138]  blk_finish_plug+0x2c/0x40
[    6.415255]  __do_page_cache_readahead+0x1bd/0x260
[    6.415408]  force_page_cache_readahead+0xb5/0x110
[    6.415550]  ? force_page_cache_readahead+0xb5/0x110
[    6.415687]  page_cache_sync_readahead+0x3f/0x50
[    6.415815]  generic_file_read_iter+0x54b/0x700
[    6.415965]  blkdev_read_iter+0x35/0x40
[    6.416085]  __vfs_read+0xbf/0x110
[    6.416182]  vfs_read+0x8e/0x110
[    6.416279]  SyS_read+0x46/0xb0
[    6.416369]  ? SyS_lseek+0x87/0xb0
[    6.416469]  entry_SYSCALL_64_fastpath+0x1a/0xa5
[    6.416747] RIP: 0033:0x7fd6f9b06891
[    6.416854] RSP: 002b:00007fff59e50a08 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
[    6.417057] RAX: ffffffffffffffda RBX: 00007fff59e4f950 RCX: 00007fd6f9b06891
[    6.417248] RDX: 0000000000000200 RSI: 00007fff59e50ac0 RDI: 000000000000000c
[    6.417439] RBP: 00007fff59e4f950 R08: 0000000000000000 R09: 00007fd6f98751c0
[    6.417643] R10: 000000000000006d R11: 0000000000000246 R12: 00007fff59e509d8
[    6.417832] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    6.418057] Code: 2f 01 00 00 b9 01 00 00 00 bf 01 00 00 00 48 8b 46 60 48 99 48 f7 ff 48 89 c7 8b 46 58 31 d2 c1 e8 09 f7 f1 48 8b 8e 50 01 00 00 <48> c7 01 00 00 00 00 48 c7 41 08 00 00 00 00 f6 46 44 01 48 8b 
[    6.418825] RIP: ide_cdrom_prep_fn+0x63/0x180 RSP: ffff9778c0307ad8
[    6.419017] CR2: 0000000000000000
[    6.419324] ---[ end trace dd02c5282d34fc7b ]---
[    6.419558] note: udevd[117] exited with preempt_count 1
Waiting for removable media...

Something in the IDE CDROM driver?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:00 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>> I can send you a v4 of the 4.12 patch in the next half an hour,
>> that's easiest for me to do.
>>
>> .. but if it isn't for you, go ahead and do the merge and I'll
>> sort it out in a follow up.
> 
> The above works, I'm still trying to get to the bottom of the other
> issues that are going on.

Patch sent as a v4 (although I now realize I forgot to put
v4 in the subject, only in the summary).

> 
>>> I can take care of the mips issue but we have one final problem:
>>>
>>> "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
>>>
>>> is failing, it works with 4.10, fails with 4.12. Did some key
>>> config
>>> option for booting isos go missing?
>> Not that I'm aware of, but I admit that I've never done any ISO
>> booting of the images so wouldn't see it.
>>
>> I'll diff the configs here and see if anything jumps out. Otherwise,
>> I'll do a boot test myself and debug from there.
> 
> After running the failing test case, I was able to manually boot with:
> 
> tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -cdrom tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822154904.iso -no-reboot -vga vmware -show-cursor -usb -device usb-tablet -device virtio-rng-pci  -nographic   -cpu core2duo -m 256
> 
> and then quickly "down, enter" to select the serial console option
> which gave me this:
> 
> [    4.980303] netconsole: network logging started
> [    4.980981] rtc_cmos 00:00: setting system clock to 2017-08-22 15:56:12 UTC (1503417372)
> [    5.036130] Freeing unused kernel memory: 1440K
> [    5.036320] Write protecting the kernel read-only data: 14336k
> [    5.039206] Freeing unused kernel memory: 864K
> [    5.072281] Freeing unused kernel memory: 1232K
> [    5.173842] usb 1-1: new full-speed USB device number 2 using uhci_hcd
> starting version 234
> [    5.349596] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
> [    5.361353] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
> [    5.504201] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
> [    6.408140] BUG: unable to handle kernel NULL pointer dereference at           (null)
> [    6.408651] IP: ide_cdrom_prep_fn+0x63/0x180
> [    6.408802] PGD beed067
> [    6.408834] P4D beed067
> [    6.408935] PUD 0
> [    6.409028]
> [    6.409251] Oops: 0002 [#1] PREEMPT SMP
> [    6.409524] Modules linked in:
> [    6.409811] CPU: 0 PID: 117 Comm: udevd Not tainted 4.12.7-yocto-standard #4
> [    6.410012] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
> [    6.410399] task: ffff9366cbd87080 task.stack: ffff9778c0304000
> [    6.410613] RIP: 0010:ide_cdrom_prep_fn+0x63/0x180
> [    6.410749] RSP: 0018:ffff9778c0307ad8 EFLAGS: 00000002
> [    6.410902] RAX: 0000000000000002 RBX: ffff9366cc3ef800 RCX: 0000000000000000
> [    6.411089] RDX: 0000000000000000 RSI: ffff9366cbf1ec00 RDI: 000000000000a1fc
> [    6.411318] RBP: ffff9778c0307ad8 R08: 0000000000000000 R09: 0000000000000001
> [    6.411510] R10: 0000000000000020 R11: 0000000020112a00 R12: ffff9366cbf1ec00
> [    6.411717] R13: 00000000ffffff87 R14: 00000000fffffffb R15: 0000000000000000
> [    6.411938] FS:  00007fd6fa79e300(0000) GS:ffff9366cf200000(0000) knlGS:0000000000000000
> [    6.412153] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    6.412351] CR2: 0000000000000000 CR3: 000000000beec000 CR4: 00000000000006f0
> [    6.412686] Call Trace:
> [    6.413793]  blk_peek_request+0x189/0x2d0
> [    6.414010]  blk_fetch_request+0x12/0x30
> [    6.414142]  ? _raw_spin_unlock_irq+0x23/0x30
> [    6.414276]  do_ide_request+0x37d/0x660
> [    6.414382]  ? cfq_group_service_tree_add+0x94/0xc0
> [    6.414559]  ? cfq_service_tree_add+0x258/0x300
> [    6.414695]  ? ktime_get+0x40/0xa0
> [    6.414800]  __blk_run_queue+0x33/0x40
> [    6.414908]  queue_unplugged+0x2f/0xc0
> [    6.415017]  blk_flush_plug_list+0x1f9/0x240
> [    6.415138]  blk_finish_plug+0x2c/0x40
> [    6.415255]  __do_page_cache_readahead+0x1bd/0x260
> [    6.415408]  force_page_cache_readahead+0xb5/0x110
> [    6.415550]  ? force_page_cache_readahead+0xb5/0x110
> [    6.415687]  page_cache_sync_readahead+0x3f/0x50
> [    6.415815]  generic_file_read_iter+0x54b/0x700
> [    6.415965]  blkdev_read_iter+0x35/0x40
> [    6.416085]  __vfs_read+0xbf/0x110
> [    6.416182]  vfs_read+0x8e/0x110
> [    6.416279]  SyS_read+0x46/0xb0
> [    6.416369]  ? SyS_lseek+0x87/0xb0
> [    6.416469]  entry_SYSCALL_64_fastpath+0x1a/0xa5
> [    6.416747] RIP: 0033:0x7fd6f9b06891
> [    6.416854] RSP: 002b:00007fff59e50a08 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> [    6.417057] RAX: ffffffffffffffda RBX: 00007fff59e4f950 RCX: 00007fd6f9b06891
> [    6.417248] RDX: 0000000000000200 RSI: 00007fff59e50ac0 RDI: 000000000000000c
> [    6.417439] RBP: 00007fff59e4f950 R08: 0000000000000000 R09: 00007fd6f98751c0
> [    6.417643] R10: 000000000000006d R11: 0000000000000246 R12: 00007fff59e509d8
> [    6.417832] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [    6.418057] Code: 2f 01 00 00 b9 01 00 00 00 bf 01 00 00 00 48 8b 46 60 48 99 48 f7 ff 48 89 c7 8b 46 58 31 d2 c1 e8 09 f7 f1 48 8b 8e 50 01 00 00 <48> c7 01 00 00 00 00 48 c7 41 08 00 00 00 00 f6 46 44 01 48 8b
> [    6.418825] RIP: ide_cdrom_prep_fn+0x63/0x180 RSP: ffff9778c0307ad8
> [    6.419017] CR2: 0000000000000000
> [    6.419324] ---[ end trace dd02c5282d34fc7b ]---
> [    6.419558] note: udevd[117] exited with preempt_count 1
> Waiting for removable media...
> 
> Something in the IDE CDROM driver?

I keep getting sent changes to drop IDE support completely, but
they aren't in play here, I'm still waiting on a 4.10 linux-yocto
to configure so I can diff the .configs and fire up some comparison
boot tests.

Bruce

> 
> Cheers,
> 
> Richard
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:00 PM, Richard Purdie wrote:
> > 
> > On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> > > 
> > > I can send you a v4 of the 4.12 patch in the next half an hour,
> > > that's easiest for me to do.
> > > 
> > > .. but if it isn't for you, go ahead and do the merge and I'll
> > > sort it out in a follow up.
> > The above works, I'm still trying to get to the bottom of the other
> > issues that are going on.
> Patch sent as a v4 (although I now realize I forgot to put
> v4 in the subject, only in the summary).

Thanks, I'll pull that into subsequent test runs.

> > Something in the IDE CDROM driver?
> I keep getting sent changes to drop IDE support completely, but
> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
> to configure so I can diff the .configs and fire up some comparison
> boot tests.

I did diff the configs and nothing jumped out to me at
least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
relevant as it only affects built in initramfs afaict.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

Likewise, I'm seeing only noise in the diff (i.e. new selected options)
and nothing that should break this.

Could be a valid issue with the driver. I'm onto some boot testing
now.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

I am seeing the same thing, and can't see anything obvious.

I'm now doing a git bisect between 4.10 and 4.12.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

I found the commit that is causing the problem (after three hours
of bisecting). That's the good news. The bad news is it isn't something
I can revert .. or easily fix, since the commit is large and is pretty
much tree wide. There's a lot of commits stacked on top if that change,
so it can't be reverted.

------------

commit 82ed4db499b8598f16f8871261bff088d6b0597f
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 27 09:46:29 2017 +0100

     block: split scsi_request out of struct request

     And require all drivers that want to support BLOCK_PC to allocate it
     as the first thing of their private data.  To support this the legacy
     IDE and BSG code is switched to set cmd_size on their queues to let
     the block layer allocate the additional space.

     Signed-off-by: Christoph Hellwig <hch@lst.de>
     Signed-off-by: Jens Axboe <axboe@fb.com>

---------

I was able to boot with the following in the command line:

-drive 
file=tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822200708.iso,if=virtio,media=cdrom

--------

IMHO we need to stop using the ancient IDE support, since it continually
is broken (not usually this badly .. but often in more subtle ways).

So switching to a virtio backed CDROM, while the issue is reported
upstream is probably the best bet.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 16:34 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:07 PM, Richard Purdie wrote:
> I found the commit that is causing the problem (after three hours
> of bisecting). That's the good news. The bad news is it isn't
> something
> I can revert .. or easily fix, since the commit is large and is
> pretty
> much tree wide. There's a lot of commits stacked on top if that
> change,
> so it can't be reverted.
> 
> ------------
> 
> commit 82ed4db499b8598f16f8871261bff088d6b0597f
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Fri Jan 27 09:46:29 2017 +0100
> 
>      block: split scsi_request out of struct request
> 
>      And require all drivers that want to support BLOCK_PC to
> allocate it
>      as the first thing of their private data.  To support this the
> legacy
>      IDE and BSG code is switched to set cmd_size on their queues to
> let
>      the block layer allocate the additional space.
> 
>      Signed-off-by: Christoph Hellwig <hch@lst.de>
>      Signed-off-by: Jens Axboe <axboe@fb.com>
> 
> ---------
> 
> I was able to boot with the following in the command line:
> 
> -drive 
> file=tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-
> 20170822200708.iso,if=virtio,media=cdrom
> 
> --------
> 
> IMHO we need to stop using the ancient IDE support, since it
> continually
> is broken (not usually this badly .. but often in more subtle ways).
> 
> So switching to a virtio backed CDROM, while the issue is reported
> upstream is probably the best bet.

That seems reasonable to me and should be a simple change to the
runqemu script. The hint above should let me test that so I'll try and
and see how the builds work out. Thanks for the help in figuring a
workaround!

Cheers,

Richard

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

This is the last set of -stable and meta data changes for the 2.4
release window. I've also brough aufs4 into the 4.12 tree to keep
it feature consistent with all the previous linux-yocto kernels
(and given some bug reports, folks are using the aufs support).

They are -stable updates, some configuration tweaks and a round of
CVE fixes that won't make -stable before we release.

I'm still trying to track down the reported race in meta data
gathering and the rcu stalls in qemuppc, but no sense holding onto
these while those issues churn.

Cheers,

Bruce

The following changes since commit e3a69364eb1fdbf1dcb98a04b3ddfc8f9841a7fa:

  staging: gracefully abort if two recipes conflict in the sysroot (2017-09-11 17:30:30 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  linux-yocto/meta: configuration feature additions
  linux-yocto/4.12: update to v4.12.12
  linux-yocto/4.9: update to v4.9.49
  linux-yocto/4.4: update to v4.4.87
  linux-yocto/4.12: integrate aufs4 core support
  linux-yocto/4.10: bluetooth: CVE-2017-1000251
  linux-yocto/4.12: bluetooth: CVE-2017-1000251
  linux-yocto/4.9: bluetooth: CVE-2017-1000251
  linux-yocto/4.4: bluetooth: CVE-2017-1000251

 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb  |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.10.bb      | 18 +++++++++---------
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb       | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.9.bb       | 20 ++++++++++----------
 12 files changed, 61 insertions(+), 61 deletions(-)

-- 
2.5.0

[PATCH 1/9] linux-yocto/meta: configuration feature additions

[Bruce Ashfield]

Introducing the following configuration features:

  d67d2221cc2d bpf: add bpf kernel config
  3f9fb678aa31 sysrq: add sysrq kernel config
  729eb982ffd8 kexec/kdump: Add config fragments
  e00e63ef3068 kdump: add config fragments

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index 37ccc727fc0c..f3130ad91b7d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "42965d664ffcac13ff4dffddcd4959ab08f19508"
+SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index a9db5ae18753..a1ba04102ec3 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "42965d664ffcac13ff4dffddcd4959ab08f19508"
+SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index 026d72e1f7a0..6cd82df8d2ff 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
 SRCREV_machine_qemux86-64 ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
 SRCREV_machine_qemumips64 ?= "ec95c3aebd1d653a409e844779d2a34666627f59"
 SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "42965d664ffcac13ff4dffddcd4959ab08f19508"
+SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
-- 
2.5.0

[PATCH 2/9] linux-yocto/4.12: update to v4.12.12

[Bruce Ashfield]

Integrating the korg stable update comprising the following commits:

   6ff98e8e5d24 Linux 4.12.12
   ce4ef9346d9f rtlwifi: Fix fallback firmware loading
   21da5e36f41e rtlwifi: Fix memory leak when firmware request fails
   3ef5220bdba7 of/device: Prevent buffer overflow in of_device_modalias()
   aee0b37b710e scsi: sg: recheck MMAP_IO request length with lock held
   b0f24dc0e57b scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE
   1054309aca02 cs5536: add support for IDE controller variant
   e5298cd80371 ahci: don't use MSI for devices with the silly Intel NVMe remapping scheme
   f21c4eea8bb4 workqueue: Fix flag collision
   daf316ac4a6c drm/nouveau: Fix error handling in nv50_disp_atomic_commit
   75bc569a0d4b drm/nouveau/pci/msi: disable MSI on big-endian platforms by default
   e3b9fb20262f s390/mm: fix BUG_ON in crst_table_upgrade
   2ce0e0495177 s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs
   d859d5a434f1 MCB: add support for SC31 to mcb-lpc
   f7fb789880dd mwifiex: correct channel stat buffer overflows
   0bfb078274ed dlm: avoid double-free on error path in dlm_device_{register,unregister}
   985696916329 iwlwifi: pci: add new PCI ID for 7265D
   cbe865a2e67d Bluetooth: Add support of 13d3:3494 RTL8723BE device
   7d20c5530a56 rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter
   a47814b210eb Input: trackpoint - assume 3 buttons when buttons detection fails
   d49ea1b6f98f ath10k: fix memory leak in rx ring buffer allocation
   270f0aadd1d2 intel_th: pci: Add Cannon Lake PCH-LP support
   d2192374b951 intel_th: pci: Add Cannon Lake PCH-H support
   055be595e016 fpga: altera-hps2fpga: fix multiple init of l3_remap_lock
   ba89dc8dce4e crypto: caam/qi - fix compilation with DEBUG enabled
   aa57cf57df95 crypto: caam/qi - fix compilation with CONFIG_DEBUG_FORCE_WEAK_PER_CPU=y
   693ef09dc616 binder: free memory on error
   bbe1a3b3d20d HID: wacom: Do not completely map WACOM_HID_WD_TOUCHRINGSTATUS usage
   af617519a8c2 driver core: bus: Fix a potential double free
   6c6c3c6bd954 iio: adc: ti-ads1015: add adequate wait time to get correct conversion
   00202ded930e iio: adc: ti-ads1015: don't return invalid value from buffer setup callbacks
   303d31eb5adf iio: adc: ti-ads1015: avoid getting stale result after runtime resume
   6c164a8ad918 iio: adc: ti-ads1015: enable conversion when CONFIG_PM is not set
   6c5595e0815d iio: adc: ti-ads1015: fix scale information for ADS1115
   1d7fadc5937f iio: adc: ti-ads1015: fix incorrect data rate setting update
   70bfcf9e319e staging/rts5208: fix incorrect shift to extract upper nybble
   ed68c935f5ae USB: core: Avoid race of async_completed() w/ usbdev_release()
   ffdb5b9e299a ANDROID: binder: add hwbinder,vndbinder to BINDER_DEVICES.
   74ffccfed38f ANDROID: binder: add padding to binder_fd_array_object.
   68596cc21060 USB: musb: fix external abort on suspend
   c927f42c8e38 usb:xhci:Fix regression when ATI chipsets detected
   0e8e379786da usb: Add device quirk for Logitech HD Pro Webcam C920-C
   c8ff3d1a47a2 USB: serial: option: add support for D-Link DWM-157 C1
   572bcfc7fbce usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard
   13817987369a Linux 4.12.11
   9c2144e80db8 epoll: fix race between ep_poll_callback(POLLFREE) and ep_free()/ep_remove()
   38f5d65ad997 drm/nouveau/i2c/gf119-: add support for address-only transactions
   bdacc5fcf4f9 nvme: fix the definition of the doorbell buffer config support bit
   c6d2779d8f0d drm/ttm: Fix accounting error when fail to get pages for pool
   6c5b60edd786 xfrm: policy: check policy direction value
   6cc6f45db016 lib/mpi: kunmap after finishing accessing buffer
   a3deff1d3285 mmc: sdhci-xenon: add set_power callback
   d767ccb7c387 wl1251: add a missing spin_lock_init()
   619d31a0d247 drm/vmwgfx: Fix F26 Wayland screen update issue
   399081a50c48 dm mpath: do not lock up a CPU with requeuing activity
   77ab9e7fb431 CIFS: remove endian related sparse warning
   0627f7136685 CIFS: Fix maximum SMB2 header size
   f3e9dc4504b1 alpha: uapi: Add support for __SANE_USERSPACE_TYPES__
   ae53897e22db cpuset: Fix incorrect memory_pressure control file mapping
   fd20ca80f807 cpumask: fix spurious cpumask_of_node() on non-NUMA multi-node configs
   3d7aeba120fd ceph: fix readpage from fscache
   b3010084e111 mm, madvise: ensure poisoned pages are removed from per-cpu lists
   8c46edd78de9 mm, uprobes: fix multiple free of ->uprobes_state.xol_area
   726bd348ead3 crypto: algif_skcipher - only call put_page on referenced and used pages
   44c6b4a96625 i2c: ismt: Return EMSGSIZE for block reads with bogus length
   7a90bfae6345 i2c: ismt: Don't duplicate the receive length for block reads
   6fb972d03751 crypto: chacha20 - fix handling of chunked input
   6b31ae8707a7 Input: xpad - fix PowerA init quirk for some gamepad models
   2ed56448f555 Input: synaptics - fix device info appearing different on reconnect
   55a5a10ce349 irqchip: mips-gic: SYNC after enabling GIC region
   691208979811 x86/io: Add "memory" clobber to insb/insw/insl/outsb/outsw/outsl
   34ed350889dd arm64: mm: abort uaccess retries upon fatal signal

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 20 ++++++++++----------
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index f3130ad91b7d..f19e1248a90a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -11,13 +11,13 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
+SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.12.10"
+LINUX_VERSION ?= "4.12.12"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index a1ba04102ec3..fa3cd2075b8f 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.12.10"
+LINUX_VERSION ?= "4.12.12"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
+SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index 6cd82df8d2ff..e9838247f45e 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "fd1626821467303bd084dc28d41f9093d60c3f31"
-SRCREV_machine_qemuarm64 ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_machine_qemumips ?= "0d351d8eb3feeb121e859cb77c16dd0f46007a15"
-SRCREV_machine_qemuppc ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_machine_qemux86 ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_machine_qemux86-64 ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_machine_qemumips64 ?= "ec95c3aebd1d653a409e844779d2a34666627f59"
-SRCREV_machine ?= "b5c8cfda2dfe296410d51e131289fb09c69e1e7d"
-SRCREV_meta ?= "91b4e89037c3575912d6c3cc8977db7ea83b81f1"
+SRCREV_machine_qemuarm ?= "1f5c932260cac2118d256d38b475a2811a8551e5"
+SRCREV_machine_qemuarm64 ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_machine_qemumips ?= "a9f98cc2715a65537877c86808a101429028d48b"
+SRCREV_machine_qemuppc ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_machine_qemux86 ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_machine_qemux86-64 ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_machine_qemumips64 ?= "1863c93b44aeb6badb4993fd9a6ab3d360bf30d1"
+SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
+SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.12.10"
+LINUX_VERSION ?= "4.12.12"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

[PATCH 3/9] linux-yocto/4.9: update to v4.9.49

[Bruce Ashfield]

Integrating the korg -stable updates that comprise the following commits:

   f07cb3489cff Linux 4.9.49
   8bc67f67b763 drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event()
   8b5a7e443622 drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq context
   7791b59153cb scsi: sg: recheck MMAP_IO request length with lock held
   b06e1abf1ff2 scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE
   5b9c6a54c629 cs5536: add support for IDE controller variant
   ec552ece1f25 workqueue: Fix flag collision
   25bdc516b58e drm/nouveau/pci/msi: disable MSI on big-endian platforms by default
   078866740e35 s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs
   c193becad9ad MCB: add support for SC31 to mcb-lpc
   0e720cd70631 mwifiex: correct channel stat buffer overflows
   5c23d3ed1190 dlm: avoid double-free on error path in dlm_device_{register,unregister}
   23b7d4f52b69 iwlwifi: pci: add new PCI ID for 7265D
   747562619512 Bluetooth: Add support of 13d3:3494 RTL8723BE device
   b48f7183c64c rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter
   ed7a384a904f Input: trackpoint - assume 3 buttons when buttons detection fails
   90a1e2e19ed7 ath10k: fix memory leak in rx ring buffer allocation
   d8b992d93555 intel_th: pci: Add Cannon Lake PCH-LP support
   a22d561178ee intel_th: pci: Add Cannon Lake PCH-H support
   5555eb956edc driver core: bus: Fix a potential double free
   ffb58b875d24 iio: adc: ti-ads1015: add adequate wait time to get correct conversion
   ff4a98e3bcb3 iio: adc: ti-ads1015: don't return invalid value from buffer setup callbacks
   1ed4565b7c7b iio: adc: ti-ads1015: avoid getting stale result after runtime resume
   c72ad1a4fdf0 iio: adc: ti-ads1015: enable conversion when CONFIG_PM is not set
   115af6c3b155 iio: adc: ti-ads1015: fix scale information for ADS1115
   177d84e3a72a iio: adc: ti-ads1015: fix incorrect data rate setting update
   e58b04fb5b0b staging/rts5208: fix incorrect shift to extract upper nybble
   afcfe0661a74 USB: core: Avoid race of async_completed() w/ usbdev_release()
   80cdcd7f5335 USB: musb: fix external abort on suspend
   6b3b3a22ef20 usb:xhci:Fix regression when ATI chipsets detected
   99a22c84f51d usb: Add device quirk for Logitech HD Pro Webcam C920-C
   773b93f4255f USB: serial: option: add support for D-Link DWM-157 C1
   2ea91c52ff5f usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard
   8a697a50c090 Linux 4.9.48
   d325f1f1e245 epoll: fix race between ep_poll_callback(POLLFREE) and ep_free()/ep_remove()
   dd2342ad6665 kvm: arm/arm64: Force reading uncached stage2 PGD
   70df301a083c drm/ttm: Fix accounting error when fail to get pages for pool
   12a70ccaa686 xfrm: policy: check policy direction value
   31decdcd8369 lib/mpi: kunmap after finishing accessing buffer
   9e2788ce8f17 wl1251: add a missing spin_lock_init()
   e2ae90bb85f8 CIFS: remove endian related sparse warning
   c5e76654a9e5 CIFS: Fix maximum SMB2 header size
   d4e7dfda905e alpha: uapi: Add support for __SANE_USERSPACE_TYPES__
   309e4dbfaf3d cpuset: Fix incorrect memory_pressure control file mapping
   da16ed52c36a cpumask: fix spurious cpumask_of_node() on non-NUMA multi-node configs
   715849268b34 ceph: fix readpage from fscache
   8cc3acff5f1a mm, madvise: ensure poisoned pages are removed from per-cpu lists
   17c564f629f4 mm, uprobes: fix multiple free of ->uprobes_state.xol_area
   9e0a64330ce5 crypto: algif_skcipher - only call put_page on referenced and used pages
   91a0e1edb80a i2c: ismt: Return EMSGSIZE for block reads with bogus length
   d22f6da47355 i2c: ismt: Don't duplicate the receive length for block reads
   31562136c8d4 irqchip: mips-gic: SYNC after enabling GIC region
   458ca52f1564 Linux 4.9.47
   529ada21ff9e lz4: fix bogus gcc warning
   c47c52cde806 scsi: sg: reset 'res_in_use' after unlinking reserved array
   4099ac938385 scsi: sg: protect accesses to 'reserved' page array
   c0c6dff92303 locking/spinlock/debug: Remove spinlock lockup detection code
   27e7506c33d0 arm64: fpsimd: Prevent registers leaking across exec
   43f776dab360 x86/io: Add "memory" clobber to insb/insw/insl/outsb/outsw/outsl
   509d8b52bbe7 arm64: mm: abort uaccess retries upon fatal signal
   3e033635b2b7 kvm: arm/arm64: Fix race in resetting stage2 PGD
   b8a1532b16fd gcov: support GCC 7.1
   47974403c9ca staging: wilc1000: simplify vif[i]->ndev accesses
   dd758f82a3bf scsi: isci: avoid array subscript warning
   f71996c3ce5d p54: memset(0) whole array

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.9.bb      | 20 ++++++++++----------
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index 22e478e2b8fb..23c445a814af 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -11,13 +11,13 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "d3aea9ac7fa726757720afe20286c375bf7eefbc"
-SRCREV_meta ?= "f16cac53436be696fa055bc4a139f3f1dc39a9ce"
+SRCREV_machine ?= "1e3f9281ed3043b83d31a3f3dfd28cfb0343873f"
+SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.9.46"
+LINUX_VERSION ?= "4.9.49"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index 364930bac60a..0c2ff0acb272 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.9.46"
+LINUX_VERSION ?= "4.9.49"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_meta ?= "f16cac53436be696fa055bc4a139f3f1dc39a9ce"
+SRCREV_machine ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
index c4b601c464e1..dbb5d54117f2 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "5c60622f4af68de9d6d9320f7d785156d01c305c"
-SRCREV_machine_qemuarm64 ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_machine_qemumips ?= "a5673234ab47a8653b7c3629811cc9ca634fcadb"
-SRCREV_machine_qemuppc ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_machine_qemux86 ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_machine_qemux86-64 ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_machine_qemumips64 ?= "7b4d796b512ed9bb1e13af089fc4d20a35187eeb"
-SRCREV_machine ?= "cf9a7dd9f41a32c10d19a51497463d6ec2991107"
-SRCREV_meta ?= "f16cac53436be696fa055bc4a139f3f1dc39a9ce"
+SRCREV_machine_qemuarm ?= "072093c81a9329cec188905dfadb19c983be14f7"
+SRCREV_machine_qemuarm64 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine_qemumips ?= "0c66ebad24541c7673620ca433cd8478e5d06e3b"
+SRCREV_machine_qemuppc ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine_qemux86 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine_qemux86-64 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine_qemumips64 ?= "6ac61462925ac9d6f668286bc29ee54f05e8f5e9"
+SRCREV_machine ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.9.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.9.46"
+LINUX_VERSION ?= "4.9.49"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

[PATCH 4/9] linux-yocto/4.4: update to v4.4.87

[Bruce Ashfield]

Integrating the -stable update with the following commits:

   573b59e17e37 Linux 4.4.87
   d95827490c39 crypto: algif_skcipher - only call put_page on referenced and used pages
   ab3ee6b53d67 epoll: fix race between ep_poll_callback(POLLFREE) and ep_free()/ep_remove()
   628212c89fae kvm: arm/arm64: Force reading uncached stage2 PGD
   57ff696f54b5 kvm: arm/arm64: Fix race in resetting stage2 PGD
   94183009ac0e drm/ttm: Fix accounting error when fail to get pages for pool
   9b3dcc98d8df xfrm: policy: check policy direction value
   c0c2e7567a34 wl1251: add a missing spin_lock_init()
   5f08f0aebf70 CIFS: remove endian related sparse warning
   e596cc1454d4 CIFS: Fix maximum SMB2 header size
   6cdda3497db8 alpha: uapi: Add support for __SANE_USERSPACE_TYPES__
   ed48d9230e30 cpuset: Fix incorrect memory_pressure control file mapping
   15e94ec4ec21 cpumask: fix spurious cpumask_of_node() on non-NUMA multi-node configs
   857d0b3dd756 ceph: fix readpage from fscache
   043ccc9781cc i2c: ismt: Return EMSGSIZE for block reads with bogus length
   fab3229af4e5 i2c: ismt: Don't duplicate the receive length for block reads
   e119fc492de9 irqchip: mips-gic: SYNC after enabling GIC region
   cd99a4f3f43b Linux 4.4.86
   c81c4d453edf drm/i915: fix compiler warning in drivers/gpu/drm/i915/intel_uncore.c
   b7571624fe98 scsi: sg: reset 'res_in_use' after unlinking reserved array
   a4075bbb67b9 scsi: sg: protect accesses to 'reserved' page array
   823086b057aa arm64: fpsimd: Prevent registers leaking across exec
   218720fe5939 x86/io: Add "memory" clobber to insb/insw/insl/outsb/outsw/outsl
   a7a074f3a4d5 arm64: mm: abort uaccess retries upon fatal signal
   da981044d049 lpfc: Fix Device discovery failures during switch reboot test.
   389328ea1379 p54: memset(0) whole array
   5acdbe667cf4 lightnvm: initialize ppa_addr in dev_to_generic_addr()
   d255fffdb532 gcov: support GCC 7.1
   2f3e97a814c8 gcov: add support for gcc version >= 6
   41685ae5cd7b i2c: jz4780: drop superfluous init
   05429bbfd726 btrfs: remove duplicate const specifier
   9a64425945a0 ALSA: au88x0: Fix zero clear of stream->resources
   da8477a6695a scsi: isci: avoid array subscript warning

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 20 ++++++++++----------
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
index b797dff25afd..f808f9bb9c99 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
@@ -11,13 +11,13 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "1ac44e48420edba265d0fa18e4040e6d975776e6"
-SRCREV_meta ?= "8e9afd032ff3be672506a0e5ed51cde9dc45031f"
+SRCREV_machine ?= "7c9e95ef538ddfed606500281e20c42bc1ac1ae0"
+SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.4.85"
+LINUX_VERSION ?= "4.4.87"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
index d10803ae91a3..56dd6f40e895 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.4.85"
+LINUX_VERSION ?= "4.4.87"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_meta ?= "8e9afd032ff3be672506a0e5ed51cde9dc45031f"
+SRCREV_machine ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
index 5634928b9388..9e8f43c3cdb9 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "50253831d9b2d3dfb8e910debda66405cb11900a"
-SRCREV_machine_qemuarm64 ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_machine_qemumips ?= "d49ac34e4781b4bcd4c1728338668bb1fd321f7c"
-SRCREV_machine_qemuppc ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_machine_qemux86 ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_machine_qemux86-64 ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_machine_qemumips64 ?= "310df4a803d8938415e761668426391985193398"
-SRCREV_machine ?= "0327f8213797c4885f86aec26cf55aeef5834180"
-SRCREV_meta ?= "8e9afd032ff3be672506a0e5ed51cde9dc45031f"
+SRCREV_machine_qemuarm ?= "799a97a6f555d98479a55d92e580d91e6f621118"
+SRCREV_machine_qemuarm64 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine_qemumips ?= "18ad0e32668a585380b7f48b5dacd288b0c882d3"
+SRCREV_machine_qemuppc ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine_qemux86 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine_qemux86-64 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine_qemumips64 ?= "1b88be0ada672b2b74221d9a810d3072cb92cf37"
+SRCREV_machine ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.4.85"
+LINUX_VERSION ?= "4.4.87"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

[PATCH 5/9] linux-yocto/4.12: integrate aufs4 core support

[Bruce Ashfield]

The aufs4 now has a 4.12 port, so we can integrate it into the
reference kernel and stay consistent with previous releases.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 18 +++++++++---------
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index f19e1248a90a..491e5b05a23a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -11,8 +11,8 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
+SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index fa3cd2075b8f..05debd338b99 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -9,8 +9,8 @@ LINUX_VERSION ?= "4.12.12"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
+SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index e9838247f45e..d060e2496b8d 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -11,15 +11,15 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "1f5c932260cac2118d256d38b475a2811a8551e5"
-SRCREV_machine_qemuarm64 ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_machine_qemumips ?= "a9f98cc2715a65537877c86808a101429028d48b"
-SRCREV_machine_qemuppc ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_machine_qemux86 ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_machine_qemux86-64 ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_machine_qemumips64 ?= "1863c93b44aeb6badb4993fd9a6ab3d360bf30d1"
-SRCREV_machine ?= "873830670b1af7765428166db40d413018c40e28"
-SRCREV_meta ?= "4fdd56fe602ceb2690407df44283e45ff1c9cd0e"
+SRCREV_machine_qemuarm ?= "42a4ca618610964560fcf6e4b6d7540f5449e992"
+SRCREV_machine_qemuarm64 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine_qemumips ?= "9252e9261b0a606df2f3f49004c23f8a110962ad"
+SRCREV_machine_qemuppc ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine_qemux86 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine_qemux86-64 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine_qemumips64 ?= "bbcf4a8ae8af56687938a7412a9da92f4d1b6552"
+SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
-- 
2.5.0

[PATCH 6/9] linux-yocto/4.10: bluetooth: CVE-2017-1000251

[Bruce Ashfield]

Integrating the following commit:

[
    commit 16de0149674ed12d983b77a453852ac2e64584b4
    Author: Ben Seri <ben@armis.com>
    Date:   Sat Sep 9 23:15:59 2017 +0200

    Bluetooth: Properly check L2CAP config option output buffer length

    Validate the output buffer length for L2CAP config requests and
    responses to avoid overflowing the stack buffer used for building the
    option blocks.

    Cc: stable@vger.kernel.org
    Signed-off-by: Ben Seri <ben@armis.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.10.bb      | 18 +++++++++---------
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
index 17d819153e58..f93d9530ebc5 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb
@@ -11,8 +11,8 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_meta ?= "ba11a3e8f1bc465c9de3cf00e8e60437db60e886"
+SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_meta ?= "40ee48ac099c04f60d2c132031d9625a4e0c4c9e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.10.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.10;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
index 7730da60fa62..31396ab3032e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb
@@ -9,8 +9,8 @@ LINUX_VERSION ?= "4.10.17"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_meta ?= "ba11a3e8f1bc465c9de3cf00e8e60437db60e886"
+SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_meta ?= "40ee48ac099c04f60d2c132031d9625a4e0c4c9e"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.10.bb b/meta/recipes-kernel/linux/linux-yocto_4.10.bb
index 6e5c726b336e..7fcc753a705c 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.10.bb
@@ -11,15 +11,15 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "97253eca8592c9cba7c7665277e1118b048b9639"
-SRCREV_machine_qemuarm64 ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_machine_qemumips ?= "52e935b59800868731e7620caf49cc257f1b9946"
-SRCREV_machine_qemuppc ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_machine_qemux86 ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_machine_qemux86-64 ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_machine_qemumips64 ?= "7b6d7feb4b0143d6f9146784f6072ffd171dd7ba"
-SRCREV_machine ?= "f4ba3db6e599ed41d1c676f9086ad8b97fd55046"
-SRCREV_meta ?= "ba11a3e8f1bc465c9de3cf00e8e60437db60e886"
+SRCREV_machine_qemuarm ?= "ae12e19cecc19af66f64a50538909cb1cad185f9"
+SRCREV_machine_qemuarm64 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_machine_qemumips ?= "b71b80fd679a17dfb4f73b352263c49273f721d4"
+SRCREV_machine_qemuppc ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_machine_qemux86 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_machine_qemux86-64 ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_machine_qemumips64 ?= "8bb135e71037c46175bbcc7acf387309b2e17133"
+SRCREV_machine ?= "c1d8c4408b8aedd88eeb6ccc89ce834dd41b3f09"
+SRCREV_meta ?= "40ee48ac099c04f60d2c132031d9625a4e0c4c9e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.10.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.10;destsuffix=${KMETA}"
-- 
2.5.0

[PATCH 7/9] linux-yocto/4.12: bluetooth: CVE-2017-1000251

[Bruce Ashfield]

Integrating the following commit:

[
    commit 16de0149674ed12d983b77a453852ac2e64584b4
    Author: Ben Seri <ben@armis.com>
    Date:   Sat Sep 9 23:15:59 2017 +0200

    Bluetooth: Properly check L2CAP config option output buffer length

    Validate the output buffer length for L2CAP config requests and
    responses to avoid overflowing the stack buffer used for building the
    option blocks.

    Cc: stable@vger.kernel.org
    Signed-off-by: Ben Seri <ben@armis.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 16 ++++++++--------
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index 491e5b05a23a..c49a9340f8e2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine ?= "16de0149674ed12d983b77a453852ac2e64584b4"
 SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index 05debd338b99..efd876aee5ef 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.12.12"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine ?= "16de0149674ed12d983b77a453852ac2e64584b4"
 SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index d060e2496b8d..a2624090d3f8 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -11,14 +11,14 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "42a4ca618610964560fcf6e4b6d7540f5449e992"
-SRCREV_machine_qemuarm64 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
-SRCREV_machine_qemumips ?= "9252e9261b0a606df2f3f49004c23f8a110962ad"
-SRCREV_machine_qemuppc ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
-SRCREV_machine_qemux86 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
-SRCREV_machine_qemux86-64 ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
-SRCREV_machine_qemumips64 ?= "bbcf4a8ae8af56687938a7412a9da92f4d1b6552"
-SRCREV_machine ?= "c86fccf85be960294703ca9882dde9ee62aaa9e4"
+SRCREV_machine_qemuarm ?= "67b62d8d7bd9f19f0f4fad044787d947ebc4ec25"
+SRCREV_machine_qemuarm64 ?= "16de0149674ed12d983b77a453852ac2e64584b4"
+SRCREV_machine_qemumips ?= "371926551d44c140a0fb869cec34762b40bdf1a6"
+SRCREV_machine_qemuppc ?= "16de0149674ed12d983b77a453852ac2e64584b4"
+SRCREV_machine_qemux86 ?= "16de0149674ed12d983b77a453852ac2e64584b4"
+SRCREV_machine_qemux86-64 ?= "16de0149674ed12d983b77a453852ac2e64584b4"
+SRCREV_machine_qemumips64 ?= "9d63d9c11c44ceabd452d7ee49cf55a88c39383f"
+SRCREV_machine ?= "16de0149674ed12d983b77a453852ac2e64584b4"
 SRCREV_meta ?= "eda4d18ce4b259c84ccd5c249c3dc5958c16928c"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \
-- 
2.5.0

[PATCH 8/9] linux-yocto/4.9: bluetooth: CVE-2017-1000251

[Bruce Ashfield]

Integrating the following commit:

[
    commit 16de0149674ed12d983b77a453852ac2e64584b4
    Author: Ben Seri <ben@armis.com>
    Date:   Sat Sep 9 23:15:59 2017 +0200

    Bluetooth: Properly check L2CAP config option output buffer length

    Validate the output buffer length for L2CAP config requests and
    responses to avoid overflowing the stack buffer used for building the
    option blocks.

    Cc: stable@vger.kernel.org
    Signed-off-by: Ben Seri <ben@armis.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb      | 16 ++++++++--------
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index 23c445a814af..6734dc0d05e2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "1e3f9281ed3043b83d31a3f3dfd28cfb0343873f"
+SRCREV_machine ?= "0817a7b3a853d1bdd3b87a2654ed2ee62f624806"
 SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index 0c2ff0acb272..e0c523661883 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.9.49"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
 SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
index dbb5d54117f2..dbe40a338d88 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
@@ -11,14 +11,14 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "072093c81a9329cec188905dfadb19c983be14f7"
-SRCREV_machine_qemuarm64 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
-SRCREV_machine_qemumips ?= "0c66ebad24541c7673620ca433cd8478e5d06e3b"
-SRCREV_machine_qemuppc ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
-SRCREV_machine_qemux86 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
-SRCREV_machine_qemux86-64 ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
-SRCREV_machine_qemumips64 ?= "6ac61462925ac9d6f668286bc29ee54f05e8f5e9"
-SRCREV_machine ?= "0a2c7ae3c42cd9009df2df20afd2df78332c3ae3"
+SRCREV_machine_qemuarm ?= "8caa35a74753d45178720933f03d8d5150a8ff17"
+SRCREV_machine_qemuarm64 ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
+SRCREV_machine_qemumips ?= "fc2a3b9f932779fdf053675a5a73e8f9917507a5"
+SRCREV_machine_qemuppc ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
+SRCREV_machine_qemux86 ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
+SRCREV_machine_qemux86-64 ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
+SRCREV_machine_qemumips64 ?= "aee63978005c04ea853099764acaa08130e65554"
+SRCREV_machine ?= "480ee599fb8df712c10dcf4b7aa6398b79f7d404"
 SRCREV_meta ?= "6acae6f7200af17b3c2be5ecab2cffdc59a02b35"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.9.git;name=machine;branch=${KBRANCH}; \
-- 
2.5.0

[PATCH 9/9] linux-yocto/4.4: bluetooth: CVE-2017-1000251

[Bruce Ashfield]

Integrating the following commit:

[
    commit 16de0149674ed12d983b77a453852ac2e64584b4
    Author: Ben Seri <ben@armis.com>
    Date:   Sat Sep 9 23:15:59 2017 +0200

    Bluetooth: Properly check L2CAP config option output buffer length

    Validate the output buffer length for L2CAP config requests and
    responses to avoid overflowing the stack buffer used for building the
    option blocks.

    Cc: stable@vger.kernel.org
    Signed-off-by: Ben Seri <ben@armis.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 16 ++++++++--------
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
index f808f9bb9c99..25d88833a943 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
@@ -11,7 +11,7 @@ python () {
         raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "7c9e95ef538ddfed606500281e20c42bc1ac1ae0"
+SRCREV_machine ?= "1e691db7af642fff0222a1f1d1e9043c172699d5"
 SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
index 56dd6f40e895..50b9a56a005a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.4.87"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
 SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
index 9e8f43c3cdb9..d300e69489c5 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
@@ -11,14 +11,14 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "799a97a6f555d98479a55d92e580d91e6f621118"
-SRCREV_machine_qemuarm64 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
-SRCREV_machine_qemumips ?= "18ad0e32668a585380b7f48b5dacd288b0c882d3"
-SRCREV_machine_qemuppc ?= "7078ebf077771189f5da4b676f70dddc92abba42"
-SRCREV_machine_qemux86 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
-SRCREV_machine_qemux86-64 ?= "7078ebf077771189f5da4b676f70dddc92abba42"
-SRCREV_machine_qemumips64 ?= "1b88be0ada672b2b74221d9a810d3072cb92cf37"
-SRCREV_machine ?= "7078ebf077771189f5da4b676f70dddc92abba42"
+SRCREV_machine_qemuarm ?= "840e2c02dde98ee9c584cacdd5bb0812e9dcd016"
+SRCREV_machine_qemuarm64 ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
+SRCREV_machine_qemumips ?= "27a547fe77b05ae63c3b973a029c3933ef62c164"
+SRCREV_machine_qemuppc ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
+SRCREV_machine_qemux86 ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
+SRCREV_machine_qemux86-64 ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
+SRCREV_machine_qemumips64 ?= "7e333c223b568704cc3303b2e922ff85a2a8f7ef"
+SRCREV_machine ?= "b71c7b786aed26c0a1e4eca66f1d874ec017d699"
 SRCREV_meta ?= "804d2b3164ec25ed519fd695de9aa0908460c92e"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; \
-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

This is the latest consolidated kernel pull request. It contains -stable updates,
the kernel-devsrc re-work, and a libc-headers version bump.

The -stable updates are routine, and are required to pick up the latest CVE and
bug fixes from korg.

The kernel-devsrc re-structure has already gone through two revisions, and this
v3 of that patch addresses mips + powerpc + ARM issues that were found during
the on target kernel module compilation testing.

There's one minor fix for kernel class handling of crtsaveres.o, and that same fix
was required for kernel-devsrc.

And finally, there is also have a libc-headers version bump to deal with a
regression introduced in the 4.15 kernel uapi headers. This was picked up due
to the breakage of several packages, and has since been nominated for -stable
inclusion. Patching libc-headers is a last resort, so instead I've tracked the
-stable version to pick up the change. All the details are in the patches
commit log:

--->--->--->--->--->--->--->
   Subject: [PATCH 2/9] linux-libc-headers: update to 4.15.7

   While we don't normally follow all the -stable updates for libc-headers, there
   was one userspace header that was broken in the 4.15 cycle, and it has now
   been fixed in -stable.

   The offending header breaks the build for several packages, so we update to
   pick up this change:

      Author: Hauke Mehrtens <hauke@hauke-m.de>
      Date:   Mon Feb 12 23:59:51 2018 +0100

          uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define

          commit da360299b6734135a5f66d7db458dcc7801c826a upstream.

          This fixes a compile problem of some user space applications by not
          including linux/libc-compat.h in uapi/if_ether.h.

          linux/libc-compat.h checks which "features" the header files, included
          from the libc, provide to make the Linux kernel uapi header files only
             provide no conflicting structures and enums. If a user application mixes
          kernel headers and libc headers it could happen that linux/libc-compat.h
          gets included too early where not all other libc headers are included
          yet. Then the linux/libc-compat.h would not prevent all the
          redefinitions and we run into compile problems.
          This patch removes the include of linux/libc-compat.h from
          uapi/if_ether.h to fix the recently introduced case, but not all as this
          is more or less impossible.

          It is no problem to do the check directly in the if_ether.h file and not
          in libc-compat.h as this does not need any fancy glibc header detection
          as glibc never provided struct ethhdr and should define
          __UAPI_DEF_ETHHDR by them self when they will provide this.

          The following test program did not compile correctly any more:

          #include <linux/if_ether.h>
          #include <netinet/in.h>
          #include <linux/in.h>

          int main(void)
          {
              return 0;
          }

          Fixes: 6926e041a892 ("uapi/if_ether.h: prevent redefinition of struct ethhdr")
          Reported-by: Guillaume Nault <g.nault@alphalink.fr>
          Cc: <stable@vger.kernel.org> # 4.15
          Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
          Signed-off-by: David S. Miller <davem@davemloft.net>
          Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

   We also add a new muslc patch to adjust the ethhdr change in the uapi. As is
   suggested in the kernel commit, we can protect musl directly in if_ether itself.

   Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
--->--->--->--->--->--->--->

Cheers,

Bruce

The following changes since commit e5f258cecef6c51a4d7ebeedbaa29d2126e566e3:

  util-linux: add taskset to alternatives list (2018-03-06 06:43:11 -0800)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-devsrc: restructure for out of tree (and on target) module
    builds
  linux-libc-headers: update to 4.15.7
  linux-yocto/4.15: update to v4.15.7
  linux-yocto/4.14: update to v4.14.24
  linux-yocto/4.12: fix aufs compile warning
  linux-yocto/4.12: memleak and build warning fixes
  linux-yocto: aufs and systemtap
  linux-yocto/4.12: warning: drm/i915/cfl: Coffee Lake works on Kaby
    Lake PCH
  kernel: make copying of crtsavres.o conditional

 meta/classes/kernel.bbclass                        |   6 +-
 ...move-muslc-ethhdr-protection-to-uapi-file.patch |  30 ++++
 ...eaders_4.15.bb => linux-libc-headers_4.15.7.bb} |   6 +-
 meta/recipes-kernel/linux/kernel-devsrc.bb         | 192 ++++++++++++++++-----
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |   4 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   |   6 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb   |   6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |   4 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb |   6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb |   6 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      |  18 +-
 meta/recipes-kernel/linux/linux-yocto_4.14.bb      |  20 +--
 meta/recipes-kernel/linux/linux-yocto_4.15.bb      |  20 +--
 13 files changed, 235 insertions(+), 89 deletions(-)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.15.bb => linux-libc-headers_4.15.7.bb} (62%)

-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here is my queue of changes for kernel-yocto.

These are mainly -stable updates, but contained in those updates are the gcc8
fixes that we need to get gcc8 working for the reference kernels in master.

I've also fixed a couple of issues that were found in the last
4.12 update.

Note: I'll be dropping 4.12 and 4.15 from master in my next set of
      updates, keeping 4.14 and moving to a 4.17+ kernel as the latest.

There's also a minor kern-tools fix that was sent in my direction.

And finally we were seeing intermittent failures when configuring linux-yocto
for 4.16+. The failures were sometimes obvious (configure failure) or not so
obvious (dropped options). When I dug into the problem, I found that 4.16+ has
new checks for x86 that require native binaries, and the compiler that will be
used to build the kernel. The fix was to put the required dependencies on the
kernel_configme task for linux-yocto (since it runs before do_configure, it
doesn't have the default kernel DEPENDS in place), and to ensure that CC= and
HOSTCC are set in the environment for the configure invokations.

Cheers,

Bruce

The following changes since commit 1c7ad49bfd3e60c44281a8f49d69f4b96c359703:

  bitbake: bitbake: Update version to post release 1.39 (2018-06-06 13:35:15 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  linux-yocto/4.14: update to v4.14.30
  linux-yocto/4.15: update to v4.15.18
  linux-yocto/4.14/4.15: gcc8 fixes
  linux-yocto/4.12: fix ppc cryptodev build
  kernel: specify dependencies for compilation for config tasks
  kern-tools: avoid merge_config concatenation issues
  linux-yocto/4.12: gcc8 + platform support
  linux-yocto: add kernel sample configuration fragment
  linux-yocto/4.14: update to v4.14.48

 meta/classes/kernel-yocto.bbclass                    |  5 ++++-
 meta/classes/kernel.bbclass                          |  2 +-
 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb     |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb     |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb     |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.12.bb        | 16 ++++++++--------
 meta/recipes-kernel/linux/linux-yocto_4.14.bb        | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.15.bb        | 20 ++++++++++----------
 12 files changed, 48 insertions(+), 45 deletions(-)

-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

I've kept the v5.4 content changes, as well as the kernel version default
changes out of this series and instead focused it on the collection of
kernel-yocto and kern-tools tweaks that I've gethered over the past few
weeks.

I have Martin's gold linker fixes included, as well as the re-org'ing of
the linux-yocto tasks that Paul Barker did to make it usable as a single
inherit of the bbclass.

I also have a defconfig detection fix included that was sent to the list.

I was able to confirm that my configuration was the same with this series
enabled, and I was able to boot.

That being said, I'll keep my eye out for any AB fallout and will continue
some more build locally .. but I wanted to get this out today as promised.

Cheers,

Bruce

The following changes since commit 3c6978c8db59f152693f9fae65dbab13ecfcaad4:

  kernel-yocto.bbclass: export LD in the environment used by kconf_check (2020-02-04 15:56:29 +0000)

are available in the Git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (2):
  kern-tools: tweak symbol_why to be python safe
  kern-tools: integrate merge_config fix for gold linker

Gavin Li (1):
  kernel-yocto: fix defconfig detection in find_sccs()

Martin Jansa (3):
  kern-tools-native: use more common S value and oe_runmake
  kernel-yocto.bbclass: set KERNEL_LD also for merge_config.sh
  kernel-yocto.bbclass: do_kernel_configme: don't use +errexit,
    merge_config_build.log and fail when /.config wasn't created

Paul Barker (3):
  kernel-yocto: Move defaults and tasks from linux-yocto.inc into
    bbclass
  kernel-yocto: Drop setting of unused variables in do_kernel_metadata
  kernel-yocto: Only override CONFIG_LOCALVERSION if
    LINUX_VERSION_EXTENSION is set

 meta/classes/kernel-yocto.bbclass             | 43 +++++++++++++------
 .../kern-tools/kern-tools-native_git.bb       | 13 +++---
 meta/recipes-kernel/linux/linux-yocto.inc     | 21 ---------
 3 files changed, 37 insertions(+), 40 deletions(-)

-- 
2.19.1

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

Hi Bruce,

On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Hi all,
> 
> I've kept the v5.4 content changes, as well as the kernel version
> default
> changes out of this series and instead focused it on the collection
> of
> kernel-yocto and kern-tools tweaks that I've gethered over the past
> few
> weeks.
> 
> I have Martin's gold linker fixes included, as well as the re-org'ing 
> of
> the linux-yocto tasks that Paul Barker did to make it usable as a
> single
> inherit of the bbclass.
> 
> I also have a defconfig detection fix included that was sent to the
> list.
> 
> I was able to confirm that my configuration was the same with this
> series
> enabled, and I was able to boot.
> 
> That being said, I'll keep my eye out for any AB fallout and will
> continue
> some more build locally .. but I wanted to get this out today as
> promised.

qemuarm64 seems unhappy:

https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/1524

(the builds on the arm native machine also failed but it looks related)

I think everything else passed testing for this series.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Thu, Feb 6, 2020 at 4:03 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > I've kept the v5.4 content changes, as well as the kernel version
> > default
> > changes out of this series and instead focused it on the collection
> > of
> > kernel-yocto and kern-tools tweaks that I've gethered over the past
> > few
> > weeks.
> >
> > I have Martin's gold linker fixes included, as well as the re-org'ing
> > of
> > the linux-yocto tasks that Paul Barker did to make it usable as a
> > single
> > inherit of the bbclass.
> >
> > I also have a defconfig detection fix included that was sent to the
> > list.
> >
> > I was able to confirm that my configuration was the same with this
> > series
> > enabled, and I was able to boot.
> >
> > That being said, I'll keep my eye out for any AB fallout and will
> > continue
> > some more build locally .. but I wanted to get this out today as
> > promised.
>
> qemuarm64 seems unhappy:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/1524

Bugger. I'll fix and resend a v2 pull request.

Bruce

>
> (the builds on the arm native machine also failed but it looks related)
>
> I think everything else passed testing for this series.
>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here are the gathered changes for our active lnux-yocto references, as well
as some pre-work for moving to 5.13+ as the reference. I've also included
a patch to add some BSP/SRC_URI information after the kernel meta data has
been gathered .. this was requested just before the previous release, and
I finally got time to pull something together.

No big surprises and everything looked fine locally, and my AB run was
clean (outside of an arm64 ptest timeout that doesn't look related).

Bruce

The following changes since commit fb26a7c9b86488f46aef707c7836c2cd406d9b8a:

  meson: update patch status (2021-05-17 09:53:15 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-yocto: provide debug / summary information for metadata
  linux-yocto/5.10: update to v5.10.35
  linux-yocto/5.4: update to v5.4.117
  linux-yocto/5.10: ktypes/standard: disable obsolete crypto options by
    default
  linux-yocto/5.10: update to v5.10.36
  linux-yocto/5.4: update to v5.4.118
  linux-yocto/5.10: update to v5.10.37
  linux-yocto/5.4: update to v5.4.119
  kernel-devsrc: adjust NM and OBJTOOL variables for target

 meta/classes/kernel-yocto.bbclass             | 17 +++++++++++++
 meta/recipes-kernel/linux/kernel-devsrc.bb    |  2 ++
 .../linux/linux-yocto-rt_5.10.bb              |  6 ++---
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.10.bb            |  8 +++----
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++++++---------
 8 files changed, 56 insertions(+), 37 deletions(-)

-- 
2.19.1

[PATCH 0/9] kernel-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's the next set of -stable updates to the active reference kernels.
I also have updates back to 5.4 that I'll send to the various stable
branches shortly.

I also have a couple of kern-tools fixes. One to solve a problem reported
on the list about some directory structures (typically created from KAS)
to break the meta-data phase of the kernel build. I've fixed that issue,
then fixed the other regressions that fix caused, and have everything
passing sanity. There shouldn't be any fallout, but I'll be keeping a
close eye on things.

I also have Khem's MDIO configuration change in the queue, along with
a previously hidden kern-tools feature that allows it to not warn if
something is 'enabled' (y or m).

Cheers,

Bruce

The following changes since commit fa86bfd3617b54dbf7e44093ae0e6f35538bdabc:

  diffoscope: upgrade 220 -> 221 (2022-09-17 07:47:08 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (8):
  linux-yocto/5.15: update to v5.15.63
  linux-yocto/5.19: update to v5.19.5
  linux-yocto/5.19: update to v5.19.7
  linux-yocto/5.15: update to v5.15.65
  kern-tools: fix queue processing in relative TOPDIR configurations
  kern-tools: allow 'y' or 'm' to avoid config audit warnings
  linux-yocto/5.19: update to v5.19.9
  linux-yocto/5.15: update to v5.15.68

Khem Raj (1):
  linux-yocto: Enable mdio for qemu

 .../kern-tools/kern-tools-native_git.bb       |  2 +-
 .../linux/linux-yocto-rt_5.15.bb              |  6 ++--
 .../linux/linux-yocto-rt_5.19.bb              |  6 ++--
 .../linux/linux-yocto-tiny_5.15.bb            |  6 ++--
 .../linux/linux-yocto-tiny_5.19.bb            |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 ++++++++---------
 meta/recipes-kernel/linux/linux-yocto_5.19.bb | 28 +++++++++----------
 7 files changed, 40 insertions(+), 40 deletions(-)

-- 
2.19.1

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
> 
> I also have a couple of kern-tools fixes. One to solve a problem reported
> on the list about some directory structures (typically created from KAS)
> to break the meta-data phase of the kernel build. I've fixed that issue,
> then fixed the other regressions that fix caused, and have everything
> passing sanity. There shouldn't be any fallout, but I'll be keeping a
> close eye on things.
> 
> I also have Khem's MDIO configuration change in the queue, along with
> a previously hidden kern-tools feature that allows it to not warn if
> something is 'enabled' (y or m).

Thanks, those sound like good fixes. Unfortunately this showed an issue
with TMPDIR in perf somewhere in testing:

Reproducible error:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/1570

and warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/5871

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5832
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/5862
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6153
https://autobuilder.yoctoproject.org/typhoon/#/builders/131/builds/1255
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/5848
https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/5910
and more, seems to be on all arches.

Diffoscope output is here:
http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220919-7ypfzvog/packages/diff-html/

which shows an issue in debug symbols and it looks to be python
related:

PYTHON·BUILD_STR('/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleA/tmp/work/qemux86_64-poky-linux/perf/1.0-r9/recipe-sysroot-native/usr/bin/python3-native/python3')

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Richard,
> 
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
> 
> I also have a couple of kern-tools fixes. One to solve a problem reported
> on the list about some directory structures (typically created from KAS)
> to break the meta-data phase of the kernel build. I've fixed that issue,
> then fixed the other regressions that fix caused, and have everything
> passing sanity. There shouldn't be any fallout, but I'll be keeping a
> close eye on things.
> 
> I also have Khem's MDIO configuration change in the queue, along with
> a previously hidden kern-tools feature that allows it to not warn if
> something is 'enabled' (y or m).

I have a patch in master-next I'm testing for the perf issue. On
testing that, this set of config warnings became clear for poky-tiny:

https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Richard,
> >
> > Here's the next set of -stable updates to the active reference kernels.
> > I also have updates back to 5.4 that I'll send to the various stable
> > branches shortly.
> >
> > I also have a couple of kern-tools fixes. One to solve a problem reported
> > on the list about some directory structures (typically created from KAS)
> > to break the meta-data phase of the kernel build. I've fixed that issue,
> > then fixed the other regressions that fix caused, and have everything
> > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > close eye on things.
> >
> > I also have Khem's MDIO configuration change in the queue, along with
> > a previously hidden kern-tools feature that allows it to not warn if
> > something is 'enabled' (y or m).
>
> I have a patch in master-next I'm testing for the perf issue. On
> testing that, this set of config warnings became clear for poky-tiny:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157

That's very likely due to this change from Andrei :
https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c

Was that a qemuarm64 configuration ?

Bruce


>
> Cheers,
>
> Richard



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > 
> > > Richard,
> > > 
> > > Here's the next set of -stable updates to the active reference kernels.
> > > I also have updates back to 5.4 that I'll send to the various stable
> > > branches shortly.
> > > 
> > > I also have a couple of kern-tools fixes. One to solve a problem reported
> > > on the list about some directory structures (typically created from KAS)
> > > to break the meta-data phase of the kernel build. I've fixed that issue,
> > > then fixed the other regressions that fix caused, and have everything
> > > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > > close eye on things.
> > > 
> > > I also have Khem's MDIO configuration change in the queue, along with
> > > a previously hidden kern-tools feature that allows it to not warn if
> > > something is 'enabled' (y or m).
> > 
> > I have a patch in master-next I'm testing for the perf issue. On
> > testing that, this set of config warnings became clear for poky-tiny:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157
> 
> That's very likely due to this change from Andrei :
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c
> 
> Was that a qemuarm64 configuration ?

It warned on qemux86:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/12/logs/stdio

qemux86-64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/16/logs/stdio

qemuarm64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/18/logs/stdio

so on all the arches we test for tiny.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Tue, Sep 20, 2022 at 8:55 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> > On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > >
> > > > Richard,
> > > >
> > > > Here's the next set of -stable updates to the active reference kernels.
> > > > I also have updates back to 5.4 that I'll send to the various stable
> > > > branches shortly.
> > > >
> > > > I also have a couple of kern-tools fixes. One to solve a problem reported
> > > > on the list about some directory structures (typically created from KAS)
> > > > to break the meta-data phase of the kernel build. I've fixed that issue,
> > > > then fixed the other regressions that fix caused, and have everything
> > > > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > > > close eye on things.
> > > >
> > > > I also have Khem's MDIO configuration change in the queue, along with
> > > > a previously hidden kern-tools feature that allows it to not warn if
> > > > something is 'enabled' (y or m).
> > >
> > > I have a patch in master-next I'm testing for the perf issue. On
> > > testing that, this set of config warnings became clear for poky-tiny:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157
> >
> > That's very likely due to this change from Andrei :
> > https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c
> >
> > Was that a qemuarm64 configuration ?
>
> It warned on qemux86:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/12/logs/stdio
>
> qemux86-64:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/16/logs/stdio
>
> qemuarm64:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/18/logs/stdio
>
> so on all the arches we test for tiny.
>

I've reproduced it locally .. the fix is a bit fiddly. I'm going to
try some things tonight / tomorrow and will send a patch that goes
onto the end of the series to fix it up.

Bruce

> Cheers,
>
> Richard



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II