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=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=unavailable 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 4E728C28EB9 for ; Thu, 6 Jun 2019 22:42:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 211F72083E for ; Thu, 6 Jun 2019 22:42:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=amacapital-net.20150623.gappssmtp.com header.i=@amacapital-net.20150623.gappssmtp.com header.b="PTRK9vmn" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728005AbfFFWmJ (ORCPT ); Thu, 6 Jun 2019 18:42:09 -0400 Received: from mail-pl1-f194.google.com ([209.85.214.194]:39547 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727941AbfFFWmI (ORCPT ); Thu, 6 Jun 2019 18:42:08 -0400 Received: by mail-pl1-f194.google.com with SMTP id g9so14646plm.6 for ; Thu, 06 Jun 2019 15:42:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amacapital-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KsNX6r5jKFOtQ4lc+eGRV9xmq07Fm18WJPMjS5Z5MPI=; b=PTRK9vmnWT/g5Zr13QQRSUiVwS2KbOUvsIl2db/P+q1I8gaxTF0N84zr8YwVEVwyxL 1NzQ2DkAwfGv9hZcClcYfEqM1HX4/V4oVt7BdvmPoDazbYJaYLaMcEgjqlu3Uxg1/kb6 n0eSP40bYpV5/gjNcG4y1fCKV7DSQn/yW9xDmUx9Ci2PbXiBlSy78NzILgwdl+f8NyvE QHEZasQgWh4BfDBUTRa2NVTPuoEkWz/LBCpTMu6QgdK6y15/L78uij70co/ARlFW4kUV 2/KU00Eq47kw3ycEMGuxqu3uund8p1OPBUVsgPHr7HpKOu4Wc1yJ02Ts2iR7g1aSpMO4 smRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KsNX6r5jKFOtQ4lc+eGRV9xmq07Fm18WJPMjS5Z5MPI=; b=WPFynImyoIdF2NvoCBE+zAjDs6wda8IRfIGk0sqFj/A21ltoLJgFXLGDsREVEMN1Ew 0y4mxoaRVTF0T6IAjBNxaVq3o2Tsvtq2ZVHytUwLSH7lwK/c4nfBN1nruOlrrOZf5tNT w6ises0i1LmNmGYTDm6LCQciJoqu0h/E8yAywOHL90wwHhYpWXxcg4md49AkJ4zYiQON KcSlEfJProTDK7ZOVUQ1Gm9mgublPlvQbTaZQhRK9wUpm/xoctuQGzTi9GNfDlZIBIBS RgCvPtMMjo65TbxfRydlQF7SIjyziEowLsLi/WqvSG+Z4X6AXjVtQjxlVls19fVFMgbn VGlw== X-Gm-Message-State: APjAAAXHG8hrstfq3YGkljjbSvKxGqCmuFSXsys7TFbLFmsnooRrfjWl rpvZhru3kfDRFYMlBuhANAgo0w== X-Google-Smtp-Source: APXvYqynrY/MWcua7DL8n0SxJjPX2N5fvHveHOTGRewZhfAbF+o8v10tdKo1UnQrl1Ben9xxExi0kg== X-Received: by 2002:a17:902:8d89:: with SMTP id v9mr33641433plo.99.1559860927859; Thu, 06 Jun 2019 15:42:07 -0700 (PDT) Received: from ?IPv6:2601:646:c200:1ef2:1d20:2c9f:a1b0:7165? ([2601:646:c200:1ef2:1d20:2c9f:a1b0:7165]) by smtp.gmail.com with ESMTPSA id x66sm167031pfx.139.2019.06.06.15.42.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 15:42:07 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: [RFC][PATCH 00/10] Mount, FS, Block and Keyrings notifications [ver #3] From: Andy Lutomirski X-Mailer: iPhone Mail (16F203) In-Reply-To: <30567.1559860681@warthog.procyon.org.uk> Date: Thu, 6 Jun 2019 15:42:06 -0700 Cc: Andy Lutomirski , Casey Schaufler , Stephen Smalley , Al Viro , Greg Kroah-Hartman , USB list , raven@themaw.net, Linux FS Devel , Linux API , linux-block@vger.kernel.org, keyrings@vger.kernel.org, LSM List , LKML , Paul Moore Content-Transfer-Encoding: quoted-printable Message-Id: References: <155981411940.17513.7137844619951358374.stgit@warthog.procyon.org.uk> <3813.1559827003@warthog.procyon.org.uk> <8382af23-548c-f162-0e82-11e308049735@tycho.nsa.gov> <0eb007c5-b4a0-9384-d915-37b0e5a158bf@schaufler-ca.com> <07e92045-2d80-8573-4d36-643deeaff9ec@schaufler-ca.com> <23611.1559855827@warthog.procyon.org.uk> <30567.1559860681@warthog.procyon.org.uk> To: David Howells Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Jun 6, 2019, at 3:38 PM, David Howells wrote: >=20 > Andy Lutomirski wrote: >=20 >> I mean: are there cases where some action generates a notification but do= es >> not otherwise have an effect visible to the users who can receive the >> notification. It looks like the answer is probably =E2=80=9Cno=E2=80=9D, w= hich is good. >=20 > mount_notify(). You can get a notification that someone altered the mount= > topology (eg. by mounting something). A process receiving a notification > could then use fsinfo(), say, to reread the mount topology tree, find out > where the new mount is and wander over there to have a look - assuming the= y > have the permissions for pathwalk to succeed. >=20 >=20 They can call fsinfo() anyway, or just read /proc/self/mounts. As far as I=E2= =80=99m concerned, if you have CAP_SYS_ADMIN over a mount namespace and LSM p= olicy lets you mount things, the of course you can get information to basica= lly anyone who can use that mount namespace.=