lazytime fixes

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

To: "Theodore Ts'o" <tytso@xxxxxxx>, Jaegeuk Kim <jaegeuk@xxxxxxxxxx>, Chao Yu <chao@xxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, Richard Weinberger <richard@xxxxxx>, linux-xfs@xxxxxxxxxxxxxxx
Subject: lazytime fixes
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 25 Mar 2020 13:28:21 +0100
Cc: Eric Biggers <ebiggers@xxxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-mtd@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx

Hi all,

this is my take on Teds take on Erics bug report about ext4 inodes
beeing kept dirty after sync.  After looking into the area I found
a few other loose ends, so the series has grown a bit.

Follow-Ups:
- [PATCH 4/4] fs: clean up generic_update_time a bit
  - From: Christoph Hellwig
- [PATCH 3/4] fs: don't call ->dirty_inode for lazytime timestamp updates
  - From: Christoph Hellwig
- [PATCH 2/4] fs: avoid double-writing the inode on a lazytime expiration
  - From: Christoph Hellwig
- [PATCH 1/4] ubifs: remove broken lazytime support
  - From: Christoph Hellwig

Prev by Date: [PATCH 4/4] fs: clean up generic_update_time a bit
Next by Date: Re: [PATCH v10 24/25] fuse: Convert from readpages to readahead
Previous by thread: [PATCH 1/2] ext4: return lblk from ext4_find_entry
Next by thread: [PATCH 1/4] ubifs: remove broken lazytime support
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux