linux-kernel - Re: [PATCH 3.10 000/319] 3.10.105-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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 6 Feb 2017 07:30:44 +0100
From:   Willy Tarreau <w@....eu>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 3.10 000/319] 3.10.105-stable review

Hi Guenter,

On Sun, Feb 05, 2017 at 07:12:58PM -0800, Guenter Roeck wrote:
> On 02/05/2017 11:09 AM, Willy Tarreau wrote:
> > This is the start of the stable review cycle for the 3.10.105 release.
> > 
> > NOTE! This series is quite large as I've caught up with many pending fixes
> > that were submitted for -stable long ago and that I had been holding on
> > since 3.10.103 due to limited time. Most fixes address stability issues
> > in crypto, net, usb, scsi, kvm, random info leaks, and risks of oopses
> > in various subsystems. My pending queue is now empty.
> > 
> > It builds fine here on i586 and x86_64 for allmodconfig and on armv7 with
> > mvebu_defconfig.
> > 
> > All patches will be posted as a response to this one. If anyone has any
> > issue with these being applied, please let me know. If anyone thinks some
> > important patches are missing and should be added prior to the release,
> > please report them quickly with their respective mainline commit IDs.
> > 
> 
> Build results:
> 	total: 124 pass: 98 fail: 26
> Failed builds:
> 	alpha:defconfig
> 	alpha:allmodconfig
> 	arc:tb10x_defconfig
> 	avr32:defconfig
> 	avr32:merisc_defconfig
> 	avr32:atngw100mkii_evklcd101_defconfig
> 	blackfin:defconfig
> 	blackfin:BF561-EZKIT-SMP_defconfig
> 	cris:etrax-100lx_defconfig
> 	frv:defconfig
> 	hexagon:defconfig
> 	m32r:defconfig
> 	m68k:defconfig
> 	m68k:allmodconfig
> 	m68k:sun3_defconfig
> 	microblaze:mmu_defconfig
> 	microblaze:nommu_defconfig
> 	parisc:defconfig
> 	parisc:a500_defconfig
> 	score:defconfig
> 	sh:dreamcast_defconfig
> 	sh:shx3_defconfig
> 	tile:tilegx_defconfig
> 	unicore32:defconfig
> 	xtensa:defconfig
> 	xtensa:allmodconfig
> 
> Qemu test results:
> 	total: 83 pass: 60 fail: 23
> Failed tests:
> 	alpha:defconfig
> 	microblaze:microblaze_defconfig
> 	microblaze:microblazeel_defconfig
> 	sh:rts7751r2dplus_defconfig
> 	sh:rts7751r2dplus_defconfig
> 	sparc32:SPARCClassic:nosmp:sparc32_defconfig
> 	sparc32:SPARCbook:nosmp:sparc32_defconfig
> 	sparc32:SS-4:nosmp:sparc32_defconfig
> 	sparc32:SS-5:nosmp:sparc32_defconfig
> 	sparc32:SS-10:nosmp:sparc32_defconfig
> 	sparc32:SS-20:nosmp:sparc32_defconfig
> 	sparc32:SS-600MP:nosmp:sparc32_defconfig
> 	sparc32:LX:nosmp:sparc32_defconfig
> 	sparc32:Voyager:nosmp:sparc32_defconfig
> 	sparc32:SPARCClassic:smp:sparc32_defconfig
> 	sparc32:SPARCbook:smp:sparc32_defconfig
> 	sparc32:SS-4:smp:sparc32_defconfig
> 	sparc32:SS-5:smp:sparc32_defconfig
> 	sparc32:SS-10:smp:sparc32_defconfig
> 	sparc32:SS-20:smp:sparc32_defconfig
> 	sparc32:SS-600MP:smp:sparc32_defconfig
> 	sparc32:LX:smp:sparc32_defconfig
> 	sparc32:Voyager:smp:sparc32_defconfig
> 
> As far as I can see, the failures are all due to the following build failure.
> 
> ipc/sem.c: In function 'complexmode_tryleave':
> ipc/sem.c:317: error: implicit declaration of function 'smp_store_release'
> ipc/sem.c: In function 'sem_lock':
> ipc/sem.c:370: error: implicit declaration of function 'smp_load_acquire'

Thanks a lot. I'll revert these ones and revert the patch that required
this one, it'll be safer.

Many thanks,
Willy