Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752460Ab2JJFzA (ORCPT ); Wed, 10 Oct 2012 01:55:00 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:44665 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154Ab2JJFy4 (ORCPT ); Wed, 10 Oct 2012 01:54:56 -0400 MIME-Version: 1.0 Reply-To: mtk.manpages@gmail.com In-Reply-To: References: <1348179300-11653-1-git-send-email-keescook@chromium.org> <50749DE8.7010703@zytor.com> <5074A0AB.8040207@zytor.com> From: "Michael Kerrisk (man-pages)" Date: Wed, 10 Oct 2012 07:54:35 +0200 Message-ID: Subject: Re: [PATCH 1/4] module: add syscall to load module from fd To: "H. Peter Anvin" Cc: eparis@redhat.com, "Serge E. Hallyn" , Rusty Russell , Arnd Bergmann , Al Viro , James Morris , Andrew Morton , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, Mimi Zohar , Kees Cook , Jiri Kosina Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 22 [resending because my mobile device decided it wanted to send HTML, which of course bounced.] On Oct 10, 2012 12:09 AM, "H. Peter Anvin" wrote: > > On 10/10/2012 06:03 AM, Michael Kerrisk (man-pages) wrote: > > Good point. A "whole hog" openat()-style interface is worth thinking about too. > > *Although* you could argue that you can always simply open the module > file first, and that finit_module() is really what we should have had in > the first place. Then you don't need the flags since those would come > from openat(). But in that case, I'd still stand by my original point: it may be desirable to have a flags argument to allow future modifications to the behavior of finit_module() (as opposed to the behavior of the file open). -- 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/