All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH] fsync.2: no writability requirements, must operate on directories
Date: Thu, 03 Aug 2023 17:07:00 +0100	[thread overview]
Message-ID: <87y1isnm7w.fsf@gentoo.org> (raw)
In-Reply-To: <oc67sum2hk73gl7oim7kitbqac6gcursqcxf6j2qjxzzdzgbxq@afirbuozty2f>


наб <nabijaczleweli@nabijaczleweli.xyz> writes:

> [[PGP Signed Part:Undecided]]
> POSIX has for a long time implied that directories are fsyncable,
> and since Issue 8 explicitly specifies directory syncing semantics:
>   https://www.austingroupbugs.net/view.php?id=672
>
> Simultaneously, directories being unopenable for writing is a
> Longest-Standing UNIX Semantic, present in the UNIX Programmer's Manual
> under directory (V), and has always been enshrined in the standards.
>
> Kill the FUD that says that some UNIXes require the fd to be writable:
> they /must not/ and this confuses users:
>   https://101010.pl/@eater@cijber.social/110824211348995583

Must not, or need not be?

>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
>  man2/fsync.2 | 6 ------
>  1 file changed, 6 deletions(-)
>
> diff --git a/man2/fsync.2 b/man2/fsync.2
> index 1043e6a1b..9ced40b28 100644
> --- a/man2/fsync.2
> +++ b/man2/fsync.2
> @@ -155,12 +155,6 @@ .SH VERSIONS
>  .\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
>  .\" -1: unavailable, 0: ask using sysconf().
>  .\" glibc defines them to 1.
> -.PP
> -On some UNIX systems (but not Linux),
> -.I fd
> -must be a
> -.I writable
> -file descriptor.
>  .SH STANDARDS
>  POSIX.1-2008.
>  .SH HISTORY


  parent reply	other threads:[~2023-08-03 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 11:52 [PATCH] fsync.2: no writability requirements, must operate on directories наб
2023-08-03 13:22 ` Alejandro Colomar
2023-08-03 13:32   ` Alejandro Colomar
2023-08-03 14:20   ` наб
2023-08-03 15:18     ` Jakub Wilk
2023-08-03 16:54       ` наб
2023-08-03 18:59         ` G. Branden Robinson
2023-08-04 10:07     ` Guillem Jover
2023-08-04 15:03       ` наб
2023-08-04 15:03         ` [PATCH v3] fsync.2: no writability requirements наб
2023-08-11 23:01           ` Alejandro Colomar
2023-08-03 16:07 ` Sam James [this message]
2023-08-03 16:44   ` [PATCH] fsync.2: no writability requirements, must operate on directories наб

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=87y1isnm7w.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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.