From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Martijn Coenen <maco@android.com>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/4 v2] writeback: Lazytime handling fix and cleanups
Date: Thu, 11 Jun 2020 10:11:51 +0200 [thread overview]
Message-ID: <20200611075033.1248-1-jack@suse.cz> (raw)
Hello,
this patch series fixes an issue with handling of lazy inode timestamp
writeback which could result in missed background writeback of an inode
or missed update of inode timestamps during sync(2). It also somewhat
simplifies the writeback code handling of lazy inode timestamp updates.
Changes since v1:
* Split off locking change for i_io_list manipulation to a separate patch
* Renamed older_than_this to dirtied_before
* Renamed __redirty_tail() to redirty_tail_locked()
* Other minor style fixes
Honza
Previous versions:
Link: http://lore.kernel.org/r/20200601091202.31302-1-jack@suse.cz
next reply other threads:[~2020-06-11 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 8:11 Jan Kara [this message]
2020-06-11 8:11 ` [PATCH 1/4] writeback: Protect inode->i_io_list with inode->i_lock Jan Kara
2020-06-12 7:45 ` Martijn Coenen
2020-06-15 6:27 ` Christoph Hellwig
2020-06-11 8:11 ` [PATCH 2/4] writeback: Avoid skipping inode writeback Jan Kara
2020-06-12 8:03 ` Martijn Coenen
2020-06-15 7:15 ` Jan Kara
2020-06-15 6:27 ` Christoph Hellwig
2020-06-15 7:15 ` Jan Kara
2020-06-11 8:11 ` [PATCH 3/4] writeback: Fix sync livelock due to b_dirty_time processing Jan Kara
2020-06-15 6:27 ` Christoph Hellwig
2020-06-11 8:11 ` [PATCH 4/4] writeback: Drop I_DIRTY_TIME_EXPIRE Jan Kara
2020-09-02 17:20 ` Darrick J. Wong
2020-09-03 10:10 ` 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=20200611075033.1248-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=maco@android.com \
/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).