Re: [PATCH 4.4 00/58] 4.4.81-stable review

[Guenter Roeck <linux@roeck-us.net>]

On Wed, Aug 09, 2017 at 12:41:12PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.81 release.
> There are 58 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 Fri Aug 11 19:41:25 UTC 2017.
> Anything received after that time might be too late.
> 

Bisect results for the nios2 crash:

# bad: [a7b4f512d9ce04f1c4133838371a2f3a8a31d323] Linux 4.4.81-rc1
# good: [09e69607e47ce9f422da4310c68d7a9b399d4f8c] Linux 4.4.80
git bisect start 'HEAD' 'v4.4.80'
# good: [a3bfc7a6f7e2a469d261d50a4bd4a9797ccc38d8] openvswitch: fix potential out of bound access in parse_ct
git bisect good a3bfc7a6f7e2a469d261d50a4bd4a9797ccc38d8
# bad: [fec6ca05cae44222e0d778ae9f2662de4c7da6e8] sh_eth: R8A7740 supports packet shecksumming
git bisect bad fec6ca05cae44222e0d778ae9f2662de4c7da6e8
# good: [f9a6e277a4290a30aaeb43b74ec78fa0ea8b125a] sctp: don't dereference ptr before leaving _sctp_walk_{params, errors}()
git bisect good f9a6e277a4290a30aaeb43b74ec78fa0ea8b125a
# bad: [9a8cf5c3ae379556f25c47f0e26276101045c421] xen-netback: correctly schedule rate-limited queues
git bisect bad 9a8cf5c3ae379556f25c47f0e26276101045c421
# good: [eded791aa722d68d443c1722489339ba52930e44] net/mlx5: Fix command bad flow on command entry allocation failure
git bisect good eded791aa722d68d443c1722489339ba52930e44
# bad: [75f7f0b78d6ba311c902871649561fb6a1a66956] net: phy: Correctly process PHY_HALTED in phy_stop_machine()
git bisect bad 75f7f0b78d6ba311c902871649561fb6a1a66956
# first bad commit: [75f7f0b78d6ba311c902871649561fb6a1a66956] net: phy: Correctly process PHY_HALTED in phy_stop_machine()

Reverting the offending patch fixes the problem. Reverting the same patch
in v4.9.y fixes the problem there as well.

I did a wild guess and found that applying

7b9a88a390da net: phy: Fix PHY unbind crash

instead of reverting the offending patch fixes the problem in both
v4.4.y and v4.9.y.

Copying Florian and David for additional input.

Guenter