From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] iomap: fixes for 5.17-rc3
Date: Fri, 4 Feb 2022 18:46:13 -0800 [thread overview]
Message-ID: <20220205024613.GV8313@magnolia> (raw)
Hi Linus,
Please pull this branch containing a single bugfix for iomap for
5.17-rc3. The fix should eliminate occasional complaints about stall
warnings when a lot of writeback IO completes all at once and we have to
then go clearing status on a large number of folios.
As usual, I did a test-merge with upstream master as of a few minutes
ago, and didn't see any conflicts. Please let me know if you encounter
any problems.
--D
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.17-fixes-1
for you to fetch changes up to ebb7fb1557b1d03b906b668aa2164b51e6b7d19a:
xfs, iomap: limit individual ioend chain lengths in writeback (2022-01-26 09:19:20 -0800)
----------------------------------------------------------------
Fixes for 5.17-rc2:
- Limit the length of ioend chains in writeback so that we don't trip
the softlockup watchdog and to limit long tail latency on clearing
PageWriteback.
----------------------------------------------------------------
Dave Chinner (1):
xfs, iomap: limit individual ioend chain lengths in writeback
fs/iomap/buffered-io.c | 52 ++++++++++++++++++++++++++++++++++++++++++++++----
fs/xfs/xfs_aops.c | 16 +++++++++++++++-
include/linux/iomap.h | 2 ++
3 files changed, 65 insertions(+), 5 deletions(-)
next reply other threads:[~2022-02-05 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 2:46 Darrick J. Wong [this message]
2022-02-05 17:29 ` [GIT PULL] iomap: fixes for 5.17-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=20220205024613.GV8313@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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 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.