Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751793AbaGQR6V (ORCPT ); Thu, 17 Jul 2014 13:58:21 -0400 Received: from mail-ie0-f176.google.com ([209.85.223.176]:44466 "EHLO mail-ie0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750964AbaGQR6U (ORCPT ); Thu, 17 Jul 2014 13:58:20 -0400 MIME-Version: 1.0 In-Reply-To: References: <1405588695-12014-1-git-send-email-tytso@mit.edu> <20140717161215.GA14951@infradead.org> <20140717170115.GO1491@thunk.org> <20140717173433.GQ1491@thunk.org> From: Bob Beck Date: Thu, 17 Jul 2014 11:57:59 -0600 X-Google-Sender-Auth: AHuEiTTVOJWtfLgc3WkPCS8_-EQ Message-ID: Subject: Re: [PATCH, RFC] random: introduce getrandom(2) system call To: "Theodore Ts'o" , Bob Beck , Christoph Hellwig , linux-kernel , linux-abi , linux-crypto Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Or perhaps to put that another way, since you don't do minherit - maybe a FORK_ZERO for madvise? or a similar way to do that? On Thu, Jul 17, 2014 at 11:46 AM, Bob Beck wrote: > And thanks btw. > > I don't suppose you guys know who we should talk to about possibly > getting MAP_INHERIT_ZERO minherit() support? > > On Thu, Jul 17, 2014 at 11:45 AM, Bob Beck wrote: >> we have diffs pending that will do the syscall method until we start >> to see it in libc :) >> >> So basically we're going to put that in right away :) >> >> On Thu, Jul 17, 2014 at 11:34 AM, Theodore Ts'o wrote: >>> On Thu, Jul 17, 2014 at 11:05:01AM -0600, Bob Beck wrote: >>>> Hi Ted, yeah I understand the reasoning, it would be good if there was >>>> a way to influence the various libc people to >>>> ensure they manage to provide a getentropy(). >>> >>> I don't anticipate that to be a problem. And before they do, and/or >>> if you are dealing with a system where the kernel has been upgraded, >>> but not libc, you have your choice of either sticking with the >>> binary_sysctl approach, or calling getrandom directly using the >>> syscall method; and in that case, whether we use getrandom() or >>> provide an exact getentropy() replacement system call isn't that much >>> difference, since you'd have to have Linux-specific workaround code >>> anyway.... >>> >>> - Ted -- 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/