linux-kernel - Re: [PATCH 6 of 6] x86, UV: correct UV2 BAU destination timeout

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

Message-ID: <20110615074319.GC3538@elte.hu>
Date:	Wed, 15 Jun 2011 09:43:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Cliff Wickman <cpw@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6 of 6] x86, UV: correct UV2 BAU destination timeout


* Cliff Wickman <cpw@....com> wrote:

> From: Cliff Wickman <cpw@....com>
> 
> Correct the UV2 broacast assist unit's destination timeout period.
>   The period is set in 4 bits of memory-mapped register MISC_CONTROL.
>   The left bit toggles base period between 10us and 80us.
>   The other 3 bits are the multiplier.
> Decimal 15, hex f, gives the maximum: 7 * 80us
> 
> And the activation status register in UV2 should be tested for a destination
> timeout with a 4, not a 2.  The values for Active versus Timeout were reversed.

This changelog tells us everything except what a user of this code 
would be most interested in: what was the practical effect of the 
bug, how badly does the user want the fix?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/