Re: [PATCH] Btrfs: make full fsyncs always operate on the entire file again

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

 



On Wed, Apr 8, 2020 at 6:07 PM David Sterba <dsterba@xxxxxxx> wrote:
>
> On Tue, Apr 07, 2020 at 11:37:44AM +0100, fdmanana@xxxxxxxxxx wrote:
> > From: Filipe Manana <fdmanana@xxxxxxxx>
>
> I've put the note about revert at the beginning, fixed the comment
> formatting in btrfs_sync_file, and updated the parameters of

I totally missed that when looking at the diff in a console, don't
know what happened.

> copy_inode_items_to_log in btrfs_log_inode so the diff against
> 0a8068a3dd4294 minimal.

Sounds good.

Thanks.

>
> > Fix this by reverting commit 0a8068a3dd4294 ("btrfs: make ranged full fsyncs
> > more efficient") since there is no easy way to work around it.
>
> Oh well, you tried and that's appreciated, but the fsync matters are
> undoubtedly complicated. Patch added to misc-next and will go to
> upcoming rc, thanks.



[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux