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.4-rc3
Date: Thu, 10 Oct 2019 09:53:14 -0700 [thread overview]
Message-ID: <20191010165314.GP1473994@magnolia> (raw)
Hi Linus,
Please pull this set of changes for 5.4-rc3. There are a couple of
small code cleanups and bug fixes for rounding errors, metadata logging
errors, and an extra layer of safeguards against leaking memory
contents.
The branch has survived a round of xfstests runs and merges cleanly with
this morning's master. Please let me know if anything strange happens.
--D
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.4-fixes-3
for you to fetch changes up to aeea4b75f045294e1c026acc380466daa43afc65:
xfs: move local to extent inode logging into bmap helper (2019-10-09 08:54:30 -0700)
----------------------------------------------------------------
Changes since last update:
- Fix a rounding error in the fallocate code
- Minor code cleanups
- Make sure to zero memory buffers before formatting metadata blocks
- Fix a few places where we forgot to log an inode metadata update
- Remove broken error handling that tried to clean up after a failure
but still got it wrong
----------------------------------------------------------------
Aliasgar Surti (1):
xfs: removed unused error variable from xchk_refcountbt_rec
Bill O'Donnell (1):
xfs: assure zeroed memory buffers for certain kmem allocations
Brian Foster (3):
xfs: log the inode on directory sf to block format change
xfs: remove broken error handling on failed attr sf to leaf change
xfs: move local to extent inode logging into bmap helper
Eric Sandeen (1):
xfs: remove unused flags arg from xfs_get_aghdr_buf()
Max Reitz (1):
xfs: Fix tail rounding in xfs_alloc_file_space()
fs/xfs/libxfs/xfs_ag.c | 5 ++---
fs/xfs/libxfs/xfs_attr_leaf.c | 21 +++------------------
fs/xfs/libxfs/xfs_bmap.c | 6 ++++--
fs/xfs/libxfs/xfs_bmap.h | 3 ++-
fs/xfs/libxfs/xfs_dir2_block.c | 2 +-
fs/xfs/scrub/refcount.c | 3 +--
fs/xfs/xfs_bmap_util.c | 4 +++-
fs/xfs/xfs_buf.c | 12 +++++++++++-
fs/xfs/xfs_log.c | 2 +-
fs/xfs/xfs_log_recover.c | 2 +-
10 files changed, 29 insertions(+), 31 deletions(-)
next reply other threads:[~2019-10-10 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 16:53 Darrick J. Wong [this message]
2019-10-10 18:50 ` [GIT PULL] xfs: fixes for 5.4-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=20191010165314.GP1473994@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.