linux-kernel - Re: [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite

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: <87lgpo8b91.fsf@concordia.ellerman.id.au>
Date:   Tue, 23 May 2017 14:09:46 +1000
From:   Michael Ellerman <mpe@...erman.id.au>
To:     Ivan Mikhaylov <ivan@...ibm.com>,
        Alistair Popple <alistair@...ple.id.au>,
        Matt Porter <mporter@...nel.crashing.org>
Cc:     linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Joel Stanley <joel@....id.au>,
        Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite

Ivan Mikhaylov <ivan@...ibm.com> writes:
>
> From my point of view it's possible. I've checked docu and on idea
> it should be possible cause WP is only affecting watchdog ping time.

The question is, is there any chance that leaving those bits set on
another platform will cause a problem?

ie. on existing machines we always clear those bits, is it OK that we
will now start leaving those bits with whatever value they had.

cheers