From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
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] xfs: fixes for 5.3-rc5
Date: Thu, 15 Aug 2019 10:13:47 -0700 [thread overview]
Message-ID: <20190815171347.GD15186@magnolia> (raw)
Hi Linus,
Here are a few more bug fixes that trickled in since -rc3. It's
survived the usual xfstests runs and merges cleanly with this morning's
master. Please let me know if anything strange happens.
--D
The following changes since commit afa1d96d1430c2138c545fb76e6dcb21222098d4:
xfs: Fix possible null-pointer dereferences in xchk_da_btree_block_check_sibling() (2019-07-30 11:28:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.3-fixes-2
for you to fetch changes up to 8612de3f7ba6e900465e340516b8313806d27b2d:
xfs: don't crash on null attr fork xfs_bmapi_read (2019-08-12 09:32:44 -0700)
----------------------------------------------------------------
Changes since last update:
- Fix crashes when the attr fork isn't present due to errors but inode
inactivation tries to zap the attr data anyway.
- Convert more directory corruption debugging asserts to actual
EFSCORRUPTED returns instead of blowing up later on.
- Don't fail writeback just because we ran out of memory allocating
metadata log data.
----------------------------------------------------------------
Darrick J. Wong (2):
xfs: remove more ondisk directory corruption asserts
xfs: don't crash on null attr fork xfs_bmapi_read
Tetsuo Handa (1):
fs: xfs: xfs_log: Don't use KM_MAYFAIL at xfs_log_reserve().
fs/xfs/libxfs/xfs_bmap.c | 29 +++++++++++++++++++++--------
fs/xfs/libxfs/xfs_da_btree.c | 19 ++++++++++++-------
fs/xfs/libxfs/xfs_dir2_node.c | 3 ++-
fs/xfs/xfs_log.c | 5 +----
4 files changed, 36 insertions(+), 20 deletions(-)
next reply other threads:[~2019-08-15 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 17:13 Darrick J. Wong [this message]
2019-08-15 19:38 ` [GIT PULL] xfs: fixes for 5.3-rc5 Linus Torvalds
2019-08-15 20:05 ` Darrick J. Wong
2019-08-15 21:33 ` Linus Torvalds
2019-08-15 19:45 ` 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=20190815171347.GD15186@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.