From: Willy Tarreau <w@1wt.eu>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 3.10 000/319] 3.10.105-stable review
Date: Mon, 6 Feb 2017 07:30:44 +0100 [thread overview]
Message-ID: <20170206063044.GA9533@1wt.eu> (raw)
In-Reply-To: <ff7144e8-abcb-fbf0-6921-ff82e7518c0d@roeck-us.net>
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
next prev parent reply other threads:[~2017-02-06 6:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 19:09 [PATCH 3.10 000/319] 3.10.105-stable review Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 001/319] sched/core: Fix a race between try_to_wake_up() and a woken up task Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 002/319] sched/core: Fix an SMP ordering race in try_to_wake_up() vs. schedule() Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 003/319] crypto: algif_skcipher - Require setkey before accept(2) Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 004/319] crypto: af_alg - Disallow bind/setkey/... after accept(2) Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 005/319] crypto: af_alg - Add nokey compatibility path Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 006/319] crypto: algif_skcipher " Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 007/319] crypto: hash - Add crypto_ahash_has_setkey Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 008/319] crypto: shash - Fix has_key setting Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 009/319] crypto: algif_hash - Require setkey before accept(2) Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 010/319] crypto: skcipher - Add crypto_skcipher_has_setkey Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 011/319] crypto: algif_skcipher - Add key check exception for cipher_null Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 012/319] crypto: af_alg - Allow af_af_alg_release_parent to be called on nokey path Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 013/319] crypto: algif_hash - Remove custom release parent function Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 014/319] crypto: algif_skcipher " Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 015/319] crypto: af_alg - Forbid bind(2) when nokey child sockets are present Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 016/319] crypto: algif_hash - Fix race condition in hash_check_key Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 017/319] crypto: algif_skcipher - Fix race condition in skcipher_check_key Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 018/319] crypto: algif_skcipher - Load TX SG list after waiting Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 019/319] crypto: cryptd - initialize child shash_desc on import Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 020/319] crypto: skcipher - Fix blkcipher walk OOM crash Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 021/319] crypto: gcm - Fix IV buffer size in crypto_gcm_setkey Willy Tarreau
2017-02-05 19:09 ` [PATCH 3.10 022/319] MIPS: KVM: Fix unused variable build warning Willy Tarreau
2017-02-06 3:12 ` [PATCH 3.10 000/319] 3.10.105-stable review Guenter Roeck
2017-02-06 6:30 ` Willy Tarreau [this message]
2017-02-06 8:13 ` Willy Tarreau
2017-02-06 14:46 ` Guenter Roeck
2017-02-06 15:10 ` Willy Tarreau
2017-02-06 22:48 ` Willy Tarreau
2017-02-06 23:48 ` Guenter Roeck
2017-02-07 4:56 ` Guenter Roeck
2017-02-07 6:39 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170206063044.GA9533@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox