All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: David Howells <dhowells@redhat.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
	Christoph Hellwig <hch@lst.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH v2] fs: rename S_KERNEL_FILE
Date: Fri, 28 Jan 2022 13:17:22 +0000	[thread overview]
Message-ID: <YfPs4hpWtFziiO2c@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <922909.1643369759@warthog.procyon.org.uk>

On Fri, Jan 28, 2022 at 11:35:59AM +0000, David Howells wrote:

> > Whether deny rmdir should have its own flag or not I don't know,
> > but from ovl POV I *think* it should not be a problem to deny rmdir
> > for the ovl upper/work dirs as long as ovl is mounted(?).
> 
> What's the consequence of someone rearranging the directories directly in the
> contributing dirs whilst there's an overlay over them?

"Don't do it, then - presumably the kernel won't panic, but don't expect it to
try and invent nice semantics for the crap you are trying to pull"

  reply	other threads:[~2022-01-28 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  7:47 [PATCH v2] fs: rename S_KERNEL_FILE Christoph Hellwig
2022-01-28  9:01 ` Chaitanya Kulkarni
2022-01-28 10:12 ` David Howells
2022-01-28 11:09   ` Amir Goldstein
2022-01-28 11:35     ` David Howells
2022-01-28 13:17       ` Al Viro [this message]
2022-01-28 15:24         ` Amir Goldstein

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=YfPs4hpWtFziiO2c@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=chaitanyak@nvidia.com \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    /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.