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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 2E410C433E0 for ; Mon, 15 Jun 2020 16:28:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0D352207F5 for ; Mon, 15 Jun 2020 16:28:38 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="OO0Hsoq7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730929AbgFOQ2g (ORCPT ); Mon, 15 Jun 2020 12:28:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56498 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730447AbgFOQ2f (ORCPT ); Mon, 15 Jun 2020 12:28:35 -0400 Received: from mail-ej1-x641.google.com (mail-ej1-x641.google.com [IPv6:2a00:1450:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBAE3C05BD43 for ; Mon, 15 Jun 2020 09:28:34 -0700 (PDT) Received: by mail-ej1-x641.google.com with SMTP id l27so18147705ejc.1 for ; Mon, 15 Jun 2020 09:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dmwX7P1qa5AxhzzJ+vXMBvRvKi99lt5x3CENqnU7BDw=; b=OO0Hsoq7pEyhd+RhOtlLw3eIuo0gsRaaDxCHKadHohKQfIIQ/9Mtk36ofZ79Xn/fVe 2/SghCCNBVGjo+xthRh9+r0HrA9X+gLQVqwl6PPJc5GPGE9c21JAZYxrzaO4vushKDIY yDMmXHJAHEDwQlurhRRU+LadbJm/2cTz8GR4w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dmwX7P1qa5AxhzzJ+vXMBvRvKi99lt5x3CENqnU7BDw=; b=JCQ2vMih5OhfP2zbD7ewM12np1OT+9TwCCB6Y5V/0OpQG6PP0/juzyi2oF2HSqpDUG pOsHosbls7Y4VFG2j1JvVOgpZpeqmCYrEGIzM5kk20sG9u5nlV6/eZ5JWA1tW+VnPHPE 2yLFlUwFcll4De9pn0ZxDWpFdzyNF0J8lwcjnT2sSvyj9H3TmZioeVGxA+rotCDimxcA pHmWUNVpMHhnHR5OcKSIQn2olGrYaMoK2NEJllr8QdCbFHTdeR/R8c6Ctd7r9A80dpHu LY+bBgFQp/oLgLxdn/+2OmZvtpIqfedNfN+0RStOAhQ/0poW2rBNQSlx11755xv876Cw +wug== X-Gm-Message-State: AOAM533JwXECzuhdncuSrPwsDEioS6hQIMn9jsqzoUtqEkQ1vY5kQlup 9WSBmzraOarAWu9RhrwPCxvn16LQKZa1/3qM2W3xMg== X-Google-Smtp-Source: ABdhPJzzuW9ljsYYvg62Bc4EVtQsy0MDdXnrP9JjQj14fiHarxB1DQyUyFTLx2JgD06teVbGPjK1cYlEJYt+THXpesU= X-Received: by 2002:a17:906:d973:: with SMTP id rp19mr25139408ejb.475.1592238513568; Mon, 15 Jun 2020 09:28:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Micah Morton Date: Mon, 15 Jun 2020 09:28:22 -0700 Message-ID: Subject: Re: [GIT PULL] SafeSetID LSM changes for v5.8 To: Linus Torvalds Cc: Linux Kernel Mailing List , linux-security-module 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 Sun, Jun 14, 2020 at 12:20 PM Linus Torvalds wrote: > > On Sun, Jun 14, 2020 at 12:12 PM Micah Morton wrote: > > > > That said I'm a little fuzzy on where to draw the line for which kinds > > of changes really should be required to have bake time in -next. If > > you think this is one of those cases, we can hold off on this until we > > have some bake time for v5.9. > > It's merged, but in general the rule for "bake in -next" should be > absolutely everything. > > The only exception is just pure and plain fixes. Sounds good, that makes it pretty clear. Thanks > > This SafeSetID change should in fact have been there for two different > reasons: not only was it a new feature rather than a fix (in > linux-next just for testing), it was one that crossed subsystem > borders (should be in linux-next just for cross-subsystem testing). It > touched files that very much aren't touched by just you. > > "Looks obvious" has nothing to do with avoiding linux-next. > > I suspect most of the bugs we have tend to be in code that "looked > obvious" to somebody. > > Linus