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: fixes for 4.15-rc7
Date: Fri, 5 Jan 2018 09:42:23 -0800 [thread overview]
Message-ID: <20180105174223.GJ5602@magnolia> (raw)
Hi Linus,
I have just a few fixes for bugs and resource cleanup problems this week.
It merges cleanly against your tree as of ~5min ago.
--Darrick
The following changes since commit 68c58e9b9a88c1a9d0c2eaf6c7acefb00f5fbbfb:
xfs: only skip rmap owner checks for unknown-owner rmap removal (2017-12-21 08:48:38 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.15-fixes-10
for you to fetch changes up to b4d8ad7fd3a18e6d92d4ebe858185c704604a57d:
xfs: fix s_maxbytes overflow problems (2018-01-02 10:16:32 -0800)
----------------------------------------------------------------
Changes since last update:
- Fix resource cleanup of failed quota initialization
- Fix integer overflow problems wrt s_maxbytes
----------------------------------------------------------------
Aliaksei Karaliou (2):
xfs: quota: fix missed destroy of qi_tree_lock
xfs: quota: check result of register_shrinker()
Darrick J. Wong (1):
xfs: fix s_maxbytes overflow problems
fs/xfs/xfs_aops.c | 4 ++--
fs/xfs/xfs_iomap.c | 2 +-
fs/xfs/xfs_qm.c | 46 ++++++++++++++++++++++++++++++----------------
3 files changed, 33 insertions(+), 19 deletions(-)
reply other threads:[~2018-01-05 17:42 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=20180105174223.GJ5602@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;
as well as URLs for NNTP newsgroup(s).