linux-kernel - Re: [PATCH 5/6] x86/platform/uv/BAU: Remove initial write to swack register

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:   Thu, 16 Feb 2017 19:28:30 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Andrew Banman <abanman@....com>
cc:     mingo@...hat.com, akpm@...ux-foundation.org, hpa@...or.com,
        mike.travis@....com, rja@....com, sivanich@....com, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] x86/platform/uv/BAU: Remove initial write to swack
 register

On Tue, 14 Feb 2017, Andrew Banman wrote:

> Writing to the software acknowledge clear register when there are no
> pending messages causes a HUB error to assert. The original intent of this
> write was to clear the pending bits before start of operation, but this is
> an incorrect method and has been determined to be unnecessary.

This is a bug fix, independent of the rest of the series, right?

So it should go to the beginning of that series or even better sent out as
a seperate patch so it can be picked up right away. Hiding bug fixes in the
middle of a functional/feature series makes them slip through.

Thanks,

	tglx