Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932612AbbDJOJT (ORCPT ); Fri, 10 Apr 2015 10:09:19 -0400 Received: from mail.eperm.de ([89.247.134.16]:34086 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932699AbbDJOJN (ORCPT ); Fri, 10 Apr 2015 10:09:13 -0400 From: Stephan Mueller To: Hannes Frederic Sowa Cc: Daniel Borkmann , mancha , tytso@mit.edu, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au, dborkman@redhat.com Subject: Re: [BUG/PATCH] kernel RNG and its secrets Date: Fri, 10 Apr 2015 16:09:10 +0200 Message-ID: <1697288.aUGCRhyl06@tauon> User-Agent: KMail/4.14.6 (Linux/3.19.3-200.fc21.x86_64; KDE/4.14.6; x86_64; ; ) In-Reply-To: <1428674403.3377.4.camel@stressinduktion.org> References: <20150318095345.GA12923@zoho.com> <2792913.x6Cv5ZCyOY@tauon> <1428674403.3377.4.camel@stressinduktion.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1428 Lines: 70 Am Freitag, 10. April 2015, 16:00:03 schrieb Hannes Frederic Sowa: Hi Hannes, >On Fr, 2015-04-10 at 15:25 +0200, Stephan Mueller wrote: >> I would like to bring up that topic again as I did some more analyses: >> >> For testing I used the following code: >> >> static inline void memset_secure(void *s, int c, size_t n) >> { >> >> memset(s, c, n); >> >> BARRIER >> >> } >> >> where BARRIER is defined as: >> >> (1) __asm__ __volatile__("" : "=r" (s) : "0" (s)); >> >> (2) __asm__ __volatile__("": : :"memory"); >> >> (3) __asm__ __volatile__("" : "=r" (s) : "0" (s) : "memory"); > >Hm, I wonder a little bit... > >Could you quickly test if you replace (s) with (n) just for the fun of >it? I don't know if we should ask clang people about that, at least it >is their goal to be as highly compatible with gcc inline asm. Using __asm__ __volatile__("" : "=r" (n) : "0" (n) : "memory"); clang O2/3: no mov gcc O2/3: mov present ==> not good Using __asm__ __volatile__("" : "=r" (n) : "0" (n)); clang O2/3: no mov gcc O2/3: no mov ==> not good What do you expect that change shall do? > >Thanks for looking into this! > >Bye, >Hannes Ciao Stephan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/