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.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 9991EC433E1 for ; Wed, 3 Jun 2020 21:27:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8022F206E6 for ; Wed, 3 Jun 2020 21:27:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726410AbgFCV1W (ORCPT ); Wed, 3 Jun 2020 17:27:22 -0400 Received: from namei.org ([65.99.196.166]:40800 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725961AbgFCV1V (ORCPT ); Wed, 3 Jun 2020 17:27:21 -0400 Received: from localhost (localhost [127.0.0.1]) by namei.org (8.14.4/8.14.4) with ESMTP id 053LRKem003771; Wed, 3 Jun 2020 21:27:20 GMT Date: Thu, 4 Jun 2020 07:27:20 +1000 (AEST) From: James Morris To: Linus Torvalds cc: Linux Kernel Mailing List , LSM List Subject: Re: [GIT PULL][Security] lockdown: Allow unprivileged users to see lockdown status In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2 Jun 2020, Linus Torvalds wrote: > On Mon, Jun 1, 2020 at 7:15 PM James Morris wrote: > > > > Just one update for the security subsystem: allows unprivileged users to > > see the status of the lockdown feature. From Jeremy Cline. > > Hmm. > > That branch seems to have sprouted another commit just today. Oops, sorry, I thought it was already pulled. > > I ended up taking that too as trivial, but it shows how you seem to > basically send me a pointer to a live branch. Please don't do that. > When you make changes to that branch, I now get those changes that you > may not have meant to send me (and that I get upset for being > surprised by). > > An easy solution to that is to send me a signed tag instead of a > pointer to a branch. Then you can continue to update the branch, while > the tag stays stable. > > Plus we've been encouraging signed tags for pull requests anyway. Ok. -- James Morris