Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-25 Thread Alexandre Belloni 
On 25/03/2017 at 12:27:05 +0100, Alexandre Belloni wrote:
> On 24/03/2017 at 21:15:28 -0700, Guenter Roeck wrote:
> > On 03/24/2017 05:10 PM, Kevin Hilman wrote:
> > > + at91 maintainers
> > > 
> 
> + Richard, Ludovic
> 
> > > kernelci.org bot  writes:
> > > 
> > > > stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 
> > > > conflict (v4.4.56-31-gbcd1e808ead3)
> > > > 
> > > > Full Boot Summary: 
> > > > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > > Full Build Summary: 
> > > > https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > > 
> > > > Tree: stable-rc
> > > > Branch: local/linux-4.4.y
> > > > Git Describe: v4.4.56-31-gbcd1e808ead3
> > > > Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
> > > > Git URL: 
> > > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > > Tested: 97 unique boards, 23 SoC families, 31 builds out of 202
> > > > 
> > > > Boot Regressions Detected:
> > > > 
> > > > arm:
> > > > 
> > > > multi_v7_defconfig+CONFIG_LKDTM=y:
> > > > at91-sama5d2_xplained:
> > > > lab-free-electrons: new failure (last pass: 
> > > > v4.4.51-27-g2ffd736763bc)
> > > 
> > > This one is definitely a new regression.  Hopefully the AT91 maintainers
> > > (now Cc'd) can have a closer look.
> > > 
> > 
> > 6b1d7b6f54c7 would be a candidate for a culprit.
> > 
> 
> Possibly and it may exercise a part of the logic that is not quite
> robust in atmel_set_ops(). Basically, atmel_rx_from_pdc() must not be
> chosen on sama5d2 (it has no PDC).
> 

I confirm the issue, commit 6b1d7b6f54c7 enables dma but
uart1 node doesn't have a "dmas" property so the driver thinks it has to
use PDC which is not correct. I'll try backporting
b1708b72a0959a032cd2eebb77fa9086ea3e0c84 which seems the proper way
forward.

> For reference, bootlog here:
> https://storage.kernelci.org/stable-rc/v4.4.56-31-gbcd1e808ead3/arm-multi_v7_defconfig+CONFIG_LKDTM=y/lab-free-electrons/boot-at91-sama5d2_xplained.html
> 
> > > > Conflicting Boot Failure Detected: (These likely are not failures as 
> > > > other labs are reporting PASS. Needs review.)
> > > > 
> > > > arm:
> > > > 
> > > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > > > at91-sama5d3_xplained:
> > > > lab-baylibre-seattle: PASS
> > > > lab-free-electrons: FAIL
> > > 
> > > @Alexandre: Because it's passing in my lab and failing in yours, I'm
> > > guessing this is still the UART overflow issue we've discussed before?
> > > 
> > > What's strange is that this defconfig in your lab seems to only be
> > > booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
> > > so I couldn't check if the problem still exists in mainline.
> > > 
> 
> It definitively exists but it is not solvable quickly. Either we run
> without DMA and we'll see the issue because CONFIG_PROVE_LOCKING makes
> the interrupt handling to slow and characters are dropped. Or, we add
> DMA and then CONFIG_PROVE_LOCKING will find a deadlock (that's a real
> deadlock, not a false positive) and the platform will not boot.
> 
> This only affects sama5d3 because it is the only SoC using the hdma
> controller with the uart IP. Earlier SoCs have a PDC and later SoCs are
> using the xdma controller.
> 
> This happens because atc_chain_complete() keeps the lock before calling
> the callback.  And atmel_complete_tx_dma() will call dmaengine function
> that will try to acquire the lock. No issue using the xdmac because
> there is no lock.
> 
> -- 
> Alexandre Belloni, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-25 Thread Alexandre Belloni 
On 25/03/2017 at 12:27:05 +0100, Alexandre Belloni wrote:
> On 24/03/2017 at 21:15:28 -0700, Guenter Roeck wrote:
> > On 03/24/2017 05:10 PM, Kevin Hilman wrote:
> > > + at91 maintainers
> > > 
> 
> + Richard, Ludovic
> 
> > > kernelci.org bot  writes:
> > > 
> > > > stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 
> > > > conflict (v4.4.56-31-gbcd1e808ead3)
> > > > 
> > > > Full Boot Summary: 
> > > > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > > Full Build Summary: 
> > > > https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > > 
> > > > Tree: stable-rc
> > > > Branch: local/linux-4.4.y
> > > > Git Describe: v4.4.56-31-gbcd1e808ead3
> > > > Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
> > > > Git URL: 
> > > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > > Tested: 97 unique boards, 23 SoC families, 31 builds out of 202
> > > > 
> > > > Boot Regressions Detected:
> > > > 
> > > > arm:
> > > > 
> > > > multi_v7_defconfig+CONFIG_LKDTM=y:
> > > > at91-sama5d2_xplained:
> > > > lab-free-electrons: new failure (last pass: 
> > > > v4.4.51-27-g2ffd736763bc)
> > > 
> > > This one is definitely a new regression.  Hopefully the AT91 maintainers
> > > (now Cc'd) can have a closer look.
> > > 
> > 
> > 6b1d7b6f54c7 would be a candidate for a culprit.
> > 
> 
> Possibly and it may exercise a part of the logic that is not quite
> robust in atmel_set_ops(). Basically, atmel_rx_from_pdc() must not be
> chosen on sama5d2 (it has no PDC).
> 

I confirm the issue, commit 6b1d7b6f54c7 enables dma but
uart1 node doesn't have a "dmas" property so the driver thinks it has to
use PDC which is not correct. I'll try backporting
b1708b72a0959a032cd2eebb77fa9086ea3e0c84 which seems the proper way
forward.

> For reference, bootlog here:
> https://storage.kernelci.org/stable-rc/v4.4.56-31-gbcd1e808ead3/arm-multi_v7_defconfig+CONFIG_LKDTM=y/lab-free-electrons/boot-at91-sama5d2_xplained.html
> 
> > > > Conflicting Boot Failure Detected: (These likely are not failures as 
> > > > other labs are reporting PASS. Needs review.)
> > > > 
> > > > arm:
> > > > 
> > > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > > > at91-sama5d3_xplained:
> > > > lab-baylibre-seattle: PASS
> > > > lab-free-electrons: FAIL
> > > 
> > > @Alexandre: Because it's passing in my lab and failing in yours, I'm
> > > guessing this is still the UART overflow issue we've discussed before?
> > > 
> > > What's strange is that this defconfig in your lab seems to only be
> > > booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
> > > so I couldn't check if the problem still exists in mainline.
> > > 
> 
> It definitively exists but it is not solvable quickly. Either we run
> without DMA and we'll see the issue because CONFIG_PROVE_LOCKING makes
> the interrupt handling to slow and characters are dropped. Or, we add
> DMA and then CONFIG_PROVE_LOCKING will find a deadlock (that's a real
> deadlock, not a false positive) and the platform will not boot.
> 
> This only affects sama5d3 because it is the only SoC using the hdma
> controller with the uart IP. Earlier SoCs have a PDC and later SoCs are
> using the xdma controller.
> 
> This happens because atc_chain_complete() keeps the lock before calling
> the callback.  And atmel_complete_tx_dma() will call dmaengine function
> that will try to acquire the lock. No issue using the xdmac because
> there is no lock.
> 
> -- 
> Alexandre Belloni, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-25 Thread Alexandre Belloni 
On 24/03/2017 at 21:15:28 -0700, Guenter Roeck wrote:
> On 03/24/2017 05:10 PM, Kevin Hilman wrote:
> > + at91 maintainers
> > 

+ Richard, Ludovic

> > kernelci.org bot  writes:
> > 
> > > stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 
> > > conflict (v4.4.56-31-gbcd1e808ead3)
> > > 
> > > Full Boot Summary: 
> > > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > Full Build Summary: 
> > > https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > 
> > > Tree: stable-rc
> > > Branch: local/linux-4.4.y
> > > Git Describe: v4.4.56-31-gbcd1e808ead3
> > > Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
> > > Git URL: 
> > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > Tested: 97 unique boards, 23 SoC families, 31 builds out of 202
> > > 
> > > Boot Regressions Detected:
> > > 
> > > arm:
> > > 
> > > multi_v7_defconfig+CONFIG_LKDTM=y:
> > > at91-sama5d2_xplained:
> > > lab-free-electrons: new failure (last pass: 
> > > v4.4.51-27-g2ffd736763bc)
> > 
> > This one is definitely a new regression.  Hopefully the AT91 maintainers
> > (now Cc'd) can have a closer look.
> > 
> 
> 6b1d7b6f54c7 would be a candidate for a culprit.
> 

Possibly and it may exercise a part of the logic that is not quite
robust in atmel_set_ops(). Basically, atmel_rx_from_pdc() must not be
chosen on sama5d2 (it has no PDC).

For reference, bootlog here:
https://storage.kernelci.org/stable-rc/v4.4.56-31-gbcd1e808ead3/arm-multi_v7_defconfig+CONFIG_LKDTM=y/lab-free-electrons/boot-at91-sama5d2_xplained.html

> > > Conflicting Boot Failure Detected: (These likely are not failures as 
> > > other labs are reporting PASS. Needs review.)
> > > 
> > > arm:
> > > 
> > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > > at91-sama5d3_xplained:
> > > lab-baylibre-seattle: PASS
> > > lab-free-electrons: FAIL
> > 
> > @Alexandre: Because it's passing in my lab and failing in yours, I'm
> > guessing this is still the UART overflow issue we've discussed before?
> > 
> > What's strange is that this defconfig in your lab seems to only be
> > booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
> > so I couldn't check if the problem still exists in mainline.
> > 

It definitively exists but it is not solvable quickly. Either we run
without DMA and we'll see the issue because CONFIG_PROVE_LOCKING makes
the interrupt handling to slow and characters are dropped. Or, we add
DMA and then CONFIG_PROVE_LOCKING will find a deadlock (that's a real
deadlock, not a false positive) and the platform will not boot.

This only affects sama5d3 because it is the only SoC using the hdma
controller with the uart IP. Earlier SoCs have a PDC and later SoCs are
using the xdma controller.

This happens because atc_chain_complete() keeps the lock before calling
the callback.  And atmel_complete_tx_dma() will call dmaengine function
that will try to acquire the lock. No issue using the xdmac because
there is no lock.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-25 Thread Alexandre Belloni 
On 24/03/2017 at 21:15:28 -0700, Guenter Roeck wrote:
> On 03/24/2017 05:10 PM, Kevin Hilman wrote:
> > + at91 maintainers
> > 

+ Richard, Ludovic

> > kernelci.org bot  writes:
> > 
> > > stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 
> > > conflict (v4.4.56-31-gbcd1e808ead3)
> > > 
> > > Full Boot Summary: 
> > > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > Full Build Summary: 
> > > https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
> > > 
> > > Tree: stable-rc
> > > Branch: local/linux-4.4.y
> > > Git Describe: v4.4.56-31-gbcd1e808ead3
> > > Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
> > > Git URL: 
> > > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > Tested: 97 unique boards, 23 SoC families, 31 builds out of 202
> > > 
> > > Boot Regressions Detected:
> > > 
> > > arm:
> > > 
> > > multi_v7_defconfig+CONFIG_LKDTM=y:
> > > at91-sama5d2_xplained:
> > > lab-free-electrons: new failure (last pass: 
> > > v4.4.51-27-g2ffd736763bc)
> > 
> > This one is definitely a new regression.  Hopefully the AT91 maintainers
> > (now Cc'd) can have a closer look.
> > 
> 
> 6b1d7b6f54c7 would be a candidate for a culprit.
> 

Possibly and it may exercise a part of the logic that is not quite
robust in atmel_set_ops(). Basically, atmel_rx_from_pdc() must not be
chosen on sama5d2 (it has no PDC).

For reference, bootlog here:
https://storage.kernelci.org/stable-rc/v4.4.56-31-gbcd1e808ead3/arm-multi_v7_defconfig+CONFIG_LKDTM=y/lab-free-electrons/boot-at91-sama5d2_xplained.html

> > > Conflicting Boot Failure Detected: (These likely are not failures as 
> > > other labs are reporting PASS. Needs review.)
> > > 
> > > arm:
> > > 
> > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > > at91-sama5d3_xplained:
> > > lab-baylibre-seattle: PASS
> > > lab-free-electrons: FAIL
> > 
> > @Alexandre: Because it's passing in my lab and failing in yours, I'm
> > guessing this is still the UART overflow issue we've discussed before?
> > 
> > What's strange is that this defconfig in your lab seems to only be
> > booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
> > so I couldn't check if the problem still exists in mainline.
> > 

It definitively exists but it is not solvable quickly. Either we run
without DMA and we'll see the issue because CONFIG_PROVE_LOCKING makes
the interrupt handling to slow and characters are dropped. Or, we add
DMA and then CONFIG_PROVE_LOCKING will find a deadlock (that's a real
deadlock, not a false positive) and the platform will not boot.

This only affects sama5d3 because it is the only SoC using the hdma
controller with the uart IP. Earlier SoCs have a PDC and later SoCs are
using the xdma controller.

This happens because atc_chain_complete() keeps the lock before calling
the callback.  And atmel_complete_tx_dma() will call dmaengine function
that will try to acquire the lock. No issue using the xdmac because
there is no lock.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Guenter Roeck 

On 03/24/2017 10:58 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.4.57 release.
There are 30 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 26 15:12:02 UTC 2017.
Anything received after that time might be too late.



Build results:
total: 149 pass: 149 fail: 0
Qemu test results:
total: 115 pass: 115 fail: 0

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

Guenter

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Guenter Roeck 

On 03/24/2017 10:58 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 4.4.57 release.
There are 30 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 26 15:12:02 UTC 2017.
Anything received after that time might be too late.



Build results:
total: 149 pass: 149 fail: 0
Qemu test results:
total: 115 pass: 115 fail: 0

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

Guenter

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Guenter Roeck 

On 03/24/2017 05:10 PM, Kevin Hilman wrote:

+ at91 maintainers

kernelci.org bot  writes:


stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 conflict 
(v4.4.56-31-gbcd1e808ead3)

Full Boot Summary: 
https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
Full Build Summary: 
https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/

Tree: stable-rc
Branch: local/linux-4.4.y
Git Describe: v4.4.56-31-gbcd1e808ead3
Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
Git URL: 
http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 97 unique boards, 23 SoC families, 31 builds out of 202

Boot Regressions Detected:

arm:

multi_v7_defconfig+CONFIG_LKDTM=y:
at91-sama5d2_xplained:
lab-free-electrons: new failure (last pass: 
v4.4.51-27-g2ffd736763bc)


This one is definitely a new regression.  Hopefully the AT91 maintainers
(now Cc'd) can have a closer look.



6b1d7b6f54c7 would be a candidate for a culprit.

Guenter


[...]


Conflicting Boot Failure Detected: (These likely are not failures as other labs 
are reporting PASS. Needs review.)

arm:

multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
at91-sama5d3_xplained:
lab-baylibre-seattle: PASS
lab-free-electrons: FAIL


@Alexandre: Because it's passing in my lab and failing in yours, I'm
guessing this is still the UART overflow issue we've discussed before?

What's strange is that this defconfig in your lab seems to only be
booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
so I couldn't check if the problem still exists in mainline.

Kevin

[1] 
https://kernelci.org/boot/at91-sama5d3_xplained/?CONFIG_PROVE_LOCKING

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Guenter Roeck 

On 03/24/2017 05:10 PM, Kevin Hilman wrote:

+ at91 maintainers

kernelci.org bot  writes:


stable-rc boot: 496 boots: 1 failed, 492 passed with 2 offline, 1 conflict 
(v4.4.56-31-gbcd1e808ead3)

Full Boot Summary: 
https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/
Full Build Summary: 
https://kernelci.org/build/stable-rc/kernel/v4.4.56-31-gbcd1e808ead3/

Tree: stable-rc
Branch: local/linux-4.4.y
Git Describe: v4.4.56-31-gbcd1e808ead3
Git Commit: bcd1e808ead359a9af8476025d8b8a5349796dcd
Git URL: 
http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 97 unique boards, 23 SoC families, 31 builds out of 202

Boot Regressions Detected:

arm:

multi_v7_defconfig+CONFIG_LKDTM=y:
at91-sama5d2_xplained:
lab-free-electrons: new failure (last pass: 
v4.4.51-27-g2ffd736763bc)


This one is definitely a new regression.  Hopefully the AT91 maintainers
(now Cc'd) can have a closer look.



6b1d7b6f54c7 would be a candidate for a culprit.

Guenter


[...]


Conflicting Boot Failure Detected: (These likely are not failures as other labs 
are reporting PASS. Needs review.)

arm:

multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
at91-sama5d3_xplained:
lab-baylibre-seattle: PASS
lab-free-electrons: FAIL


@Alexandre: Because it's passing in my lab and failing in yours, I'm
guessing this is still the UART overflow issue we've discussed before?

What's strange is that this defconfig in your lab seems to only be
booting for stable/linux-4.4.y[1] but not mailine or newer stable trees,
so I couldn't check if the problem still exists in mainline.

Kevin

[1] 
https://kernelci.org/boot/at91-sama5d3_xplained/?CONFIG_PROVE_LOCKING

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Shuah Khan 
On 03/24/2017 11:58 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.57 release.
> There are 30 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 26 15:12:02 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.57-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
> 

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

Re: [PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Shuah Khan 
On 03/24/2017 11:58 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.57 release.
> There are 30 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 26 15:12:02 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.57-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
> 

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

[PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 4.4.57 release.
There are 30 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 26 15:12:02 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.57-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.57-rc1

Theodore Ts'o 
ext4: fix fencepost in s_first_meta_bg validation

Tahsin Erdogan 
percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

Andreas Gruenbacher 
gfs2: Avoid alignment hole in struct lm_lockname

Johan Hovold 
isdn/gigaset: fix NULL-deref at probe

Max Lohrmann 
target: Fix VERIFY_16 handling in sbc_parse_cdb

Chris Leech 
scsi: libiscsi: add lock around task lists to fix list corruption regression

Anton Blanchard 
scsi: lpfc: Add shutdown method for kexec

Nicholas Bellinger 
target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

Shaohua Li 
md/raid1/10: fix potential deadlock

Michael Ellerman 
powerpc/boot: Fix zImage TOC alignment

Rafael J. Wysocki 
cpufreq: Fix and clean up show_cpuinfo_cur_freq()

Peter Zijlstra 
perf/core: Fix event inheritance on fork()

Linus Torvalds 
give up on gcc ilog2() constant optimizations

Andi Kleen 
kernek/fork.c: allocate idle task for a CPU always on its local node

Vitaly Kuznetsov 
hv_netvsc: use skb_get_hash() instead of a homegrown implementation

Jason Gunthorpe 
tpm_tis: Use devm_free_irq not free_irq

Dave Airlie 
drm/amdgpu: add missing irq.h include

Sebastian Ott 
s390/pci: fix use after free in dma_init

Thomas Huth 
KVM: PPC: Book3S PR: Fix illegal opcode emulation

Ross Lagerwall 
xen/qspinlock: Don't kick CPU if IRQ is not initialized

Vitaly Kuznetsov 
Drivers: hv: avoid vfree() on crash

Vitaly Kuznetsov 
Drivers: hv: balloon: don't crash when memory is added in non-sorted order

Mika Westerberg 
pinctrl: cherryview: Do not mask all interrupts in probe

Alex Hung 
ACPI / video: skip evaluating _DOD when it does not exist

Manoj N. Kumar 
cxlflash: Increase cmd_per_lun for better throughput

Wang, Rui Y 
crypto: mcryptd - Fix load failure

Wang, Rui Y 
crypto: cryptd - Assign statesize properly

Wang, Rui Y 
crypto: ghash-clmulni - Fix load failure

Alan Stern 
USB: don't free bandwidth_mutex too early

Chris Bainbridge 
usb: core: hub: hub_port_init lock controller instead of bus


-

Diffstat:

 Makefile   |  4 +-
 arch/powerpc/boot/zImage.lds.S |  1 +
 arch/powerpc/kvm/emulate.c |  1 -
 arch/s390/pci/pci_dma.c| 16 ---
 arch/x86/crypto/ghash-clmulni-intel_glue.c | 26 
 arch/x86/xen/spinlock.c|  6 +++
 crypto/cryptd.c|  1 +
 crypto/mcryptd.c   |  1 +
 drivers/acpi/acpi_video.c  |  3 ++
 drivers/char/tpm/tpm_tis.c |  2 +-
 drivers/cpufreq/cpufreq.c  |  8 ++--
 drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c|  1 +
 drivers/hv/hv.c|  8 ++--
 drivers/hv/hv_balloon.c|  4 +-
 drivers/hv/hyperv_vmbus.h  |  2 +-
 drivers/hv/vmbus_drv.c |  8 ++--
 drivers/isdn/gigaset/bas-gigaset.c |  3 ++
 drivers/md/raid10.c| 18 
 drivers/net/hyperv/netvsc_drv.c| 67 ++
 drivers/pinctrl/intel/pinctrl-cherryview.c |  5 +--
 drivers/scsi/cxlflash/common.h |  8 ++--
 drivers/scsi/cxlflash/main.c   |  2 +-
 drivers/scsi/libiscsi.c| 26 +++-
 drivers/scsi/lpfc/lpfc_init.c  |  1 +
 drivers/target/target_core_pscsi.c | 47 ++---
 drivers/target/target_core_sbc.c

[PATCH 4.4 00/30] 4.4.57-stable review

2017-03-24 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 4.4.57 release.
There are 30 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 26 15:12:02 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.57-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.57-rc1

Theodore Ts'o 
ext4: fix fencepost in s_first_meta_bg validation

Tahsin Erdogan 
percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

Andreas Gruenbacher 
gfs2: Avoid alignment hole in struct lm_lockname

Johan Hovold 
isdn/gigaset: fix NULL-deref at probe

Max Lohrmann 
target: Fix VERIFY_16 handling in sbc_parse_cdb

Chris Leech 
scsi: libiscsi: add lock around task lists to fix list corruption regression

Anton Blanchard 
scsi: lpfc: Add shutdown method for kexec

Nicholas Bellinger 
target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

Shaohua Li 
md/raid1/10: fix potential deadlock

Michael Ellerman 
powerpc/boot: Fix zImage TOC alignment

Rafael J. Wysocki 
cpufreq: Fix and clean up show_cpuinfo_cur_freq()

Peter Zijlstra 
perf/core: Fix event inheritance on fork()

Linus Torvalds 
give up on gcc ilog2() constant optimizations

Andi Kleen 
kernek/fork.c: allocate idle task for a CPU always on its local node

Vitaly Kuznetsov 
hv_netvsc: use skb_get_hash() instead of a homegrown implementation

Jason Gunthorpe 
tpm_tis: Use devm_free_irq not free_irq

Dave Airlie 
drm/amdgpu: add missing irq.h include

Sebastian Ott 
s390/pci: fix use after free in dma_init

Thomas Huth 
KVM: PPC: Book3S PR: Fix illegal opcode emulation

Ross Lagerwall 
xen/qspinlock: Don't kick CPU if IRQ is not initialized

Vitaly Kuznetsov 
Drivers: hv: avoid vfree() on crash

Vitaly Kuznetsov 
Drivers: hv: balloon: don't crash when memory is added in non-sorted order

Mika Westerberg 
pinctrl: cherryview: Do not mask all interrupts in probe

Alex Hung 
ACPI / video: skip evaluating _DOD when it does not exist

Manoj N. Kumar 
cxlflash: Increase cmd_per_lun for better throughput

Wang, Rui Y 
crypto: mcryptd - Fix load failure

Wang, Rui Y 
crypto: cryptd - Assign statesize properly

Wang, Rui Y 
crypto: ghash-clmulni - Fix load failure

Alan Stern 
USB: don't free bandwidth_mutex too early

Chris Bainbridge 
usb: core: hub: hub_port_init lock controller instead of bus


-

Diffstat:

 Makefile   |  4 +-
 arch/powerpc/boot/zImage.lds.S |  1 +
 arch/powerpc/kvm/emulate.c |  1 -
 arch/s390/pci/pci_dma.c| 16 ---
 arch/x86/crypto/ghash-clmulni-intel_glue.c | 26 
 arch/x86/xen/spinlock.c|  6 +++
 crypto/cryptd.c|  1 +
 crypto/mcryptd.c   |  1 +
 drivers/acpi/acpi_video.c  |  3 ++
 drivers/char/tpm/tpm_tis.c |  2 +-
 drivers/cpufreq/cpufreq.c  |  8 ++--
 drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c|  1 +
 drivers/hv/hv.c|  8 ++--
 drivers/hv/hv_balloon.c|  4 +-
 drivers/hv/hyperv_vmbus.h  |  2 +-
 drivers/hv/vmbus_drv.c |  8 ++--
 drivers/isdn/gigaset/bas-gigaset.c |  3 ++
 drivers/md/raid10.c| 18 
 drivers/net/hyperv/netvsc_drv.c| 67 ++
 drivers/pinctrl/intel/pinctrl-cherryview.c |  5 +--
 drivers/scsi/cxlflash/common.h |  8 ++--
 drivers/scsi/cxlflash/main.c   |  2 +-
 drivers/scsi/libiscsi.c| 26 +++-
 drivers/scsi/lpfc/lpfc_init.c  |  1 +
 drivers/target/target_core_pscsi.c | 47 ++---
 drivers/target/target_core_sbc.c   | 10 -
 drivers/usb/core/hcd.c | 26 
 drivers/usb/core/hub.c |  8 ++--
 fs/ext4/super.c|  2 +-
 fs/gfs2/incore.h   |  2 +-
 include/linux/log2.h   | 13 +-
 include/linux/usb.h|  3 +-
 include/linux/usb/hcd.h|  1 +
 include/scsi/libiscsi.h|  1 +
 kernel/events/core.c   |  5 ++-
 kernel/fork.c  | 15 ---
 mm/percpu.c|  5 ++-
 tools/include/linux/log2.h | 13 +-
 38 files changed, 193 insertions(+),