linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>
Cc: jack@suse.cz, torvalds@linux-foundation.org, viro@zeniv.linux.org.uk
Subject: [GIT PULL] Re: [PATCH-v3 0/2] lazytime fixes for 4.0
Date: Tue, 31 Mar 2015 19:00:09 -0400	[thread overview]
Message-ID: <20150331230009.GC22180@thunk.org> (raw)
In-Reply-To: <20150324231252.GB28505@thunk.org>

On Tue, Mar 24, 2015 at 07:12:52PM -0400, Theodore Ts'o wrote:
> 
> Ping?  Al, are you OK with taking these patches and sending them to
> Linus?

Ping**2?

Linus, do you want to pull these two patches before 4.0 gets released?
Jan Kara has reviewed them.

						- Ted

P.S.  I just recently generated GPG subkey so you might need to run
the command "gpg --recv-key C11804F0" in order to fetch the subkey to
verify the tag.


The following changes since commit 13a7a6ac0a11197edcd0f756a035f472b42cdf8b:

  Linux 4.0-rc2 (2015-03-03 09:04:59 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/lazytime_fix

for you to fetch changes up to 1efff914afac8a965ad63817ecf8861a927c2ace:

  fs: add dirtytime_expire_seconds sysctl (2015-03-17 12:23:32 -0400)

----------------------------------------------------------------
This fixes a problem in the lazy time patches, which can cause
frequently updated inods to never have their timestamps updated.
These changes guarantee that no timestamp on disk will be stale by
more than 24 hours.

----------------------------------------------------------------
Theodore Ts'o (2):
      fs: make sure the timestamps for lazytime inodes eventually get written
      fs: add dirtytime_expire_seconds sysctl

 fs/fs-writeback.c         | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++------
 include/linux/fs.h        |  1 +
 include/linux/writeback.h |  3 ++
 kernel/sysctl.c           |  8 +++++
 4 files changed, 95 insertions(+), 10 deletions(-)

      reply	other threads:[~2015-03-31 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  0:08 [PATCH-v3 0/2] lazytime fixes for 4.0 Theodore Ts'o
2015-03-19  0:08 ` [PATCH-v3 1/2] fs: make sure the timestamps for lazytime inodes eventually get written Theodore Ts'o
2015-03-19  0:08 ` [PATCH-v3 2/2] fs: add dirtytime_expire_seconds sysctl Theodore Ts'o
2015-03-24 23:12 ` [PATCH-v3 0/2] lazytime fixes for 4.0 Theodore Ts'o
2015-03-31 23:00   ` Theodore Ts'o [this message]

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=20150331230009.GC22180@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).