| 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
| ||
|
Message-ID: <DB904C5425BA6F4E8424B3B51A1414D16D3BA94A82@NWD2CMBX1.ad.analog.com> Date: Wed, 26 Oct 2011 04:53:00 -0400 From: "Zhang, Sonic" <Sonic.Zhang@...log.com> To: Mike Frysinger <vapier@...too.org>, Sonic Zhang <sonic.adi@...il.com> CC: "uclinux-dist-devel@...ckfin.uclinux.org" <uclinux-dist-devel@...ckfin.uclinux.org>, Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org> Subject: RE: [uclinux-dist-devel] [PATCH] mutex:SMP:bf561:Run smp memory barrier after take atomic lock in mutex_fastpath APIs. Hi Mike, Our SMP atomic implementation doesn't include memory barrier. Is it a better way to add barrier there? Thanks Sonic >-----Original Message----- >From: uclinux-dist-devel-bounces@...ckfin.uclinux.org >[mailto:uclinux-dist-devel-bounces@...ckfin.uclinux.org] On >Behalf Of Mike Frysinger >Sent: Wednesday, October 26, 2011 3:54 PM >To: Sonic Zhang >Cc: uclinux-dist-devel@...ckfin.uclinux.org; Ingo Molnar; LKML >Subject: Re: [uclinux-dist-devel] [PATCH] mutex:SMP:bf561:Run >smp memory barrier after take atomic lock in mutex_fastpath APIs. > >unfortunately, this is incorrect. please see the thread: >https://lkml.org/lkml/2011/5/29/233 >-mike >_______________________________________________ >Uclinux-dist-devel mailing list >Uclinux-dist-devel@...ckfin.uclinux.org >https://blackfin.uclinux.org/mailman/listinfo/uclinux-dist-devel > > -- 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/
Powered by blists - more mailing lists