linux-kernel - Re: [PATCH 3.10 00/86] 3.10.39-stable review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 04 May 2014 11:15:44 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org
CC:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	satoru.takeuchi@...il.com, shuah.kh@...sung.com,
	stable@...r.kernel.org
Subject: Re: [PATCH 3.10 00/86] 3.10.39-stable review

On 05/04/2014 08:40 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.39 release.
> There are 86 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 Tue May  6 15:41:13 UTC 2014.
> Anything received after that time might be too late.
>

I am still seeing build failures, even with x86_64 (both allmodconfig and
allyesconfig fail).
	total: 127 pass: 113 skipped: 4 fail: 10

drivers/usb/musb/musb_core.c: In function 'musb_stage0_irq':
drivers/usb/musb/musb_core.c:673:26: error: 'struct musb' has no member named 'hcd'

Problem is due to 'usb: musb: avoid NULL pointer dereference'.
A brief glance into the code suggests that the patch will require an explicit
back-port to 3.10.

Greg, I suspect you might not have USB_MUSB_HDRC enabled in your builds.

On the plus side, qemu builds and tests all passed ... but I guess that only
shows the somewhat limited scope of those tests :-(.

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/