Received: by 10.223.185.116 with SMTP id b49csp4186286wrg; Tue, 6 Mar 2018 11:13:57 -0800 (PST) X-Google-Smtp-Source: AG47ELvw1shjVBJUC2QIxKFJMtT+NesyI9zFl82Tz1/ChoZ9UGk4kFZVm3watLDzOzDZ+TCdSKDk X-Received: by 10.98.206.1 with SMTP id y1mr19929573pfg.196.1520363637409; Tue, 06 Mar 2018 11:13:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520363637; cv=none; d=google.com; s=arc-20160816; b=rkly2IMf5FtM9/HKSenZm9GZ8edTihj26xG5jqQ1ynt63ZDs7bTiXT51P+0+olc2CQ GLBiprLwpvzQvVoJ1CqhwKZVJExdbRzROqBjjC93Sr8AH3WwIyaH0N6MiHXODubiRtkQ b1V7/OJIMqJ9922wkcDf603L8vVm2neRcdA1XmAVwy7IcS/o0ZTuU1KCe0Jjg35gD/7N hdA+BrMMubGZMV6r6n6xk7xJHGNJBvq+WHiaJAvvqclVkXjeqkcvhg94jvEtGW9FZHEY qZyOd5keh/IOYkrta5IiL1eIXPr2KY4LxNkBPkUcuD6tZ54jtNOJsOkQ278pZQX/yuRJ LnMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=j5cPMo2ik6gOS+UMFS6OEtgrG9JHC4ZfFuW+7n0gTgE=; b=I8KduE8yJAHvUNJojJW9LrEwkONObyxUPDo9p5SEBxTE4KF8rE+atNKt3p8Q+iIQXW l4t0/E1wq6IKDqoz6Ij2BEdiLVB7+o1rmMDrrDfofyRLUXsVBq5HrUHFIttGpk0dKg6n bg/oB/gkq+l0alxZhO/hy9uZC2qH+eJOnTFM9a9dgAgTC+F2+h4/moSs8hIhk7Y0EsJG SkRMS4u5udDQGeAiGhqOti9gCmAUwkxBiItOsD3KLuRa7ZzldVS0iF07XOclQuTg4Hcd po/eVLlvznh+sInyE5y9Ls5OavWyyFUsUKm/c5VMxZQML0yF/PAuSHTCy1nYeSYEPsmo pnEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=EW+cZrS+; dkim=fail header.i=@linux-foundation.org header.s=google header.b=NTkjdWxr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w12-v6si11643355pld.51.2018.03.06.11.13.42; Tue, 06 Mar 2018 11:13:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=EW+cZrS+; dkim=fail header.i=@linux-foundation.org header.s=google header.b=NTkjdWxr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754033AbeCFTM2 (ORCPT + 99 others); Tue, 6 Mar 2018 14:12:28 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:40952 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753168AbeCFTMZ (ORCPT ); Tue, 6 Mar 2018 14:12:25 -0500 Received: by mail-it0-f68.google.com with SMTP id e64so176367ita.5; Tue, 06 Mar 2018 11:12:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=j5cPMo2ik6gOS+UMFS6OEtgrG9JHC4ZfFuW+7n0gTgE=; b=EW+cZrS+w+VrwXgy5wme4bBQEKdV5FqC7ygX6Yd9PDip/zzrxGrmpuVCwluTydVV6r E2KLKNJkYrveHAr4ZlCLq/J/hgL4LufTxfTKmnf558FCV/ZHD79u5x4lx96VgpVxCw5m Cul7xzyjswakWcEdrNCzeRveIl2JoX3XNP0HQSWyD/u6C3pXOlFkhe3sCMPWLCW7gDBj 2dukm0O1ylpN0DaC+vpxSanxyuRIBpiNvIDU1/6inEsNHob6ScPOnOu8Q/PbNt+G7kvB t+spK34Xl2li9FAAixsytCtrJtfdql8nYbPxlkHoBLPGFN7Nm6EZsQTUb/hJFzVtzBk7 Rjlg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=j5cPMo2ik6gOS+UMFS6OEtgrG9JHC4ZfFuW+7n0gTgE=; b=NTkjdWxrN+wE5zxXMzN3r8mMl9N/xLN1egMj23SmZZ7O/q+70udxJ8Ej9S2BkCmyFc WEvGQuLwDkS8ODMWvpImajMCnyNr3u/KYpFnVsfquBq7pBP5cR+BFYhHpEkfguO4PI49 AI52OucMJWXeFg3M2HM1/ubs3vYxniakObhsQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=j5cPMo2ik6gOS+UMFS6OEtgrG9JHC4ZfFuW+7n0gTgE=; b=jI4tKCExymGhp2/RGhSnTX/r8VcwVAuC0vgQSJgEhNPAZccD4k3DaGSFkRksI9oY0t iT1GoKco8/JCk36bZkeUTroyzklR3ozYMM8HPlvhHW4xScA9vMyvXLBBPExydBfMQ0Tn e+4Hn1w1pOvXGYLJfpPQQuJrO2zCbYRtQ1x/msnFqmLw2fN2gYAb3jOXGPb4Pmy/60YK 6qdfC9b2DjpWicq3QI9Fm9MnSEX/unIt2bsLTnIPNHYMnlDQMwU94yIJ9EXdlGWMVTBO N4erKTDsT3k1yP4dWWSeaIrm4iBor4U2oSdNxtvcgjUJ/1ufmlU5uDer25Gg7QNHUN5l 7R6g== X-Gm-Message-State: AElRT7Gu2HO37uG/gML8sVFWArY/XcsCd0pj8TwXKo7B0+L1GpBYUzPr vLDq54j+Q1VilPQrGvb99RPTX58kzMxDRC//v9M= X-Received: by 10.36.89.137 with SMTP id p131mr19532206itb.113.1520363544612; Tue, 06 Mar 2018 11:12:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.135.221 with HTTP; Tue, 6 Mar 2018 11:12:24 -0800 (PST) In-Reply-To: <20180306013457.1955486-1-ast@kernel.org> References: <20180306013457.1955486-1-ast@kernel.org> From: Linus Torvalds Date: Tue, 6 Mar 2018 11:12:24 -0800 X-Google-Sender-Auth: D2_eZzdGHg-RtDffp08f36Xo0Qk Message-ID: Subject: Re: [PATCH net-next] modules: allow modprobe load regular elf binaries To: Alexei Starovoitov Cc: David Miller , Daniel Borkmann , Greg Kroah-Hartman , "Luis R. Rodriguez" , Network Development , Linux Kernel Mailing List , kernel-team , Linux API Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 5, 2018 at 5:34 PM, Alexei Starovoitov wrote: > As the first step in development of bpfilter project [1] the request_module() > code is extended to allow user mode helpers to be invoked. Idea is that > user mode helpers are built as part of the kernel build and installed as > traditional kernel modules with .ko file extension into distro specified > location, such that from a distribution point of view, they are no different > than regular kernel modules. Thus, allow request_module() logic to load such > user mode helper (umh) modules via: [,,] I like this, but I have one request: can we make sure that this action is visible in the system messages? When we load a regular module, at least it shows in lsmod afterwards, although I have a few times wanted to really see module load as an event in the logs too. When we load a module that just executes a user program, and there is no sign of it in the module list, I think we *really* need to make that event show to the admin some way. .. and yes, maybe we'll need to rate-limit the messages, and maybe it turns out that I'm entirely wrong and people will hate the messages after they get used to the concept of these pseudo-modules, but particularly for the early implementation when this is a new thing, I really want a message like executed user process xyz-abc as a pseudo-module or something in dmesg. I do *not* want this to be a magical way to hide things. Linus