Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/27/2018 01:45 AM, Greg Kroah-Hartman wrote:

On Tue, Mar 27, 2018 at 11:33:00AM +0300, Thomas Backlund wrote:

Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they
idle at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued
already.

Guenter



And if you ant it to work in 4.14 longterm, you want the series:

68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip
specific code into probe function
9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support for
family 17h
1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support for
temperature offsets
ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model
name for Ryzen 1600X
6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add temperature
offset for Ryzen 1900X
aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply
temperature offset if result is positive


We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and
ThreadRipper 1950X


I'd like an ack from the hwmon maintainer before adding all of those, as
it really feels like a "backport new hardware support" type of request
that is a bit bigger than a normal "add some new device ids and quirks".


That is why I did not request it. It is ok with me if you are willing to
accept it, though.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/27/2018 01:45 AM, Greg Kroah-Hartman wrote:

On Tue, Mar 27, 2018 at 11:33:00AM +0300, Thomas Backlund wrote:

Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they
idle at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued
already.

Guenter



And if you ant it to work in 4.14 longterm, you want the series:

68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip
specific code into probe function
9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support for
family 17h
1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support for
temperature offsets
ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model
name for Ryzen 1600X
6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add temperature
offset for Ryzen 1900X
aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply
temperature offset if result is positive


We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and
ThreadRipper 1950X


I'd like an ack from the hwmon maintainer before adding all of those, as
it really feels like a "backport new hardware support" type of request
that is a bit bigger than a normal "add some new device ids and quirks".


That is why I did not request it. It is ok with me if you are willing to
accept it, though.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Tue, Mar 27, 2018 at 11:33:00AM +0300, Thomas Backlund wrote:
> Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:
> > On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:
> > > On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> > > > On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > > > > Ryzen and Threadripper are only supported in v4.15+.
> > > > 
> > > > 
> > > > Nope, the offset for 1900X is not available in 4.15, I've had to
> > > > manually patch all systems otherwise monitoring complains they
> > > > idle at 53C.
> > > 
> > > I don't understand, what patch are you talking about here?
> > > 
> > 
> > 6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued
> > already.
> > 
> > Guenter
> > 
> 
> And if you ant it to work in 4.14 longterm, you want the series:
> 
> 68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip
> specific code into probe function
> 9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support for
> family 17h
> 1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support for
> temperature offsets
> ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model
> name for Ryzen 1600X
> 6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add temperature
> offset for Ryzen 1900X
> aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply
> temperature offset if result is positive
> 
> 
> We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and
> ThreadRipper 1950X

I'd like an ack from the hwmon maintainer before adding all of those, as
it really feels like a "backport new hardware support" type of request
that is a bit bigger than a normal "add some new device ids and quirks".

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Tue, Mar 27, 2018 at 11:33:00AM +0300, Thomas Backlund wrote:
> Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:
> > On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:
> > > On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> > > > On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > > > > Ryzen and Threadripper are only supported in v4.15+.
> > > > 
> > > > 
> > > > Nope, the offset for 1900X is not available in 4.15, I've had to
> > > > manually patch all systems otherwise monitoring complains they
> > > > idle at 53C.
> > > 
> > > I don't understand, what patch are you talking about here?
> > > 
> > 
> > 6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued
> > already.
> > 
> > Guenter
> > 
> 
> And if you ant it to work in 4.14 longterm, you want the series:
> 
> 68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip
> specific code into probe function
> 9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support for
> family 17h
> 1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support for
> temperature offsets
> ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model
> name for Ryzen 1600X
> 6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add temperature
> offset for Ryzen 1900X
> aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply
> temperature offset if result is positive
> 
> 
> We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and
> ThreadRipper 1950X

I'd like an ack from the hwmon maintainer before adding all of those, as
it really feels like a "backport new hardware support" type of request
that is a bit bigger than a normal "add some new device ids and quirks".

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Thomas Backlund]

Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle 
at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued 
already.


Guenter



And if you ant it to work in 4.14 longterm, you want the series:

68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip 
specific code into probe function
9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support 
for family 17h
1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support 
for temperature offsets
ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model 
name for Ryzen 1600X
6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add 
temperature offset for Ryzen 1900X
aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply 
temperature offset if result is positive



We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and 
ThreadRipper 1950X


--
Thomas

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Thomas Backlund]

Den 27.03.2018 kl. 09:37, skrev Guenter Roeck:

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle 
at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued 
already.


Guenter



And if you ant it to work in 4.14 longterm, you want the series:

68546abf7a3a63f199e53d6dcaa7375df37a6aaa  hwmon: (k10temp) Move chip 
specific code into probe function
9af0a9aecdb945cd5513941ffdcbcc031009b402  hwmon: (k10temp) Add support 
for family 17h
1b50b776355fa6c6d7b3281a63c275d5c18d629d  hwmon: (k10temp) Add support 
for temperature offsets
ab5ee24615f9dd8b0cd199403959f8b13309e7b1  hwmon: (k10temp) Correct model 
name for Ryzen 1600X
6509614fdd2d05c6926d50901a45d5dfb852b715  hwmon: (k10temp) Add 
temperature offset for Ryzen 1900X
aef17ca1271948ee57cc39b2493d31110cc42625  hwmon: (k10temp) Only apply 
temperature offset if result is positive



We have it in Mageia, and I've confirmed it works on a Ryzen 7 1700 and 
ThreadRipper 1950X


--
Thomas

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Mon, Mar 26, 2018 at 11:37:28PM -0700, Guenter Roeck wrote:
> On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:
> > On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> > > On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > > > Ryzen and Threadripper are only supported in v4.15+.
> > > 
> > > 
> > > Nope, the offset for 1900X is not available in 4.15, I've had to
> > > manually patch all systems otherwise monitoring complains they idle at 
> > > 53C.
> > 
> > I don't understand, what patch are you talking about here?
> > 
> 
> 6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued already.

Both now queued up, thanks.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Mon, Mar 26, 2018 at 11:37:28PM -0700, Guenter Roeck wrote:
> On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:
> > On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> > > On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > > > Ryzen and Threadripper are only supported in v4.15+.
> > > 
> > > 
> > > Nope, the offset for 1900X is not available in 4.15, I've had to
> > > manually patch all systems otherwise monitoring complains they idle at 
> > > 53C.
> > 
> > I don't understand, what patch are you talking about here?
> > 
> 
> 6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued already.

Both now queued up, thanks.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued already.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/26/2018 11:28 PM, Greg Kroah-Hartman wrote:

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:

On 2018-03-19 02:20 PM, Guenter Roeck wrote:

Ryzen and Threadripper are only supported in v4.15+.



Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle at 53C.


I don't understand, what patch are you talking about here?



6509614fdd2d, but you'll also want aef17ca12719 if that isn't queued already.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > Ryzen and Threadripper are only supported in v4.15+.
> 
> 
> Nope, the offset for 1900X is not available in 4.15, I've had to
> manually patch all systems otherwise monitoring complains they idle at 53C.

I don't understand, what patch are you talking about here?

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Mon, Mar 26, 2018 at 01:54:18PM -0400, Kash Pande wrote:
> On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> > Ryzen and Threadripper are only supported in v4.15+.
> 
> 
> Nope, the offset for 1900X is not available in 4.15, I've had to
> manually patch all systems otherwise monitoring complains they idle at 53C.

I don't understand, what patch are you talking about here?

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Kash Pande]

On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> Ryzen and Threadripper are only supported in v4.15+.


Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle at 53C.




signature.asc
Description: OpenPGP digital signature

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Kash Pande]

On 2018-03-19 02:20 PM, Guenter Roeck wrote:
> Ryzen and Threadripper are only supported in v4.15+.


Nope, the offset for 1900X is not available in 4.15, I've had to
manually patch all systems otherwise monitoring complains they idle at 53C.




signature.asc
Description: OpenPGP digital signature

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On Mon, Mar 19, 2018 at 02:13:23PM -0400, Kash Pande wrote:
> On 2018-03-16 11:22 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> 
> Any chance to get the k10temp change for Threadripper 1900X offset
> reporting included [https://patchwork.kernel.org/patch/10175457/]?
> 
Ryzen and Threadripper are only supported in v4.15+.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On Mon, Mar 19, 2018 at 02:13:23PM -0400, Kash Pande wrote:
> On 2018-03-16 11:22 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> 
> Any chance to get the k10temp change for Threadripper 1900X offset
> reporting included [https://patchwork.kernel.org/patch/10175457/]?
> 
Ryzen and Threadripper are only supported in v4.15+.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Kash Pande]

On 2018-03-16 11:22 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.

Any chance to get the k10temp change for Threadripper 1900X offset
reporting included [https://patchwork.kernel.org/patch/10175457/]?


Kash Pande



signature.asc
Description: OpenPGP digital signature

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Kash Pande]

On 2018-03-16 11:22 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.

Any chance to get the k10temp change for Threadripper 1900X offset
reporting included [https://patchwork.kernel.org/patch/10175457/]?


Kash Pande



signature.asc
Description: OpenPGP digital signature

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Dan Rue]

On Sun, Mar 18, 2018 at 12:14:42PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.28 release.
> > > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > > and the diffstat can be found below.
> > 
> > -rc2 is out to fix a build problem on some configs:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz
> 
> Ok, that sucked, let's try this again...
> 
> -rc3 is out, and this time it at least passed _my_ build tests:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz

As reported, arm32 build failed and so tests did not run. No regressions on
arm64 or x86_64.

There are two 'regressions' listed below which are not regressions.
reuseport_bpf is a test issue that's fixed in mainline kselftest, which we'll
pick up when 4.16 is released. sigreturn_64 is an intermittent failure that
we've been seeing on qemu only. It works fine on real hardware.

Summary


kernel: 4.14.28-rc3
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: de586f09b77dafe110c0689218b860aefd7e4ed6
git describe: v4.14.27-108-gde586f09b77d
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.27-108-gde586f09b77d

Regressions (compared to build v4.14.27-110-g96676597127d)


qemu_x86_64:
  kselftest-vsyscall-mode-native:
* reuseport_bpf
* sigreturn_64

* test src: not informed
  kselftest-vsyscall-mode-none:
* sigreturn_64

* test src: not informed


Boards, architectures and test suites:
-

dragonboard-410c
* boot - pass: 20
* kselftest - skip: 20, pass: 45
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* ltp-fs_bind-tests - pass: 2
* ltp-fs_perms_simple-tests - pass: 19
* ltp-fsx-tests - pass: 2
* ltp-hugetlb-tests - skip: 1, pass: 21
* 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 - skip: 148, pass: 1002
* ltp-timers-tests - skip: 1, pass: 12

hi6220-hikey - arm64
* boot - pass: 20
* kselftest - skip: 17, pass: 48
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* ltp-fs_bind-tests - pass: 2
* ltp-fs_perms_simple-tests - pass: 19
* ltp-fsx-tests - pass: 2
* ltp-hugetlb-tests - skip: 1, pass: 21
* 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 - skip: 4, pass: 10
* ltp-securebits-tests - pass: 4
* ltp-syscalls-tests - skip: 151, pass: 999
* ltp-timers-tests - skip: 1, pass: 12

juno-r2 - arm64
* boot - pass: 20
* kselftest - skip: 17, pass: 48
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* 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 - skip: 4, pass: 10
* ltp-securebits-tests - pass: 4
* ltp-syscalls-tests - skip: 149, pass: 1001
* ltp-timers-tests - skip: 1, pass: 12

qemu_x86_64
* boot - pass: 28
* kselftest - skip: 20, pass: 62
* kselftest-vsyscall-mode-native - skip: 40, fail: 2, pass: 122
* kselftest-vsyscall-mode-none - skip: 40, fail: 1, pass: 123
* libhugetlbfs - skip: 2, pass: 180
* ltp-cap_bounds-tests - pass: 4
* ltp-containers-tests - skip: 34, pass: 128
* ltp-fcntl-locktests-tests - pass: 4
* ltp-filecaps-tests - pass: 2
* 

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Dan Rue]

On Sun, Mar 18, 2018 at 12:14:42PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.28 release.
> > > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > > and the diffstat can be found below.
> > 
> > -rc2 is out to fix a build problem on some configs:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz
> 
> Ok, that sucked, let's try this again...
> 
> -rc3 is out, and this time it at least passed _my_ build tests:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz

As reported, arm32 build failed and so tests did not run. No regressions on
arm64 or x86_64.

There are two 'regressions' listed below which are not regressions.
reuseport_bpf is a test issue that's fixed in mainline kselftest, which we'll
pick up when 4.16 is released. sigreturn_64 is an intermittent failure that
we've been seeing on qemu only. It works fine on real hardware.

Summary


kernel: 4.14.28-rc3
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: de586f09b77dafe110c0689218b860aefd7e4ed6
git describe: v4.14.27-108-gde586f09b77d
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.27-108-gde586f09b77d

Regressions (compared to build v4.14.27-110-g96676597127d)


qemu_x86_64:
  kselftest-vsyscall-mode-native:
* reuseport_bpf
* sigreturn_64

* test src: not informed
  kselftest-vsyscall-mode-none:
* sigreturn_64

* test src: not informed


Boards, architectures and test suites:
-

dragonboard-410c
* boot - pass: 20
* kselftest - skip: 20, pass: 45
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* ltp-fs_bind-tests - pass: 2
* ltp-fs_perms_simple-tests - pass: 19
* ltp-fsx-tests - pass: 2
* ltp-hugetlb-tests - skip: 1, pass: 21
* 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 - skip: 148, pass: 1002
* ltp-timers-tests - skip: 1, pass: 12

hi6220-hikey - arm64
* boot - pass: 20
* kselftest - skip: 17, pass: 48
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* ltp-fs_bind-tests - pass: 2
* ltp-fs_perms_simple-tests - pass: 19
* ltp-fsx-tests - pass: 2
* ltp-hugetlb-tests - skip: 1, pass: 21
* 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 - skip: 4, pass: 10
* ltp-securebits-tests - pass: 4
* ltp-syscalls-tests - skip: 151, pass: 999
* ltp-timers-tests - skip: 1, pass: 12

juno-r2 - arm64
* boot - pass: 20
* kselftest - skip: 17, pass: 48
* libhugetlbfs - skip: 1, pass: 90
* ltp-cap_bounds-tests - pass: 2
* ltp-containers-tests - skip: 17, pass: 64
* ltp-fcntl-locktests-tests - pass: 2
* ltp-filecaps-tests - pass: 2
* ltp-fs-tests - skip: 2, pass: 61
* 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 - skip: 4, pass: 10
* ltp-securebits-tests - pass: 4
* ltp-syscalls-tests - skip: 149, pass: 1001
* ltp-timers-tests - skip: 1, pass: 12

qemu_x86_64
* boot - pass: 28
* kselftest - skip: 20, pass: 62
* kselftest-vsyscall-mode-native - skip: 40, fail: 2, pass: 122
* kselftest-vsyscall-mode-none - skip: 40, fail: 1, pass: 123
* libhugetlbfs - skip: 2, pass: 180
* ltp-cap_bounds-tests - pass: 4
* ltp-containers-tests - skip: 34, pass: 128
* ltp-fcntl-locktests-tests - pass: 4
* ltp-filecaps-tests - pass: 2
* 

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sun, Mar 18, 2018 at 03:39:38PM -0700, Guenter Roeck wrote:
> On 03/18/2018 04:14 AM, Greg Kroah-Hartman wrote:
> > On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> > > On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.14.28 release.
> > > > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > > > Anything received after that time might be too late.
> > > > 
> > > > The whole patch series can be found in one patch at:
> > > > 
> > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > > > and the diffstat can be found below.
> > > 
> > > -rc2 is out to fix a build problem on some configs:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz
> > 
> > Ok, that sucked, let's try this again...
> > 
> > -rc3 is out, and this time it at least passed _my_ build tests:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz
> > 
> 
> For v4.14.27-108-gde586f0:
> 
> Build results:
>   total: 145 pass: 145 fail: 0
> Qemu test results:
>   total: 141 pass: 141 fail: 0

Thanks for testing both of these again and letting me know.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sun, Mar 18, 2018 at 03:39:38PM -0700, Guenter Roeck wrote:
> On 03/18/2018 04:14 AM, Greg Kroah-Hartman wrote:
> > On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> > > On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.14.28 release.
> > > > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > > > Anything received after that time might be too late.
> > > > 
> > > > The whole patch series can be found in one patch at:
> > > > 
> > > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > > > and the diffstat can be found below.
> > > 
> > > -rc2 is out to fix a build problem on some configs:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz
> > 
> > Ok, that sucked, let's try this again...
> > 
> > -rc3 is out, and this time it at least passed _my_ build tests:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz
> > 
> 
> For v4.14.27-108-gde586f0:
> 
> Build results:
>   total: 145 pass: 145 fail: 0
> Qemu test results:
>   total: 141 pass: 141 fail: 0

Thanks for testing both of these again and letting me know.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/18/2018 04:14 AM, Greg Kroah-Hartman wrote:

On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:

On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
and the diffstat can be found below.


-rc2 is out to fix a build problem on some configs:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz


Ok, that sucked, let's try this again...

-rc3 is out, and this time it at least passed _my_ build tests:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz



For v4.14.27-108-gde586f0:

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

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/18/2018 04:14 AM, Greg Kroah-Hartman wrote:

On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:

On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
and the diffstat can be found below.


-rc2 is out to fix a build problem on some configs:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz


Ok, that sucked, let's try this again...

-rc3 is out, and this time it at least passed _my_ build tests:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz



For v4.14.27-108-gde586f0:

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

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > and the diffstat can be found below.
> 
> -rc2 is out to fix a build problem on some configs:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz

Ok, that sucked, let's try this again...

-rc3 is out, and this time it at least passed _my_ build tests:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sun, Mar 18, 2018 at 11:24:54AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> > and the diffstat can be found below.
> 
> -rc2 is out to fix a build problem on some configs:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz

Ok, that sucked, let's try this again...

-rc3 is out, and this time it at least passed _my_ build tests:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc3.gz

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sat, Mar 17, 2018 at 01:10:28AM +0530, Naresh Kamboju wrote:
> On 16 March 2018 at 20:52, Greg Kroah-Hartman
>  wrote:
> > Peter Ujfalusi 
> > dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free
> 
> arm and arm64 build broken due to this patch for 4.14 and 4.15
> 
> drivers/dma/bcm2835-dma.c:815:3: error: implicit declaration of function
> 'vchan_terminate_vdesc' [-Werror=implicit-function-declaration]
>vchan_terminate_vdesc(>desc->vd);
>^
> cc1: some warnings being treated as errors
> 
> FYI, build using GCCVERSION = "linaro-6.2"

Should now be resolved, thanks.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sat, Mar 17, 2018 at 01:10:28AM +0530, Naresh Kamboju wrote:
> On 16 March 2018 at 20:52, Greg Kroah-Hartman
>  wrote:
> > Peter Ujfalusi 
> > dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free
> 
> arm and arm64 build broken due to this patch for 4.14 and 4.15
> 
> drivers/dma/bcm2835-dma.c:815:3: error: implicit declaration of function
> 'vchan_terminate_vdesc' [-Werror=implicit-function-declaration]
>vchan_terminate_vdesc(>desc->vd);
>^
> cc1: some warnings being treated as errors
> 
> FYI, build using GCCVERSION = "linaro-6.2"

Should now be resolved, thanks.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sat, Mar 17, 2018 at 07:46:20AM -0700, Guenter Roeck wrote:
> On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
>   total: 145 pass: 140 fail: 5

Thanks, I've pushed out a -rc2 to hopefully fix this build issue.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Sat, Mar 17, 2018 at 07:46:20AM -0700, Guenter Roeck wrote:
> On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.28 release.
> > There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
>   total: 145 pass: 140 fail: 5

Thanks, I've pushed out a -rc2 to hopefully fix this build issue.

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> and the diffstat can be found below.

-rc2 is out to fix a build problem on some configs:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

On Fri, Mar 16, 2018 at 04:22:29PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> and the diffstat can be found below.

-rc2 is out to fix a build problem on some configs:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-rc2.gz

thanks,

greg k-h

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.



Build results:
total: 145 pass: 140 fail: 5
Failed builds:
arm:allmodconfig
arm:lpc32xx_defconfig
arm:nhk8815_defconfig
arm:bcm2835_defconfig
arm64:allmodconfig
Qemu test results:
total: 141 pass: 122 fail: 19
Failed tests:
arm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:sabrelite:multi_v7_defconfig:imx6dl-sabrelite
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:vexpress-a15-a7:multi_v7_defconfig:vexpress-v2p-ca15_a7
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:midway:multi_v7_defconfig:ecx-2000
arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
arm64:virt:smp:defconfig:initrd
arm64:virt:smp:defconfig:rootfs
arm64:xlnx-zcu102:smp:defconfig:initrd:zynqmp-ep108
arm64:xlnx-zcu102:smp:defconfig:rootfs:zynqmp-ep108
arm64:virt:nosmp:defconfig:initrd
arm64:xlnx-zcu102:nosmp:defconfig:initrd:zynqmp-ep108
arm64:xlnx-zcu102:nosmp:defconfig:rootfs:zynqmp-ep108

The failure, as already reported, is

drivers/dma/bcm2835-dma.c: In function 'bcm2835_dma_terminate_all':
drivers/dma/bcm2835-dma.c:815:3: error: implicit declaration of function 
'vchan_terminate_vdesc'

Further details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Guenter Roeck]

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.



Build results:
total: 145 pass: 140 fail: 5
Failed builds:
arm:allmodconfig
arm:lpc32xx_defconfig
arm:nhk8815_defconfig
arm:bcm2835_defconfig
arm64:allmodconfig
Qemu test results:
total: 141 pass: 122 fail: 19
Failed tests:
arm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:sabrelite:multi_v7_defconfig:imx6dl-sabrelite
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:vexpress-a15-a7:multi_v7_defconfig:vexpress-v2p-ca15_a7
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:midway:multi_v7_defconfig:ecx-2000
arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
arm64:virt:smp:defconfig:initrd
arm64:virt:smp:defconfig:rootfs
arm64:xlnx-zcu102:smp:defconfig:initrd:zynqmp-ep108
arm64:xlnx-zcu102:smp:defconfig:rootfs:zynqmp-ep108
arm64:virt:nosmp:defconfig:initrd
arm64:xlnx-zcu102:nosmp:defconfig:initrd:zynqmp-ep108
arm64:xlnx-zcu102:nosmp:defconfig:rootfs:zynqmp-ep108

The failure, as already reported, is

drivers/dma/bcm2835-dma.c: In function 'bcm2835_dma_terminate_all':
drivers/dma/bcm2835-dma.c:815:3: error: implicit declaration of function 
'vchan_terminate_vdesc'

Further details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Naresh Kamboju]

On 16 March 2018 at 20:52, Greg Kroah-Hartman
 wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman 
> Linux 4.14.28-rc1
>
> Anusha Srivatsa 
> drm/i915/glk: Disable Guc and HuC on GLK
>
> Sinan Kaya 
> dmaengine: qcom_hidma: check pending interrupts
>
> Arnd Bergmann 
> IB/mlx5: revisit -Wmaybe-uninitialized warning
>
> Mimi Zohar 
> ima: relax requiring a file signature for new files with zero length
>
> Davidlohr Bueso 
> locking/locktorture: Fix num reader/writer corner cases
>
> SeongJae Park 
> rcutorture/configinit: Fix build directory error message
>
> Mahesh Bandewar 
> ipvlan: add L2 check for packets arriving via virtual devices
>
> Christophe Leroy 
> Fix misannotated out-of-line _copy_to_user()
>
> Adrian Hunter 
> mmc: mmc_test: Ensure command queue is disabled for testing
>
> Dan Carpenter 
> ASoC: nuc900: Fix a loop timeout test
>
> Horia Geantă 
> crypto: caam/qi - use correct print specifier for size_t
>
> Luca Coelho 
> mac80211: remove BUG() when interface type is invalid
>
> Adiel Aloni 
> mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED
>
> Chris Wilson 
> agp/intel: Flush all chipset writes after updating the GGTT
>
> Geert Uytterhoeven 
> arm64: dts: renesas: salvator-common: Add EthernetAVB PHY reset
>
> Nicholas Piggin 
> powerpc/64: Don't trace irqs-off at interrupt return to soft-disabled 
> context
>
> Josh Poimboeuf 
> powerpc/modules: Don't try to restore r2 after a sibling call
>
> Yong Zhao 
> drm/amdkfd: Fix memory leaks in kfd topology
>
> Stephen Hemminger 
> veth: set peer GSO values
>
> John Fastabend 
> net: sched: drop qdisc_reset from dev_graft_qdisc
>
> Toshiaki Makita 
> virtio_net: Disable interrupts if napi_complete_done rescheduled napi
>
> Gustavo A. R. Silva 
> media: davinci: vpif_capture: add NULL check on devm_kzalloc return value
>
> Dan Carpenter 
> media: cpia2: Fix a couple off by one bugs
>
> Heinz Mauelshagen 
> dm raid: fix raid set size revalidation
>
> Kieran Bingham 
> media: vsp1: Prevent suspending and resuming DRM pipelines
>
> Xose Vazquez Perez 
> scsi: dh: add new rdac devices
>
> Xose Vazquez Perez 
> scsi: devinfo: apply to HP XP the same flags as Hitachi VSP
>
> Bart Van Assche 
> scsi: core: scsi_get_device_flags_keyed(): Always return device flags
>
> Michael Chan 
> bnxt_en: Don't print "Link speed -1 no longer supported" messages.
>
> Tobias Jordan 
> spi: sun6i: disable/unprepare clocks on remove
>
> Julien BOIBESSOT 
> tools/usbip: fixes build with musl libc toolchain
>
> Ben Greear 
> ath10k: fix invalid STS_CAP_OFFSET_MASK
>
> Limin Zhu 
> mwifiex: cfg80211: do not change virtual interface during scan processing
>
> Srinivas Kandagatla 
> clk: qcom: msm8916: fix mnd_width for codec_digcodec
>
> Monk Liu 
> drm/amdgpu:fix virtual dce bug
>
> Sara Sharon 
> iwlwifi: mvm: avoid dumping assert log when device is stopped
>
> Thomas Richter 
> perf annotate: Fix objdump comment parsing for Intel mov dissassembly
>
> Thomas Richter 
> perf annotate: Fix unnecessary memory allocation for s390x
>
> Takeshi Kihara 
> pinctrl: sh-pfc: 

Re: [PATCH 4.14 000/109] 4.14.28-stable review

[Naresh Kamboju]

On 16 March 2018 at 20:52, Greg Kroah-Hartman
 wrote:
> This is the start of the stable review cycle for the 4.14.28 release.
> There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman 
> Linux 4.14.28-rc1
>
> Anusha Srivatsa 
> drm/i915/glk: Disable Guc and HuC on GLK
>
> Sinan Kaya 
> dmaengine: qcom_hidma: check pending interrupts
>
> Arnd Bergmann 
> IB/mlx5: revisit -Wmaybe-uninitialized warning
>
> Mimi Zohar 
> ima: relax requiring a file signature for new files with zero length
>
> Davidlohr Bueso 
> locking/locktorture: Fix num reader/writer corner cases
>
> SeongJae Park 
> rcutorture/configinit: Fix build directory error message
>
> Mahesh Bandewar 
> ipvlan: add L2 check for packets arriving via virtual devices
>
> Christophe Leroy 
> Fix misannotated out-of-line _copy_to_user()
>
> Adrian Hunter 
> mmc: mmc_test: Ensure command queue is disabled for testing
>
> Dan Carpenter 
> ASoC: nuc900: Fix a loop timeout test
>
> Horia Geantă 
> crypto: caam/qi - use correct print specifier for size_t
>
> Luca Coelho 
> mac80211: remove BUG() when interface type is invalid
>
> Adiel Aloni 
> mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED
>
> Chris Wilson 
> agp/intel: Flush all chipset writes after updating the GGTT
>
> Geert Uytterhoeven 
> arm64: dts: renesas: salvator-common: Add EthernetAVB PHY reset
>
> Nicholas Piggin 
> powerpc/64: Don't trace irqs-off at interrupt return to soft-disabled 
> context
>
> Josh Poimboeuf 
> powerpc/modules: Don't try to restore r2 after a sibling call
>
> Yong Zhao 
> drm/amdkfd: Fix memory leaks in kfd topology
>
> Stephen Hemminger 
> veth: set peer GSO values
>
> John Fastabend 
> net: sched: drop qdisc_reset from dev_graft_qdisc
>
> Toshiaki Makita 
> virtio_net: Disable interrupts if napi_complete_done rescheduled napi
>
> Gustavo A. R. Silva 
> media: davinci: vpif_capture: add NULL check on devm_kzalloc return value
>
> Dan Carpenter 
> media: cpia2: Fix a couple off by one bugs
>
> Heinz Mauelshagen 
> dm raid: fix raid set size revalidation
>
> Kieran Bingham 
> media: vsp1: Prevent suspending and resuming DRM pipelines
>
> Xose Vazquez Perez 
> scsi: dh: add new rdac devices
>
> Xose Vazquez Perez 
> scsi: devinfo: apply to HP XP the same flags as Hitachi VSP
>
> Bart Van Assche 
> scsi: core: scsi_get_device_flags_keyed(): Always return device flags
>
> Michael Chan 
> bnxt_en: Don't print "Link speed -1 no longer supported" messages.
>
> Tobias Jordan 
> spi: sun6i: disable/unprepare clocks on remove
>
> Julien BOIBESSOT 
> tools/usbip: fixes build with musl libc toolchain
>
> Ben Greear 
> ath10k: fix invalid STS_CAP_OFFSET_MASK
>
> Limin Zhu 
> mwifiex: cfg80211: do not change virtual interface during scan processing
>
> Srinivas Kandagatla 
> clk: qcom: msm8916: fix mnd_width for codec_digcodec
>
> Monk Liu 
> drm/amdgpu:fix virtual dce bug
>
> Sara Sharon 
> iwlwifi: mvm: avoid dumping assert log when device is stopped
>
> Thomas Richter 
> perf annotate: Fix objdump comment parsing for Intel mov dissassembly
>
> Thomas Richter 
> perf annotate: Fix unnecessary memory allocation for s390x
>
> Takeshi Kihara 
> pinctrl: sh-pfc: r8a7795-es1: Fix MOD_SEL1 bit[25:24] to 0x3 when using 
> STP_ISEN_1_D
>
> Fabrizio Castro 
> pinctrl: sh-pfc: r8a7791: Add can_clk function
>
> Jernej Skrabec 
> drm/sun4i: Fix format mask in DE2 driver
>
> Axel Lin 
> pwm: stmpe: Fix wrong register offset for hwpwm=2 case
>
> Li Dongyang 
> scsi: ses: don't ask for diagnostic pages repeatedly during probe
>
> Monk Liu 
> drm/amdgpu:fix random missing of FLR NOTIFY
>
> Peter Ujfalusi 
> dmaengine: amba-pl08x: Use vchan_terminate_vdesc() instead of desc_free
>
> Peter Ujfalusi 
> dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

arm and arm64 build broken due to this patch for 4.14 and 4.15

drivers/dma/bcm2835-dma.c:815:3: error: implicit declaration of function
'vchan_terminate_vdesc' [-Werror=implicit-function-declaration]
   vchan_terminate_vdesc(>desc->vd);
   ^
cc1: some warnings being treated as errors

FYI, build using GCCVERSION = "linaro-6.2"

[PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.14.28-rc1

Anusha Srivatsa 
drm/i915/glk: Disable Guc and HuC on GLK

Sinan Kaya 
dmaengine: qcom_hidma: check pending interrupts

Arnd Bergmann 
IB/mlx5: revisit -Wmaybe-uninitialized warning

Mimi Zohar 
ima: relax requiring a file signature for new files with zero length

Davidlohr Bueso 
locking/locktorture: Fix num reader/writer corner cases

SeongJae Park 
rcutorture/configinit: Fix build directory error message

Mahesh Bandewar 
ipvlan: add L2 check for packets arriving via virtual devices

Christophe Leroy 
Fix misannotated out-of-line _copy_to_user()

Adrian Hunter 
mmc: mmc_test: Ensure command queue is disabled for testing

Dan Carpenter 
ASoC: nuc900: Fix a loop timeout test

Horia Geantă 
crypto: caam/qi - use correct print specifier for size_t

Luca Coelho 
mac80211: remove BUG() when interface type is invalid

Adiel Aloni 
mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED

Chris Wilson 
agp/intel: Flush all chipset writes after updating the GGTT

Geert Uytterhoeven 
arm64: dts: renesas: salvator-common: Add EthernetAVB PHY reset

Nicholas Piggin 
powerpc/64: Don't trace irqs-off at interrupt return to soft-disabled 
context

Josh Poimboeuf 
powerpc/modules: Don't try to restore r2 after a sibling call

Yong Zhao 
drm/amdkfd: Fix memory leaks in kfd topology

Stephen Hemminger 
veth: set peer GSO values

John Fastabend 
net: sched: drop qdisc_reset from dev_graft_qdisc

Toshiaki Makita 
virtio_net: Disable interrupts if napi_complete_done rescheduled napi

Gustavo A. R. Silva 
media: davinci: vpif_capture: add NULL check on devm_kzalloc return value

Dan Carpenter 
media: cpia2: Fix a couple off by one bugs

Heinz Mauelshagen 
dm raid: fix raid set size revalidation

Kieran Bingham 
media: vsp1: Prevent suspending and resuming DRM pipelines

Xose Vazquez Perez 
scsi: dh: add new rdac devices

Xose Vazquez Perez 
scsi: devinfo: apply to HP XP the same flags as Hitachi VSP

Bart Van Assche 
scsi: core: scsi_get_device_flags_keyed(): Always return device flags

Michael Chan 
bnxt_en: Don't print "Link speed -1 no longer supported" messages.

Tobias Jordan 
spi: sun6i: disable/unprepare clocks on remove

Julien BOIBESSOT 
tools/usbip: fixes build with musl libc toolchain

Ben Greear 
ath10k: fix invalid STS_CAP_OFFSET_MASK

Limin Zhu 
mwifiex: cfg80211: do not change virtual interface during scan processing

Srinivas Kandagatla 
clk: qcom: msm8916: fix mnd_width for codec_digcodec

Monk Liu 
drm/amdgpu:fix virtual dce bug

Sara Sharon 
iwlwifi: mvm: avoid dumping assert log when device is stopped

Thomas Richter 
perf annotate: Fix objdump comment parsing for Intel mov dissassembly

Thomas Richter 
perf annotate: Fix unnecessary memory allocation for s390x

Takeshi Kihara 
pinctrl: sh-pfc: r8a7795-es1: Fix MOD_SEL1 bit[25:24] to 0x3 when using 
STP_ISEN_1_D

Fabrizio Castro 
pinctrl: sh-pfc: r8a7791: Add can_clk function

Jernej Skrabec 
drm/sun4i: Fix format mask in DE2 driver

Axel Lin 
pwm: stmpe: Fix wrong register offset for 

[PATCH 4.14 000/109] 4.14.28-stable review

[Greg Kroah-Hartman]

This is the start of the stable review cycle for the 4.14.28 release.
There are 109 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 Sun Mar 18 15:22:53 UTC 2018.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.28-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.14.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.14.28-rc1

Anusha Srivatsa 
drm/i915/glk: Disable Guc and HuC on GLK

Sinan Kaya 
dmaengine: qcom_hidma: check pending interrupts

Arnd Bergmann 
IB/mlx5: revisit -Wmaybe-uninitialized warning

Mimi Zohar 
ima: relax requiring a file signature for new files with zero length

Davidlohr Bueso 
locking/locktorture: Fix num reader/writer corner cases

SeongJae Park 
rcutorture/configinit: Fix build directory error message

Mahesh Bandewar 
ipvlan: add L2 check for packets arriving via virtual devices

Christophe Leroy 
Fix misannotated out-of-line _copy_to_user()

Adrian Hunter 
mmc: mmc_test: Ensure command queue is disabled for testing

Dan Carpenter 
ASoC: nuc900: Fix a loop timeout test

Horia Geantă 
crypto: caam/qi - use correct print specifier for size_t

Luca Coelho 
mac80211: remove BUG() when interface type is invalid

Adiel Aloni 
mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED

Chris Wilson 
agp/intel: Flush all chipset writes after updating the GGTT

Geert Uytterhoeven 
arm64: dts: renesas: salvator-common: Add EthernetAVB PHY reset

Nicholas Piggin 
powerpc/64: Don't trace irqs-off at interrupt return to soft-disabled 
context

Josh Poimboeuf 
powerpc/modules: Don't try to restore r2 after a sibling call

Yong Zhao 
drm/amdkfd: Fix memory leaks in kfd topology

Stephen Hemminger 
veth: set peer GSO values

John Fastabend 
net: sched: drop qdisc_reset from dev_graft_qdisc

Toshiaki Makita 
virtio_net: Disable interrupts if napi_complete_done rescheduled napi

Gustavo A. R. Silva 
media: davinci: vpif_capture: add NULL check on devm_kzalloc return value

Dan Carpenter 
media: cpia2: Fix a couple off by one bugs

Heinz Mauelshagen 
dm raid: fix raid set size revalidation

Kieran Bingham 
media: vsp1: Prevent suspending and resuming DRM pipelines

Xose Vazquez Perez 
scsi: dh: add new rdac devices

Xose Vazquez Perez 
scsi: devinfo: apply to HP XP the same flags as Hitachi VSP

Bart Van Assche 
scsi: core: scsi_get_device_flags_keyed(): Always return device flags

Michael Chan 
bnxt_en: Don't print "Link speed -1 no longer supported" messages.

Tobias Jordan 
spi: sun6i: disable/unprepare clocks on remove

Julien BOIBESSOT 
tools/usbip: fixes build with musl libc toolchain

Ben Greear 
ath10k: fix invalid STS_CAP_OFFSET_MASK

Limin Zhu 
mwifiex: cfg80211: do not change virtual interface during scan processing

Srinivas Kandagatla 
clk: qcom: msm8916: fix mnd_width for codec_digcodec

Monk Liu 
drm/amdgpu:fix virtual dce bug

Sara Sharon 
iwlwifi: mvm: avoid dumping assert log when device is stopped

Thomas Richter 
perf annotate: Fix objdump comment parsing for Intel mov dissassembly

Thomas Richter 
perf annotate: Fix unnecessary memory allocation for s390x

Takeshi Kihara 
pinctrl: sh-pfc: r8a7795-es1: Fix MOD_SEL1 bit[25:24] to 0x3 when using 
STP_ISEN_1_D

Fabrizio Castro 
pinctrl: sh-pfc: r8a7791: Add can_clk function

Jernej Skrabec 
drm/sun4i: Fix format mask in DE2 driver

Axel Lin 
pwm: stmpe: Fix wrong register offset for hwpwm=2 case

Li Dongyang 
scsi: ses: don't ask for diagnostic pages repeatedly during probe

Monk Liu 
drm/amdgpu:fix random missing of FLR NOTIFY

Peter Ujfalusi 
dmaengine: amba-pl08x: Use vchan_terminate_vdesc() instead of desc_free

Peter Ujfalusi 
dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

Rafael J. Wysocki 
cpufreq: Fix governor module removal race

Manikanta Pubbisetty 
ath10k: update tdls teardown state to target

Peter Meerwald-Stadler 
iio: health: max30102: Add power enable parameter to get_temp function

Stefan Brüns 
iio: adc: ina2xx: Shift bus voltage register to mask flag bits

Philipp Zabel 
drm/etnaviv: make THERMAL selectable

Christophe JAILLET 
power: supply: ab8500_charger: Bail out in case of error in 
'ab8500_charger_init_hw_registers()'

Christophe JAILLET 
power: supply: ab8500_charger: Fix an error handling path

Tero Kristo 
clk: ti: clkctrl: add support for retrying failed init

Bjorn Andersson 
leds: pm8058: Silence pointer to integer size warning