Re: [PATCH 02/13] gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: Eric Biggers <ebiggers@xxxxxxxxxx>
Subject
: Re: [PATCH 02/13] gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
From
: Christoph Hellwig <hch@xxxxxx>
Date
: Fri, 8 Jan 2021 09:54:58 +0100
Cc
: linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, "Theodore Ts'o" <tytso@xxxxxxx>, Christoph Hellwig <hch@xxxxxx>
In-reply-to
: <
20210105005452.92521-3-ebiggers@kernel.org
>
References
: <
20210105005452.92521-1-ebiggers@kernel.org
> <
20210105005452.92521-3-ebiggers@kernel.org
>
User-agent
: Mutt/1.5.17 (2007-11-01)
Looks good, Reviewed-by: Christoph Hellwig <hch@xxxxxx>
References
:
[PATCH 00/13] lazytime fixes and cleanups
From:
Eric Biggers
[PATCH 02/13] gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
From:
Eric Biggers
Prev by Date:
Re: [PATCH 01/13] fs: avoid double-writing inodes on lazytime expiration
Next by Date:
Re: [PATCH 03/13] fs: only specify I_DIRTY_TIME when needed in generic_update_time()
Previous by thread:
[PATCH 02/13] gfs2: don't worry about I_DIRTY_TIME in gfs2_fsync()
Next by thread:
[PATCH 05/13] fs: don't call ->dirty_inode for lazytime timestamp updates
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]