From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Writeback fixes for 5.9-rc3
Date: Fri, 28 Aug 2020 17:03:55 +0200 [thread overview]
Message-ID: <20200828150355.GA4614@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git writeback_for_v5.9-rc3
to get fixes for writeback code occasionally skipping writeback of some
inodes or livelocking sync(2).
Top of the tree is 5fcd57505c00. The full shortlog is:
Jan Kara (4):
writeback: Protect inode->i_io_list with inode->i_lock
writeback: Avoid skipping inode writeback
writeback: Fix sync livelock due to b_dirty_time processing
writeback: Drop I_DIRTY_TIME_EXPIRE
The diffstat is
fs/ext4/inode.c | 2 +-
fs/fs-writeback.c | 103 ++++++++++++++++++++-------------------
fs/xfs/libxfs/xfs_trans_inode.c | 4 +-
include/linux/fs.h | 7 ++-
include/trace/events/writeback.h | 14 +++---
5 files changed, 67 insertions(+), 63 deletions(-)
Thanks
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2020-08-28 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 15:03 Jan Kara [this message]
2020-08-28 19:58 ` [GIT PULL] Writeback fixes for 5.9-rc3 pr-tracker-bot
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=20200828150355.GA4614@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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