From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: more fixes for 4.17-rc4
Date: Fri, 4 May 2018 15:15:13 -0700 [thread overview]
Message-ID: <20180504221513.GT26569@magnolia> (raw)
Hi Linus,
I've got one more bug fix for xfs for 4.17-rc4, which caps the amount of
data we try to handle in one dedupe request so that userspace can't
livelock the kernel.
This series has been run through a full xfstests run during the week and
through a quick xfstests run against this morning's master, with no ajor
failures reported. Let me know if there are any merge problems.
--D
The following changes since commit 7b38460dc8e4eafba06c78f8e37099d3b34d473c:
xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE (2018-04-17 19:10:15 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.17-fixes-2
for you to fetch changes up to 021ba8e98fe5c6691b3cc3669faafa02403aa211:
xfs: cap the length of deduplication requests (2018-05-02 09:21:33 -0700)
----------------------------------------------------------------
Changes since last update:
- Cap the maximum length of a deduplication request at MAX_RW_COUNT/2
to avoid kernel livelock due to excessively large IO requests.
----------------------------------------------------------------
Darrick J. Wong (1):
xfs: cap the length of deduplication requests
fs/xfs/xfs_file.c | 10 ++++++++++
1 file changed, 10 insertions(+)
reply other threads:[~2018-05-04 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180504221513.GT26569@magnolia \
--to=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox