linux-kernel - Re: [PATCH 2/2] sp5100_tco: Write back the original value to reserved bits, instead of zero

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: <CAHh0gOjagPA2SJh+crZtL=eSFqQBJRkDB64_ffdKuJaCtHOwkQ@mail.gmail.com>
Date:	Thu, 31 Jan 2013 22:43:32 +0900
From:	t t <mc74hc00@...il.com>
To:	Wim Van Sebroeck <wim@...ana.be>
Cc:	linux-watchdog@...r.kernel.org,
	Paul Menzel <paulepanter@...rs.sourceforge.net>,
	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 2/2] sp5100_tco: Write back the original value to reserved
 bits, instead of zero

2013/1/31 Wim Van Sebroeck <wim@...ana.be>:
> Hi,
>
>> In case of SP5100 or SB7x0 chipsets, the sp5100_tco module writes zero to
>> reserved bits. The module, however, shouldn't depend on specific default
>> value, and should perform a read-merge-write operation for the reserved
>> bits.
>>
>> This patch makes the sp5100_tco module perform a read-merge-write operation
>> on all the chipset (sp5100, sb7x0, sb8x0 or later).
>>
>> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
>> Signed-off-by: Takahisa Tanaka <mc74hc00@...il.com>
>
> Added to linux-watchdog-next.

Thanks Wim!


Kind regards,
Takahisa
--
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/