linux-kernel - Re: [PATCH] genirq/affinity: Handle affinity setting on inactive interrupts correctly

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] [day] [month] [year] [list]

Date:   Fri, 17 Jul 2020 23:23:04 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     "Saidi\, Ali" <alisaidi@...zon.com>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     "x86\@kernel.org" <x86@...nel.org>,
        "Herrenschmidt\, Benjamin" <benh@...zon.com>,
        Ali Saidi <aliaidi@...zon.com>, Marc Zyngier <maz@...nel.org>,
        "linux-arm-kernel\@lists.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] genirq/affinity: Handle affinity setting on inactive interrupts correctly

Ali,

"Saidi, Ali" <alisaidi@...zon.com> writes:

can you pretty please fix your mail setup. Your replies lack the
following headers:

  In-Reply-To:
  References:

but carry some useless Microsoft gunk instead:

  Thread-Topic: [PATCH] genirq/affinity: Handle affinity setting on inactive
    interrupts correctly
  Thread-Index: AQHWXE5yOF+Kj67jZUWJl7gBhLLD9A==

which is non RFC and not documented. Evolution has some magic hack to
decode this mess, but all mail readers which rely on the documented RFC
fields including archives:

  https://lore.kernel.org/lkml/BBA90891-8A4A-4A39-BF51-13EECDE414F1@amazon.com/

fail to properly thread your mails. That sucks.

> Tested on an arm64 system that originally experienced the issue and couldn't reproduce it with this patch.
> Tested-by: Ali Saidi <alisaidi@...zon.com>

Nevertheless, thanks for confirming that it solves the problem :)

       tglx