All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] man: document XFS_XFLAG_APPEND behavior for directories
Date: Wed, 24 Feb 2021 16:31:47 -0600	[thread overview]
Message-ID: <cfaa010e-d348-7639-e680-7e7cbc8bfa77@redhat.com> (raw)
In-Reply-To: <20210224222913.GF7272@magnolia>

On 2/24/21 4:29 PM, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> For directories, the APPEND flag means that files cannot be unlinked
> from the directory.  Files can be linked in or created, just not
> unlinked.  Document this behavior, since it's been in the VFS for years
> though not explicitly mentioned.  This patch is in preparation for
> trying to hoist the fsgetxattr ioctl documentation to the man-pages
> project.

sounds good.

> 
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

> ---
>  man/man2/ioctl_xfs_fsgetxattr.2 |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/man/man2/ioctl_xfs_fsgetxattr.2 b/man/man2/ioctl_xfs_fsgetxattr.2
> index e2cbfca3..2c626a7e 100644
> --- a/man/man2/ioctl_xfs_fsgetxattr.2
> +++ b/man/man2/ioctl_xfs_fsgetxattr.2
> @@ -104,6 +104,7 @@ will be returned.
>  .B XFS_XFLAG_APPEND
>  The file is append-only - it can only be opened in append mode for
>  writing.
> +For directories, this means that files cannot be unlinked from this directory.
>  Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE
>  capability can set or clear this flag.
>  .TP
> 


  reply	other threads:[~2021-02-24 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 22:29 [PATCH] man: document XFS_XFLAG_APPEND behavior for directories Darrick J. Wong
2021-02-24 22:31 ` Eric Sandeen [this message]
2021-02-25 18:57 ` Christoph Hellwig

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=cfaa010e-d348-7639-e680-7e7cbc8bfa77@redhat.com \
    --to=sandeen@redhat.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.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.