Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "hch@xxxxxx" <hch@xxxxxx>
Subject: Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
From: David Howells <dhowells@xxxxxxxxxx>
Date: Fri, 31 Jan 2020 08:04:28 +0000
Cc: dhowells@xxxxxxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, Omar Sandoval <osandov@xxxxxxxxxxx>, Amir Goldstein <amir73il@xxxxxxxxx>, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>, "lsf-pc@xxxxxxxxxxxxxxxxxxxxxxxxxx" <lsf-pc@xxxxxxxxxxxxxxxxxxxxxxxxxx>, "miklos@xxxxxxxxxx" <miklos@xxxxxxxxxx>, "linux-fsdevel@xxxxxxxxxxxxxxx" <linux-fsdevel@xxxxxxxxxxxxxxx>, "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
In-reply-to: <20200131053150.GB17457@lst.de>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

hch@xxxxxx <hch@xxxxxx> wrote:

> > I'm using direct I/O, so I'm assuming I don't need to fsync().
> 
> Direct I/O of course requires fsync.  What makes you think different?

I guess that's fair.  Even if the data makes it directly to storage, that's
not a guarantee that the metadata does.

David

Follow-Ups:
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Amir Goldstein

References:
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: hch@xxxxxx
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Al Viro
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Omar Sandoval
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Al Viro
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Omar Sandoval
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Al Viro
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Omar Sandoval
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Amir Goldstein
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Omar Sandoval
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: Al Viro
- Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
  - From: David Howells

Prev by Date: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale
Next by Date: Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
Previous by thread: Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
Next by thread: Re: [LSF/MM/BPF TOPIC] Allowing linkat() to replace the destination
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]