linux-kernel - RE: regression: SCSI/SATA failure

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:   Mon, 5 Mar 2018 14:41:24 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Thorsten Leemhuis' <regressions@...mhuis.info>,
        "dedekind1@...il.com" <dedekind1@...il.com>,
        Christoph Hellwig <hch@....de>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Thomas Gleixner" <tglx@...utronix.de>,
        Christian Borntraeger <borntraeger@...ibm.com>,
        Stefan Haberland <sth@...ux.vnet.ibm.com>,
        "Jens Axboe" <axboe@...nel.dk>,
        "Herring, Jan-kristian Augustin" 
        <jan-kristian.augustin.herring@...el.com>
Subject: RE: regression: SCSI/SATA failure

From: Thorsten Leemhuis
> Hi! On 22.02.2018 15:57, Artem Bityutskiy wrote:
> > On Thu, 2018-02-22 at 16:54 +0200, Artem Bityutskiy wrote:
> >> one of our test box Skylake servers does not boot with v4.16-rcX.
> >> Bisection lead us to this commit:
> >> 84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
> >> Reverting this single commit fixes the problem.
> 
> Artem, is this issue still happening? I still have it in my list of
> regressions. Side note: I accidentally noticed people continue working
> in the area that 84676c1f21e8 touched;  see
> https://marc.info/?l=linux-block&m=152021971313902&w=2 ("[PATCH V2 5/5]
> genirq/affinity: irq vector spread among online CPUs as far as
> possible"). I wonder if that might be related in any way. Ciao, Thorsten

Hmmm.... I can think of some workloads where you really don't want some
cpu taking any interrupts at all (well as few as possible).
Think of workloads where process affinities are used to ensure that only
a few specific processes run on certain cpus.
The last thing you want then is interrupt load sharing and/or per cpu
ethernet rings.

	David