From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6CC42C67863 for ; Tue, 23 Oct 2018 11:32:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 41AF920671 for ; Tue, 23 Oct 2018 11:32:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 41AF920671 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728376AbeJWTzm (ORCPT ); Tue, 23 Oct 2018 15:55:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:54038 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728066AbeJWTzl (ORCPT ); Tue, 23 Oct 2018 15:55:41 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 4FD66AEBC; Tue, 23 Oct 2018 11:32:35 +0000 (UTC) Date: Tue, 23 Oct 2018 13:32:34 +0200 From: Michal Hocko To: "Edgecombe, Rick P" Cc: "jannh@google.com" , "linux-kernel@vger.kernel.org" , "daniel@iogearbox.net" , "keescook@chromium.org" , "jeyu@kernel.org" , "linux-arch@vger.kernel.org" , "arjan@linux.intel.com" , "tglx@linutronix.de" , "linux-mips@linux-mips.org" , "linux-s390@vger.kernel.org" , "x86@kernel.org" , "kristen@linux.intel.com" , "Dock, Deneen T" , "catalin.marinas@arm.com" , "mingo@redhat.com" , "will.deacon@arm.com" , "kernel-hardening@lists.openwall.com" , "bp@alien8.de" , "Hansen, Dave" , "linux-arm-kernel@lists.infradead.org" , "davem@davemloft.net" , "arnd@arndb.de" , "linux-fsdevel@vger.kernel.org" , "sparclinux@vger.kernel.org" Subject: Re: [PATCH v2 1/7] modules: Create rlimit for module space Message-ID: <20181023113234.GH32333@dhcp22.suse.cz> References: <20181011233117.7883-1-rick.p.edgecombe@intel.com> <20181011233117.7883-2-rick.p.edgecombe@intel.com> <7b0714e26c7c2216721641d7df16a49687927e37.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b0714e26c7c2216721641d7df16a49687927e37.camel@intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 12-10-18 17:04:46, Edgecombe, Rick P wrote: [...] > Any thoughts on if instead of all this there was just a system wide limit on BPF > JIT module space usage? We do allow to charge vmalloc memory to a memory cgroup. Isn't that a way forward? -- Michal Hocko SUSE Labs