Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B558CC43217 for ; Thu, 18 Nov 2021 17:32:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9ABE161A53 for ; Thu, 18 Nov 2021 17:32:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234104AbhKRRfG (ORCPT ); Thu, 18 Nov 2021 12:35:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232367AbhKRRfF (ORCPT ); Thu, 18 Nov 2021 12:35:05 -0500 Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 10C1EC061748 for ; Thu, 18 Nov 2021 09:32:05 -0800 (PST) Received: by mail-pg1-x52f.google.com with SMTP id 28so5995287pgq.8 for ; Thu, 18 Nov 2021 09:32:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=4ZRY5BIcQHJ120UEZi/XkGexoEr3hEm901+ewWa9TxY=; b=Q3we5WCD0xmIJKfl/TfgI5kD/aocwY/0SWDW+zmJNqPz5ybfO4CiNYosT1l9w0Z9zm JSfluadZC7peSWt6bagPafCt/4+VUAb2oALOEQL4x1CPXNYnju45tV0Xa3SiAuq6RtfH T7werkmqyBzOZjFDtT85I8mV9XupExiLUE+Tg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4ZRY5BIcQHJ120UEZi/XkGexoEr3hEm901+ewWa9TxY=; b=1xCjHm7dMXK9e6Q9hV3X4cAyi+Q2DFQxn+R9tPnIozIq5Fagsz16/TNbu3Y4WErrKE yYCKH3EWJMeGQfSe1eEabbpGPTwM1gu04sFVR7Yawsm+IzMXP91QdpN36ZcNJE+6gj6T 1Iw7tHsYgfOj5jaY+UarspCgkoHjf4wyB2F34CFPpbGi8dwoo5OJV0kKhufe6mtLW8M5 TWW9SxOdJwEKMBkGsjRKh73gQJtx5+9R5HKYvJQ95dEBhBM/YDk1knfc6wHV9PSyZD0R vBtoT3+vSHwelOLZzBdkTg1SyGclf3FOuaX9is26yV62SQn44AHti5RJ3YlrEr3Bupmp bewQ== X-Gm-Message-State: AOAM531NrSFdd1w4kp8LSR6QLVuYizICkVB5tl3kHGJg8Wf0ww5/1Z2A AcxNMegYjJkymkjCJelgywThp1kPHoEPbA== X-Google-Smtp-Source: ABdhPJwT/zhrA/divF29Wy7h+2JuyxEQeJZ/M1e44k8ifJxXNxi0P2wRxx059BjsCi4gIRC5beV5Rg== X-Received: by 2002:a63:5f56:: with SMTP id t83mr12443174pgb.432.1637256724564; Thu, 18 Nov 2021 09:32:04 -0800 (PST) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id f15sm242298pfe.171.2021.11.18.09.32.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Nov 2021 09:32:04 -0800 (PST) Date: Thu, 18 Nov 2021 09:32:03 -0800 From: Kees Cook To: Casey Schaufler Cc: Alexander Popov , Steven Rostedt , Linus Torvalds , Lukas Bulwahn , Jonathan Corbet , Paul McKenney , Andrew Morton , Thomas Gleixner , Peter Zijlstra , Joerg Roedel , Maciej Rozycki , Muchun Song , Viresh Kumar , Robin Murphy , Randy Dunlap , Lu Baolu , Petr Mladek , Luis Chamberlain , Wei Liu , John Ogness , Andy Shevchenko , Alexey Kardashevskiy , Christophe Leroy , Jann Horn , Greg Kroah-Hartman , Mark Rutland , Andy Lutomirski , Dave Hansen , Will Deacon , Ard Biesheuvel , Laura Abbott , David S Miller , Borislav Petkov , Arnd Bergmann , Andrew Scull , Marc Zyngier , Jessica Yu , Iurii Zaikin , Rasmus Villemoes , Wang Qing , Mel Gorman , Mauro Carvalho Chehab , Andrew Klychkov , Mathieu Chouquet-Stringer , Daniel Borkmann , Stephen Kitt , Stephen Boyd , Thomas Bogendoerfer , Mike Rapoport , Bjorn Andersson , Kernel Hardening , linux-hardening@vger.kernel.org, "open list:DOCUMENTATION" , linux-arch , Linux Kernel Mailing List , linux-fsdevel , notify@kernel.org, main@lists.elisa.tech, safety-architecture@lists.elisa.tech, devel@lists.elisa.tech, Shuah Khan Subject: Re: [PATCH v2 0/2] Introduce the pkill_on_warn parameter Message-ID: <202111180930.5FA3EF0F59@keescook> References: <20211027233215.306111-1-alex.popov@linux.com> <77b79f0c-48f2-16dd-1d00-22f3a1b1f5a6@linux.com> <20211115110649.4f9cb390@gandalf.local.home> <202111151116.933184F716@keescook> <59534db5-b251-c0c8-791f-58aca5c00a2b@linux.com> <202111161037.7456C981@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 16, 2021 at 11:00:23AM -0800, Casey Schaufler wrote: > On 11/16/2021 10:41 AM, Kees Cook wrote: > > On Tue, Nov 16, 2021 at 12:12:16PM +0300, Alexander Popov wrote: > > > What if the Linux kernel had a LSM module responsible for error handling policy? > > > That would require adding LSM hooks to BUG*(), WARN*(), KERN_EMERG, etc. > > > In such LSM policy we can decide immediately how to react on the kernel error. > > > We can even decide depending on the subsystem and things like that. > > That would solve the "atomicity" issue the WARN tracepoint solution has, > > and it would allow for very flexible userspace policy. > > > > I actually wonder if the existing panic_on_* sites should serve as a > > guide for where to put the hooks. The current sysctls could be replaced > > by the hooks and a simple LSM. > > Do you really want to make error handling a "security" issue? > If you add security_bug(), security_warn_on() and the like > you're begging that they be included in SELinux (AppArmor) policy. > BPF, too, come to think of it. Is that what you want? Yeah, that is what I was thinking. This would give the LSM a view into kernel state, which seems a reasonable thing to do. If system integrity is compromised, an LSM may want to stop trusting things. A dedicated error-handling LSM could be added for those hooks that implemented the existing default panic_on_* sysctls, and could expand on that logic for other actions. -- Kees Cook