From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: torvalds@linux-foundation.org
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
sandeen@sandeen.net
Subject: [GIT PULL] xfs: fixes for v4.20-rc2
Date: Thu, 8 Nov 2018 14:40:00 -0800 [thread overview]
Message-ID: <20181108224000.GB15721@magnolia> (raw)
Hi Linus,
Here's the start of the stabilization fixes for 4.20. Let me know if
there are any problems merging; I just did it against current master and
saw no issues.
--D
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.20-fixes-1
for you to fetch changes up to 837514f7a4ca4aca06aec5caa5ff56d33ef06976:
xfs: fix overflow in xfs_attr3_leaf_verify (2018-11-06 07:50:50 -0800)
----------------------------------------------------------------
Changes since last update:
- fix incorrect dropping of error code from bmap
- print buffer offsets instead of useless hashed pointers when dumping
corrupt metadata
- fix integer overflow in attribute verifier
----------------------------------------------------------------
Christophe JAILLET (1):
xfs: Fix error code in 'xfs_ioc_getbmap()'
Darrick J. Wong (1):
xfs: print buffer offsets when dumping corrupt buffers
Dave Chinner (1):
xfs: fix overflow in xfs_attr3_leaf_verify
fs/xfs/libxfs/xfs_attr_leaf.c | 11 +++++++++--
fs/xfs/xfs_ioctl.c | 2 +-
fs/xfs/xfs_message.c | 2 +-
3 files changed, 11 insertions(+), 4 deletions(-)
next reply other threads:[~2018-11-08 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 22:40 Darrick J. Wong [this message]
2018-11-08 23:55 ` [GIT PULL] xfs: fixes for v4.20-rc2 Linus Torvalds
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=20181108224000.GB15721@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--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).