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, Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH-v2 0/2] lazytime bug fixes for 4.0
Date: Mon, 16 Mar 2015 15:14:18 -0400	[thread overview]
Message-ID: <1426533260-3305-1-git-send-email-tytso@mit.edu> (raw)

Apologies for the delay, but Vault and LSF/MM kept me busy last week.
These patches fix the issues which Jan pointed out.  They aren't
serious; this fixes ab issue which might result in some timestamps
would end up becoming stale until the file system unmounted or
syncfs(2) is run on it.  Still, it's nice to fix them so the guarantee
is as they have been documented and as people would expect.

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(-)

-- 
2.3.0


             reply	other threads:[~2015-03-16 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 19:14 Theodore Ts'o [this message]
2015-03-16 19:14 ` [PATCH-v2 1/2] fs: make sure the timestamps for lazytime inodes eventually get written Theodore Ts'o
2015-03-16 21:34   ` Andreas Dilger
2015-03-17 10:33     ` Jan Kara
2015-03-17 15:53       ` Theodore Ts'o
2015-03-17 15:09     ` Theodore Ts'o
2015-03-17 10:29   ` Jan Kara
2015-03-16 19:14 ` [PATCH-v2 2/2] fs: add dirtytime_expire_seconds sysctl Theodore Ts'o
2015-03-17 10:30   ` Jan Kara

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=1426533260-3305-1-git-send-email-tytso@mit.edu \
    --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).