From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Ted Tso <tytso@mit.edu>, Martijn Coenen <maco@android.com>,
tj@kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/3] writeback: Lazytime handling fix and cleanups
Date: Wed, 10 Jun 2020 12:04:02 +0200 [thread overview]
Message-ID: <20200610100402.GA25104@quack2.suse.cz> (raw)
In-Reply-To: <20200601091202.31302-1-jack@suse.cz>
On Mon 01-06-20 11:18:54, Jan Kara wrote:
> 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.
> Review is welcome!
OK, nobody has replied to this and I have positive feedback from Martijn so
I guess I'll pickup the patches to my tree so that they get some testing in
linux-next and push them to Linus sometime next week.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-06-10 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:18 [PATCH 0/3] writeback: Lazytime handling fix and cleanups Jan Kara
2020-06-01 9:18 ` [PATCH 1/3] writeback: Avoid skipping inode writeback Jan Kara
2020-06-05 14:11 ` Sasha Levin
2020-06-10 15:02 ` Christoph Hellwig
2020-06-10 15:30 ` Jan Kara
2020-06-01 9:18 ` [PATCH 2/3] writeback: Fix sync livelock due to b_dirty_time processing Jan Kara
2020-06-10 15:06 ` Christoph Hellwig
2020-06-10 15:54 ` Jan Kara
2020-06-10 15:58 ` Christoph Hellwig
2020-06-01 9:18 ` [PATCH 3/3] writeback: Drop I_DIRTY_TIME_EXPIRE Jan Kara
2020-06-10 15:11 ` Christoph Hellwig
2020-06-10 16:20 ` Jan Kara
2020-06-10 10:04 ` Jan Kara [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=20200610100402.GA25104@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=maco@android.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.