Re: [PATCH 3.18 00/47] 3.18.132-stable review

[Guenter Roeck]

On 1/11/19 6:07 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.132 release.
> There are 47 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 Jan 13 13:09:31 UTC 2019.
> Anything received after that time might be too late.


Build results:
	total: 155 pass: 155 fail: 0
Qemu test results:
	total: 217 pass: 202 fail: 15
Failed tests:
	sparc32:SPARCClassic:nosmp:scsi:hd
	sparc32:SPARCbook:nosmp:scsi:cd
	sparc32:LX:nosmp:noapc:scsi:hd
	sparc32:SS-4:nosmp:initrd
	sparc32:SS-5:nosmp:scsi:hd
	sparc32:SS-10:nosmp:scsi:cd
	sparc32:SS-20:nosmp:scsi:hd
	sparc32:SS-600MP:nosmp:scsi:hd
	sparc32:Voyager:nosmp:noapc:scsi:hd
	sparc32:SS-4:smp:scsi:hd
	sparc32:SS-5:smp:scsi:cd
	sparc32:SS-10:smp:scsi:hd
	sparc32:SS-20:smp:scsi:hd
	sparc32:SS-600MP:smp:scsi:hd
	sparc32:Voyager:smp:noapc:scsi:hd

The failed sparc32 tests are really nothing new, but were discovered due
to more extensive testing. Observed behavior is a boot hang. sparc32 images
in v3.18.y (and v3.16.y) have probably been non-functional since commit
16c193364b4d ("sparc: Harden signal return frame checks."). The problem
was fixed upstream with commit 07b5ab3f71d3 ("sparc32: Fix inverted
invalid_frame_pointer checks on sigreturns"), and applying the same
commit to v3.18.y (and v3.16.y) fixes the problem.

Guenter