linux-kernel - Re: linux-next: manual merge of the mips tree with the mips-fixes tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190206104433.1c832a0b@canb.auug.org.au>
Date:   Wed, 6 Feb 2019 10:44:33 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Paul Burton <paul.burton@...s.com>
Cc:     Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <jhogan@...nel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Huacai Chen <chenhc@...ote.com>,
        Huang Pei <huangpei@...ngson.cn>
Subject: Re: linux-next: manual merge of the mips tree with the mips-fixes
 tree

Hi Paul,

On Tue, 5 Feb 2019 23:35:31 +0000 Paul Burton <paul.burton@...s.com> wrote:
>
> cmpxchg() doesn't need the added loongson_llsc_mb() barrier that
> set_pte() has in mips-fixes because for the affected Loongson 3
> configurations the smp_mb__before_llsc() that cmpxchg() already contains
> is equivalent (both will emit a "sync 0" instruction).

OK, good to know, thanks.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped