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]
Message-ID: <alpine.DEB.2.21.1807191541130.1602@nanos.tec.linutronix.de>
Date:   Thu, 19 Jul 2018 15:48:31 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Paul Menzel <pmenzel+linux-pci@...gen.mpg.de>
cc:     Bjorn Helgaas <helgaas@...nel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, Marc Zyngier <marc.zyngier@....com>
Subject: Re: NULL pointer dereference in msi_set_mask_bit

Paul,

On Thu, 19 Jul 2018, Paul Menzel wrote:

> I had to copy the files, and then was able to create an archive with
> non-zero files. Please find the tar archive attached.

Thanks for providing the data. All looks normal there.

Just for clarification. Did this happen exactly once, or did it just not
happen again after you plugged in a serial cable?

One thing you might try is to disable irqbalanced when the machine is up
and then stress the affinity setter mechanism with scripting.

Something like

while true; do
 for I in {0..3}; do echo $I > /proc/irq/$IRQ/smp_affinity_list; done
done

might be able to trigger it. But don't ask me which interrupt was involved,
so you have to iterate through the ones which are MSI based.

'cat /proc/interrupt | grep MSI' will tell you.

Thanks,

	tglx


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ