linux-kernel - Re: [PATCH 1/2] sp5100_tco: Fix wrong indirect I/O access for getting value of reserved bits

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: <1360140363.4790.7.camel@mattotaupa>
Date:	Wed, 06 Feb 2013 09:46:03 +0100
From:	Paul Menzel <paulepanter@...rs.sourceforge.net>
To:	Wim Van Sebroeck <wim@...ana.be>
Cc:	Takahisa Tanaka <mc74hc00@...il.com>,
	linux-watchdog@...r.kernel.org,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jonathan Nieder <jrnieder@...il.com>,
	linux-kernel@...r.kernel.org, Florian Mickler <florian@...kler.org>
Subject: Re: [PATCH 1/2] sp5100_tco: Fix wrong indirect I/O access for
 getting value of reserved bits

Dear Wim,


Am Mittwoch, den 30.01.2013, 20:19 +0100 schrieb Wim Van Sebroeck:

> > In case of SB800 or later chipset and re-programming MMIO address(*),
> > sp5100_tco module may read incorrect value of reserved bit, because the module
> > reads a value from an incorrect I/O address. However, this bug doesn't cause
> > a problem, because when re-programming MMIO address, by chance the module
> > writes zero (this is BIOS's default value) to the low three bits of register.
> > * In most cases, PC with SB8x0 or later chipset doesn't need to re-programming
> >   MMIO address, because such PC can enable AcpiMmio and can use 0xfed80b00 for
> >   watchdog register base address.
> > 
> > This patch fixes this bug.
> > 
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
> > Signed-off-by: Takahisa Tanaka <mc74hc00@...il.com>
> 
> Added to linux-watchdog-next.

Is it allowed to rewrite history of linux-watchdog-next? If yes, could
you please add `CC: stable@...r.kernel.org` to both of Takahisa’s
patches and also add my

    Tested-by: Paul Menzel <paulepanter@...rs.sourceforge.net>
        ASRock E350M1 (SB800)

as commented on the bug report to it?


Thanks,

Paul

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)