Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-21 Thread Tom Gall 

> On Oct 21, 2017, at 2:25 AM, Greg Kroah-Hartman  
> wrote:
> 
> On Fri, Oct 20, 2017 at 11:54:38AM -0500, Tom Gall wrote:
>> On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
 fcntl36 and raw_skew we’ll looking into.
 
 ltp-timers-tests:
   * leapsec_timer
   * runltp_timers
 
   * test src: git://github.com/linux-test-project/ltp.git
 
 This one has been working and just failed with this RC cycle. It’s only 
 failing on 32 bit arm.
 
 Needs to be looked into.
>>> 
>>> When you say "Needs to be looked into", does that mean that you are
>>> pointing this out for someone else to do this (i.e. help, someone look
>>> at this!), or are you going to be working to figure it out?
>> 
>> Help is always great. We've got it covered.
>> 
>> One of the team that works on this board has been looking into it.
>> 
>> As of this second, and looking within the context of 4.4, 4.9 and mainline 
>> data
>> what we're looking at is intermitted failures involving raw_skew from
>> kselftest and leapsec_timer
>> from ltp_timers that is present across all those 3 kernel version and
>> their respective streams.
>> (by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)
>> 
>> As such we can rule these out detecting a regression in the new RC
>> patches. Likely it's board
>> specific.
> 
> Side note, your use of \n is still really odd.  I strongly recommend
> getting a decent email client, or an sane editor that knows what to do
> here….

That email client has been sacked.

> Anyway, if you have board-specific issues, that are not -rc issues, can
> you say so really obviously so I don't worry that I broke something?
> Otherwise it's pretty annoying, as your email implies that I did
> something wrong, and only a few emails in the thread later will it come
> out that this is flaky hardware/tests so there's nothing to worry about.

Reports are pretty new & shiny yet so yes I’m over explaining the logic. 
To me, showing your work applies to other places besides math.

> The kernel.ci reports are a bit like this, I glance at them and only
> worry if the reporter tells me to worry.  Should I do the same thing
> here as well?  When can these tests/reports start to be trusted?

Exactly and no surprise as number of those involved in all of this helped 
get kernelci off the ground. 

Our aim is to have quick summaries either appended with the gory 
details or pointers to it for those that care.

For me the x86 and arm64 results are trustable. We’re working on
getting 4.14-rc runs clean and then we’ll get after the ‘known
errors with 4.4 and 4.9 as well.

32 bit arm results are a bit new/shiny yet.  That’s where I’m most
skeptical when something pops up.

Hope the perspective helps.

> thanks,
> 
> greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-21 Thread Tom Gall 

> On Oct 21, 2017, at 2:25 AM, Greg Kroah-Hartman  
> wrote:
> 
> On Fri, Oct 20, 2017 at 11:54:38AM -0500, Tom Gall wrote:
>> On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
 fcntl36 and raw_skew we’ll looking into.
 
 ltp-timers-tests:
   * leapsec_timer
   * runltp_timers
 
   * test src: git://github.com/linux-test-project/ltp.git
 
 This one has been working and just failed with this RC cycle. It’s only 
 failing on 32 bit arm.
 
 Needs to be looked into.
>>> 
>>> When you say "Needs to be looked into", does that mean that you are
>>> pointing this out for someone else to do this (i.e. help, someone look
>>> at this!), or are you going to be working to figure it out?
>> 
>> Help is always great. We've got it covered.
>> 
>> One of the team that works on this board has been looking into it.
>> 
>> As of this second, and looking within the context of 4.4, 4.9 and mainline 
>> data
>> what we're looking at is intermitted failures involving raw_skew from
>> kselftest and leapsec_timer
>> from ltp_timers that is present across all those 3 kernel version and
>> their respective streams.
>> (by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)
>> 
>> As such we can rule these out detecting a regression in the new RC
>> patches. Likely it's board
>> specific.
> 
> Side note, your use of \n is still really odd.  I strongly recommend
> getting a decent email client, or an sane editor that knows what to do
> here….

That email client has been sacked.

> Anyway, if you have board-specific issues, that are not -rc issues, can
> you say so really obviously so I don't worry that I broke something?
> Otherwise it's pretty annoying, as your email implies that I did
> something wrong, and only a few emails in the thread later will it come
> out that this is flaky hardware/tests so there's nothing to worry about.

Reports are pretty new & shiny yet so yes I’m over explaining the logic. 
To me, showing your work applies to other places besides math.

> The kernel.ci reports are a bit like this, I glance at them and only
> worry if the reporter tells me to worry.  Should I do the same thing
> here as well?  When can these tests/reports start to be trusted?

Exactly and no surprise as number of those involved in all of this helped 
get kernelci off the ground. 

Our aim is to have quick summaries either appended with the gory 
details or pointers to it for those that care.

For me the x86 and arm64 results are trustable. We’re working on
getting 4.14-rc runs clean and then we’ll get after the ‘known
errors with 4.4 and 4.9 as well.

32 bit arm results are a bit new/shiny yet.  That’s where I’m most
skeptical when something pops up.

Hope the perspective helps.

> thanks,
> 
> greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-21 Thread Greg Kroah-Hartman 
On Fri, Oct 20, 2017 at 11:54:38AM -0500, Tom Gall wrote:
> On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
> >> fcntl36 and raw_skew we’ll looking into.
> >>
> >>  ltp-timers-tests:
> >>* leapsec_timer
> >>* runltp_timers
> >>
> >>* test src: git://github.com/linux-test-project/ltp.git
> >>
> >> This one has been working and just failed with this RC cycle. It’s only 
> >> failing on 32 bit arm.
> >>
> >> Needs to be looked into.
> >
> > When you say "Needs to be looked into", does that mean that you are
> > pointing this out for someone else to do this (i.e. help, someone look
> > at this!), or are you going to be working to figure it out?
> 
> Help is always great. We've got it covered.
> 
> One of the team that works on this board has been looking into it.
> 
> As of this second, and looking within the context of 4.4, 4.9 and mainline 
> data
> what we're looking at is intermitted failures involving raw_skew from
> kselftest and leapsec_timer
> from ltp_timers that is present across all those 3 kernel version and
> their respective streams.
> (by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)
> 
> As such we can rule these out detecting a regression in the new RC
> patches. Likely it's board
> specific.

Side note, your use of \n is still really odd.  I strongly recommend
getting a decent email client, or an sane editor that knows what to do
here

Anyway, if you have board-specific issues, that are not -rc issues, can
you say so really obviously so I don't worry that I broke something?
Otherwise it's pretty annoying, as your email implies that I did
something wrong, and only a few emails in the thread later will it come
out that this is flaky hardware/tests so there's nothing to worry about.

The kernel.ci reports are a bit like this, I glance at them and only
worry if the reporter tells me to worry.  Should I do the same thing
here as well?  When can these tests/reports start to be trusted?

thanks,

greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-21 Thread Greg Kroah-Hartman 
On Fri, Oct 20, 2017 at 11:54:38AM -0500, Tom Gall wrote:
> On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
> >> fcntl36 and raw_skew we’ll looking into.
> >>
> >>  ltp-timers-tests:
> >>* leapsec_timer
> >>* runltp_timers
> >>
> >>* test src: git://github.com/linux-test-project/ltp.git
> >>
> >> This one has been working and just failed with this RC cycle. It’s only 
> >> failing on 32 bit arm.
> >>
> >> Needs to be looked into.
> >
> > When you say "Needs to be looked into", does that mean that you are
> > pointing this out for someone else to do this (i.e. help, someone look
> > at this!), or are you going to be working to figure it out?
> 
> Help is always great. We've got it covered.
> 
> One of the team that works on this board has been looking into it.
> 
> As of this second, and looking within the context of 4.4, 4.9 and mainline 
> data
> what we're looking at is intermitted failures involving raw_skew from
> kselftest and leapsec_timer
> from ltp_timers that is present across all those 3 kernel version and
> their respective streams.
> (by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)
> 
> As such we can rule these out detecting a regression in the new RC
> patches. Likely it's board
> specific.

Side note, your use of \n is still really odd.  I strongly recommend
getting a decent email client, or an sane editor that knows what to do
here

Anyway, if you have board-specific issues, that are not -rc issues, can
you say so really obviously so I don't worry that I broke something?
Otherwise it's pretty annoying, as your email implies that I did
something wrong, and only a few emails in the thread later will it come
out that this is flaky hardware/tests so there's nothing to worry about.

The kernel.ci reports are a bit like this, I glance at them and only
worry if the reporter tells me to worry.  Should I do the same thing
here as well?  When can these tests/reports start to be trusted?

thanks,

greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Tom Gall 
On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
 wrote:
> On Thu, Oct 19, 2017 at 05:18:38PM -0500, Tom Gall wrote:
>>
>> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman 
>> >  wrote:
>> >
>> > This is the start of the stable review cycle for the 4.4.94 release.
>> > There are 46 patches in this series, all will be posted as a response
>> > to this one.  If anyone has any issues with these being applied, please
>> > let me know.
>> >
>> > Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
>> > Anything received after that time might be too late.
>> >
>> > The whole patch series can be found in one patch at:
>> > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
>> > or in the git tree and branch at:
>> >  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
>> > linux-4.4.y
>> > and the diffstat can be found below.
>> >
>> > thanks,
>> >
>> > greg k-h
>>
>> Results from the Linaro test farm. This report is in two parts. The second 
>> part and reported
>> separately is the HiKey results since there are platform support patches 
>> added to the LTS
>> to make it work.
>>
>> Summary
>> 
>>
>> kernel: 4.4.94-rc1
>> git repo: 
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> git branch: linux-4.4.y
>> git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
>> git describe: v4.4.93-47-gcc1d76b2d639
>> Test details: 
>> https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639
>>
>> Regressions (compared to build v4.4.92-29-g51c43ad676c4)
>> 
>>
>> x15 - arm:
>>  kselftest:
>>* raw_skew
>>
>>* test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz
>>
>>  ltp-syscalls-tests:
>>* fcntl36
>>
>>* test src: git://github.com/linux-test-project/ltp.git
>>
>> fcntl36 and raw_skew we’ll looking into.
>>
>>  ltp-timers-tests:
>>* leapsec_timer
>>* runltp_timers
>>
>>* test src: git://github.com/linux-test-project/ltp.git
>>
>> This one has been working and just failed with this RC cycle. It’s only 
>> failing on 32 bit arm.
>>
>> Needs to be looked into.
>
> When you say "Needs to be looked into", does that mean that you are
> pointing this out for someone else to do this (i.e. help, someone look
> at this!), or are you going to be working to figure it out?

Help is always great. We've got it covered.

One of the team that works on this board has been looking into it.

As of this second, and looking within the context of 4.4, 4.9 and mainline data
what we're looking at is intermitted failures involving raw_skew from
kselftest and leapsec_timer
from ltp_timers that is present across all those 3 kernel version and
their respective streams.
(by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)

As such we can rule these out detecting a regression in the new RC
patches. Likely it's board
specific.

For fcntl36 it's been intermittent only through the series of 4.4
kernels. At the moment we just
have one type of arm 32bit board, so we don't have a history here
where we could refer to and say
fails occasionally on one board but not others. (We'll get there, Rome
wasn't built in a day) At the
time I reported results I couldn't narrow between a board specific
issue, an arch specific issue or
an issue that my have arose due to a bad patch in the RC.

Today however with fcntl36 produced failure for the very first time on
mainline only on X15 which is
a 32 bit arm board.

That should rule out the bad patch scenario in the new RC series.

Having result history you can look back into across multiple versions
and arches is awesome.
Doing all the comparisons, coming at the data from multiple directions
and triple checking to
make sure data is pointing you to reasonable conclusions, that's the fun part.



> thanks,
>
> greg k-h



-- 
Regards,
Tom

Director, Linaro Mobile Group
Linaro.org │ Open source software for ARM SoCs
irc: tgall_foo | skype : tom_gall

"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Tom Gall 
On Fri, Oct 20, 2017 at 1:26 AM, Greg Kroah-Hartman
 wrote:
> On Thu, Oct 19, 2017 at 05:18:38PM -0500, Tom Gall wrote:
>>
>> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman 
>> >  wrote:
>> >
>> > This is the start of the stable review cycle for the 4.4.94 release.
>> > There are 46 patches in this series, all will be posted as a response
>> > to this one.  If anyone has any issues with these being applied, please
>> > let me know.
>> >
>> > Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
>> > Anything received after that time might be too late.
>> >
>> > The whole patch series can be found in one patch at:
>> > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
>> > or in the git tree and branch at:
>> >  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
>> > linux-4.4.y
>> > and the diffstat can be found below.
>> >
>> > thanks,
>> >
>> > greg k-h
>>
>> Results from the Linaro test farm. This report is in two parts. The second 
>> part and reported
>> separately is the HiKey results since there are platform support patches 
>> added to the LTS
>> to make it work.
>>
>> Summary
>> 
>>
>> kernel: 4.4.94-rc1
>> git repo: 
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> git branch: linux-4.4.y
>> git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
>> git describe: v4.4.93-47-gcc1d76b2d639
>> Test details: 
>> https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639
>>
>> Regressions (compared to build v4.4.92-29-g51c43ad676c4)
>> 
>>
>> x15 - arm:
>>  kselftest:
>>* raw_skew
>>
>>* test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz
>>
>>  ltp-syscalls-tests:
>>* fcntl36
>>
>>* test src: git://github.com/linux-test-project/ltp.git
>>
>> fcntl36 and raw_skew we’ll looking into.
>>
>>  ltp-timers-tests:
>>* leapsec_timer
>>* runltp_timers
>>
>>* test src: git://github.com/linux-test-project/ltp.git
>>
>> This one has been working and just failed with this RC cycle. It’s only 
>> failing on 32 bit arm.
>>
>> Needs to be looked into.
>
> When you say "Needs to be looked into", does that mean that you are
> pointing this out for someone else to do this (i.e. help, someone look
> at this!), or are you going to be working to figure it out?

Help is always great. We've got it covered.

One of the team that works on this board has been looking into it.

As of this second, and looking within the context of 4.4, 4.9 and mainline data
what we're looking at is intermitted failures involving raw_skew from
kselftest and leapsec_timer
from ltp_timers that is present across all those 3 kernel version and
their respective streams.
(by stream I mean FOO, FOO-rc1, FOO+1, FOO+1-rc1, etc)

As such we can rule these out detecting a regression in the new RC
patches. Likely it's board
specific.

For fcntl36 it's been intermittent only through the series of 4.4
kernels. At the moment we just
have one type of arm 32bit board, so we don't have a history here
where we could refer to and say
fails occasionally on one board but not others. (We'll get there, Rome
wasn't built in a day) At the
time I reported results I couldn't narrow between a board specific
issue, an arch specific issue or
an issue that my have arose due to a bad patch in the RC.

Today however with fcntl36 produced failure for the very first time on
mainline only on X15 which is
a 32 bit arm board.

That should rule out the bad patch scenario in the new RC series.

Having result history you can look back into across multiple versions
and arches is awesome.
Doing all the comparisons, coming at the data from multiple directions
and triple checking to
make sure data is pointing you to reasonable conclusions, that's the fun part.



> thanks,
>
> greg k-h



-- 
Regards,
Tom

Director, Linaro Mobile Group
Linaro.org │ Open source software for ARM SoCs
irc: tgall_foo | skype : tom_gall

"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Guenter Roeck 

On 10/19/2017 06:48 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.4.94 release.
There are 46 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
Anything received after that time might be too late.




Build results:
total: 145 pass: 145 fail: 0
Qemu test results:
total: 116 pass: 116 fail: 0

Details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Guenter Roeck 

On 10/19/2017 06:48 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.4.94 release.
There are 46 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
Anything received after that time might be too late.




Build results:
total: 145 pass: 145 fail: 0
Qemu test results:
total: 116 pass: 116 fail: 0

Details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Greg Kroah-Hartman 
On Thu, Oct 19, 2017 at 05:18:38PM -0500, Tom Gall wrote:
> 
> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman 
> >  wrote:
> > 
> > This is the start of the stable review cycle for the 4.4.94 release.
> > There are 46 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
> > or in the git tree and branch at:
> >  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> > linux-4.4.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Results from the Linaro test farm. This report is in two parts. The second 
> part and reported 
> separately is the HiKey results since there are platform support patches 
> added to the LTS
> to make it work.
> 
> Summary
> 
> 
> kernel: 4.4.94-rc1
> git repo: 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> git branch: linux-4.4.y
> git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
> git describe: v4.4.93-47-gcc1d76b2d639
> Test details: 
> https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639
> 
> Regressions (compared to build v4.4.92-29-g51c43ad676c4)
> 
> 
> x15 - arm:
>  kselftest:
>* raw_skew
> 
>* test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz
> 
>  ltp-syscalls-tests:
>* fcntl36
> 
>* test src: git://github.com/linux-test-project/ltp.git
> 
> fcntl36 and raw_skew we’ll looking into.
> 
>  ltp-timers-tests:
>* leapsec_timer
>* runltp_timers
> 
>* test src: git://github.com/linux-test-project/ltp.git
> 
> This one has been working and just failed with this RC cycle. It’s only 
> failing on 32 bit arm.
> 
> Needs to be looked into.

When you say "Needs to be looked into", does that mean that you are
pointing this out for someone else to do this (i.e. help, someone look
at this!), or are you going to be working to figure it out?

thanks,

greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-20 Thread Greg Kroah-Hartman 
On Thu, Oct 19, 2017 at 05:18:38PM -0500, Tom Gall wrote:
> 
> > On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman 
> >  wrote:
> > 
> > This is the start of the stable review cycle for the 4.4.94 release.
> > There are 46 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
> > or in the git tree and branch at:
> >  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> > linux-4.4.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Results from the Linaro test farm. This report is in two parts. The second 
> part and reported 
> separately is the HiKey results since there are platform support patches 
> added to the LTS
> to make it work.
> 
> Summary
> 
> 
> kernel: 4.4.94-rc1
> git repo: 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> git branch: linux-4.4.y
> git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
> git describe: v4.4.93-47-gcc1d76b2d639
> Test details: 
> https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639
> 
> Regressions (compared to build v4.4.92-29-g51c43ad676c4)
> 
> 
> x15 - arm:
>  kselftest:
>* raw_skew
> 
>* test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz
> 
>  ltp-syscalls-tests:
>* fcntl36
> 
>* test src: git://github.com/linux-test-project/ltp.git
> 
> fcntl36 and raw_skew we’ll looking into.
> 
>  ltp-timers-tests:
>* leapsec_timer
>* runltp_timers
> 
>* test src: git://github.com/linux-test-project/ltp.git
> 
> This one has been working and just failed with this RC cycle. It’s only 
> failing on 32 bit arm.
> 
> Needs to be looked into.

When you say "Needs to be looked into", does that mean that you are
pointing this out for someone else to do this (i.e. help, someone look
at this!), or are you going to be working to figure it out?

thanks,

greg k-h

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-19 Thread Tom Gall 

> On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman  
> wrote:
> 
> This is the start of the stable review cycle for the 4.4.94 release.
> There are 46 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
> or in the git tree and branch at:
>  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.4.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

Results from the Linaro test farm. This report is in two parts. The second part 
and reported 
separately is the HiKey results since there are platform support patches added 
to the LTS
to make it work.

Summary


kernel: 4.4.94-rc1
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.4.y
git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
git describe: v4.4.93-47-gcc1d76b2d639
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639

Regressions (compared to build v4.4.92-29-g51c43ad676c4)


x15 - arm:
 kselftest:
   * raw_skew

   * test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz

 ltp-syscalls-tests:
   * fcntl36

   * test src: git://github.com/linux-test-project/ltp.git

fcntl36 and raw_skew we’ll looking into.

 ltp-timers-tests:
   * leapsec_timer
   * runltp_timers

   * test src: git://github.com/linux-test-project/ltp.git

This one has been working and just failed with this RC cycle. It’s only failing 
on 32 bit arm.

Needs to be looked into.


Boards, architectures and test suites:
-

juno-r2 - arm64
* boot - pass: 20,
* kselftest - pass: 32, skip: 7, fail: 13 (known failures)
* libhugetlbfs - pass: 90, skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 27, skip: 36, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 59, fail: 2 (known failures)
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 14,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 938, skip: 159, fail: 15 (known failures)
* ltp-timers-tests - pass: 13,

x15 - arm
* boot - pass: 20,
* kselftest - pass: 31, skip: 1, fail: 21 (known failures)
* libhugetlbfs - skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 63, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 60,
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1036, skip: 68, fail: 5 (noted above)
* ltp-timers-tests - pass: 11, fail: 2 (noted above)

dell-poweredge-r200 - x86_64
* boot - pass: 20,
* kselftest - pass: 43, fail: 24
* libhugetlbfs - pass: 76, skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 63, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 1,
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 960, skip: 164, fail: 13 (known failures)
* ltp-timers-tests - pass: 13,



Summary


kernel: 4.4.94-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git tag: 4.4.94-rc1-hikey-20171019
git commit: 64eacf43d6ff4c9320737af2fe207e5711010f1f
git describe: 4.4.94-rc1-hikey-20171019
Test details: 
https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.94-rc1-hikey-20171019


No regressions (compared to build 4.4.93-rc1-hikey-20171016)

Boards, architectures and test suites:
-

hi6220-hikey - arm64
* boot - pass: 20,
* kselftest - pass: 32, skip: 9, fail:

Re: [PATCH 4.4 00/46] 4.4.94-stable review

2017-10-19 Thread Tom Gall 

> On Oct 19, 2017, at 8:48 AM, Greg Kroah-Hartman  
> wrote:
> 
> This is the start of the stable review cycle for the 4.4.94 release.
> There are 46 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
> or in the git tree and branch at:
>  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.4.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

Results from the Linaro test farm. This report is in two parts. The second part 
and reported 
separately is the HiKey results since there are platform support patches added 
to the LTS
to make it work.

Summary


kernel: 4.4.94-rc1
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.4.y
git commit: cc1d76b2d639a37b3e6aec284b6838637d826f08
git describe: v4.4.93-47-gcc1d76b2d639
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.93-47-gcc1d76b2d639

Regressions (compared to build v4.4.92-29-g51c43ad676c4)


x15 - arm:
 kselftest:
   * raw_skew

   * test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz

 ltp-syscalls-tests:
   * fcntl36

   * test src: git://github.com/linux-test-project/ltp.git

fcntl36 and raw_skew we’ll looking into.

 ltp-timers-tests:
   * leapsec_timer
   * runltp_timers

   * test src: git://github.com/linux-test-project/ltp.git

This one has been working and just failed with this RC cycle. It’s only failing 
on 32 bit arm.

Needs to be looked into.


Boards, architectures and test suites:
-

juno-r2 - arm64
* boot - pass: 20,
* kselftest - pass: 32, skip: 7, fail: 13 (known failures)
* libhugetlbfs - pass: 90, skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 27, skip: 36, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 59, fail: 2 (known failures)
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 14,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 938, skip: 159, fail: 15 (known failures)
* ltp-timers-tests - pass: 13,

x15 - arm
* boot - pass: 20,
* kselftest - pass: 31, skip: 1, fail: 21 (known failures)
* libhugetlbfs - skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 63, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 60,
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1036, skip: 68, fail: 5 (noted above)
* ltp-timers-tests - pass: 11, fail: 2 (noted above)

dell-poweredge-r200 - x86_64
* boot - pass: 20,
* kselftest - pass: 43, fail: 24
* libhugetlbfs - pass: 76, skip: 1,
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 63, fail: 18 (known failures)
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 1,
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1,
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 960, skip: 164, fail: 13 (known failures)
* ltp-timers-tests - pass: 13,



Summary


kernel: 4.4.94-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git tag: 4.4.94-rc1-hikey-20171019
git commit: 64eacf43d6ff4c9320737af2fe207e5711010f1f
git describe: 4.4.94-rc1-hikey-20171019
Test details: 
https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build/4.4.94-rc1-hikey-20171019


No regressions (compared to build 4.4.93-rc1-hikey-20171016)

Boards, architectures and test suites:
-

hi6220-hikey - arm64
* boot - pass: 20,
* kselftest - pass: 32, skip: 9, fail: 13 (known failures)
*

[PATCH 4.4 00/46] 4.4.94-stable review

2017-10-19 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 4.4.94 release.
There are 46 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
or in the git tree and branch at:
  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
linux-4.4.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.4.94-rc1

Greg Kroah-Hartman 
Revert "tty: goldfish: Fix a parameter of a call to free_irq"

Arnd Bergmann 
cpufreq: CPPC: add ACPI_PROCESSOR dependency

Kinglong Mee 
nfsd/callback: Cleanup callback cred on shutdown

Varun Prakash 
target/iscsi: Fix unsolicited data seq_end_offset calculation

Dmitry V. Levin 
uapi: fix linux/mroute6.h userspace compilation errors

Dmitry V. Levin 
uapi: fix linux/rds.h userspace compilation errors

Jeff Layton 
ceph: clean up unsafe d_parent accesses in build_dentry_path

Alexandre Belloni 
i2c: at91: ensure state is restored after suspending

Thomas Petazzoni 
net: mvpp2: release reference to txq_cpu[] entry after unmapping

Dan Carpenter 
scsi: scsi_dh_emc: return success in clariion_std_inquiry()

Grygorii Maistrenko 
slub: do not merge cache if slub_debug contains a never-merge flag

Eric Ren 
ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Milan Broz 
crypto: xts - Add ECB dependency

Majd Dibbiny 
net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new 
probed PFs

Vijay Kumar 
sparc64: Migrate hvcons irq to panicked cpu

Shaohua Li 
md/linear: shutup lockdep warnning

Jaegeuk Kim 
f2fs: do not wait for writeback in write_begin

Robbie Ko 
Btrfs: send, fix failure to rename top level inode due to name collision

Christophe JAILLET 
iio: adc: xilinx: Fix error handling

Jarno Rajahalme 
netfilter: nf_ct_expect: Change __nf_ct_expect_check() return value.

Eric Dumazet 
net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

Emmanuel Grumbach 
mac80211: fix power saving clients handling in iwlwifi

Johannes Berg 
mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

Franck Demathieu 
irqchip/crossbar: Fix incorrect type of local variables

Arnd Bergmann 
watchdog: kempld: fix gcc-4.3 build

Peter Zijlstra 
locking/lockdep: Add nest_lock integrity test

Greg Kroah-Hartman 
Revert "bsg-lib: don't free job in bsg_prepare_job"

Parthasarathy Bhuvaragan 
tipc: use only positive error codes in messages

Christoph Paasch 
net: Set sk_prot_creator when cloning sockets to the right proto

Willem de Bruijn 
packet: only test po->has_vnet_hdr once in packet_snd

Willem de Bruijn 
packet: in packet_do_bind, test fanout with bind_lock held

Alexander Potapenko 
tun: bail out from tun_get_user() if the skb is empty

Sabrina Dubroca 
l2tp: fix race condition in l2tp_tunnel_delete

Ridge Kennedy 
l2tp: Avoid schedule while atomic in exit_net

Alexey Kodanev 
vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit

Meng Xu 
isdn/i4l: fetch the ppp_write buffer in one shot

Yonghong Song 
bpf: one perf event close won't free bpf program attached by another perf 
event

Willem de Bruijn 
packet: hold bind lock when rebinding to fanout hook

Christian Lamparter 
net: emac: Fix napi poll list corruption

Xin Long 
ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header

Subash Abhinov Kasiviswanathan 
udpv6: Fix the checksum computation when HW checksum does not apply

Edward Cree 
bpf/verifier: reject BPF_ALU64|BPF_END

Dan Carpenter 
sctp: potential read out

[PATCH 4.4 00/46] 4.4.94-stable review

2017-10-19 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 4.4.94 release.
There are 46 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat Oct 21 13:48:23 UTC 2017.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.94-rc1.gz
or in the git tree and branch at:
  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
linux-4.4.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.4.94-rc1

Greg Kroah-Hartman 
Revert "tty: goldfish: Fix a parameter of a call to free_irq"

Arnd Bergmann 
cpufreq: CPPC: add ACPI_PROCESSOR dependency

Kinglong Mee 
nfsd/callback: Cleanup callback cred on shutdown

Varun Prakash 
target/iscsi: Fix unsolicited data seq_end_offset calculation

Dmitry V. Levin 
uapi: fix linux/mroute6.h userspace compilation errors

Dmitry V. Levin 
uapi: fix linux/rds.h userspace compilation errors

Jeff Layton 
ceph: clean up unsafe d_parent accesses in build_dentry_path

Alexandre Belloni 
i2c: at91: ensure state is restored after suspending

Thomas Petazzoni 
net: mvpp2: release reference to txq_cpu[] entry after unmapping

Dan Carpenter 
scsi: scsi_dh_emc: return success in clariion_std_inquiry()

Grygorii Maistrenko 
slub: do not merge cache if slub_debug contains a never-merge flag

Eric Ren 
ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Milan Broz 
crypto: xts - Add ECB dependency

Majd Dibbiny 
net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new 
probed PFs

Vijay Kumar 
sparc64: Migrate hvcons irq to panicked cpu

Shaohua Li 
md/linear: shutup lockdep warnning

Jaegeuk Kim 
f2fs: do not wait for writeback in write_begin

Robbie Ko 
Btrfs: send, fix failure to rename top level inode due to name collision

Christophe JAILLET 
iio: adc: xilinx: Fix error handling

Jarno Rajahalme 
netfilter: nf_ct_expect: Change __nf_ct_expect_check() return value.

Eric Dumazet 
net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

Emmanuel Grumbach 
mac80211: fix power saving clients handling in iwlwifi

Johannes Berg 
mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

Franck Demathieu 
irqchip/crossbar: Fix incorrect type of local variables

Arnd Bergmann 
watchdog: kempld: fix gcc-4.3 build

Peter Zijlstra 
locking/lockdep: Add nest_lock integrity test

Greg Kroah-Hartman 
Revert "bsg-lib: don't free job in bsg_prepare_job"

Parthasarathy Bhuvaragan 
tipc: use only positive error codes in messages

Christoph Paasch 
net: Set sk_prot_creator when cloning sockets to the right proto

Willem de Bruijn 
packet: only test po->has_vnet_hdr once in packet_snd

Willem de Bruijn 
packet: in packet_do_bind, test fanout with bind_lock held

Alexander Potapenko 
tun: bail out from tun_get_user() if the skb is empty

Sabrina Dubroca 
l2tp: fix race condition in l2tp_tunnel_delete

Ridge Kennedy 
l2tp: Avoid schedule while atomic in exit_net

Alexey Kodanev 
vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit

Meng Xu 
isdn/i4l: fetch the ppp_write buffer in one shot

Yonghong Song 
bpf: one perf event close won't free bpf program attached by another perf 
event

Willem de Bruijn 
packet: hold bind lock when rebinding to fanout hook

Christian Lamparter 
net: emac: Fix napi poll list corruption

Xin Long 
ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header

Subash Abhinov Kasiviswanathan 
udpv6: Fix the checksum computation when HW checksum does not apply

Edward Cree 
bpf/verifier: reject BPF_ALU64|BPF_END

Dan Carpenter 
sctp: potential read out of bounds in sctp_ulpevent_type_enabled()

Matt Redfearn 
MIPS: Fix minimum alignment requirement of IRQ stack

Harry Wentland 
drm/dp/mst: save vcpi with payloads

Mark Rutland 
percpu: make this_cpu_generic_read() atomic w.r.t. interrupts


-

Diffstat:

 Makefile  |   4 +-
 arch/mips/include/asm/irq.h   |   2 +-
 arch/sparc/include/asm/setup.h|   5 +-
 arch/sparc/kernel/smp_64.c|   6 +-
 block/bsg-lib.c   |   1 +
 crypto/Kconfig|   1 +
 drivers/cpufreq/Kconfig.arm   |   2 +-
 drivers/gpu/drm/drm_dp_mst_topology.c |   2 +
 drivers/i2c/busses/i2c-at91.c |   3 +
 drivers/iio/adc/xilinx-xadc-core.c|   6 +-
 drivers/irqchip/irq-crossbar.c|   3 +-
 drivers/isdn/i4l/isdn_ppp.c   |  37 ++---
 drivers/md/linear.c   |   3 +-