All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gu Lingguang <liu83783@gmail.com>
To: Alexey Gladkov <legion@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	containers@lists.linux.dev,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Eric W . Biederman" <ebiederm@xmission.com>,
	Aleksa Sarai <cyphar@cyphar.com>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	Gu Lingguang <liu83783@gmail.com>
Subject: Re: [RFC] mnt_already_visible(): should regular-file mountpoints participate in the visibility check?
Date: Tue, 11 Aug 2026 18:49:21 +0800	[thread overview]
Message-ID: <20260811104921.8099-1-liu83783@gmail.com> (raw)
In-Reply-To: <20260811-obsession-propeller-eiskalt-a2ca8b0a1017@brauner>

Thanks to both of you for the replies.

@legion: The /proc/keys and /proc/interrupts case you raised is one
I missed, and it shows that a new mount can grant access that the
container's creators do not want to grant. I withdraw the suggestion.

@Brauner: you're right, and I apologize for the length. I'll keep
future questions to the bare minimum.

Thanks,
Gu Lingguang

      reply	other threads:[~2026-08-11 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 13:23 [RFC] mnt_already_visible(): should regular-file mountpoints participate in the visibility check? GuLingguang
2026-08-11  9:16 ` Alexey Gladkov
2026-08-11  9:19 ` Christian Brauner
2026-08-11 10:49   ` Gu Lingguang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260811104921.8099-1-liu83783@gmail.com \
    --to=liu83783@gmail.com \
    --cc=brauner@kernel.org \
    --cc=containers@lists.linux.dev \
    --cc=cyphar@cyphar.com \
    --cc=ebiederm@xmission.com \
    --cc=legion@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.