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.5-rc3
Date: Sun, 22 Dec 2019 08:32:18 -0800 [thread overview]
Message-ID: <20191222163218.GR7489@magnolia> (raw)
Hi Linus,
Please pull these bug fixes for 5.5-rc3, which fix a few bugs that could
lead to corrupt files, fsck complaints, and filesystem crashes.
The branch has survived a couple of days 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 e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.5-fixes-2
for you to fetch changes up to 5084bf6b2006fcd46f1e44e3c51b687507b362e2:
xfs: Make the symbol 'xfs_rtalloc_log_count' static (2019-12-20 08:07:31 -0800)
----------------------------------------------------------------
Fixes for 5.5:
- Minor documentation fixes
- Fix a file corruption due to read racing with an insert range
operation.
- Fix log reservation overflows when allocating large rt extents
- Fix a buffer log item flags check
- Don't allow administrators to mount with sunit= options that will
cause later xfs_repair complaints about the root directory being
suspicious because the fs geometry appeared inconsistent
- Fix a non-static helper that should have been static
----------------------------------------------------------------
Brian Foster (2):
xfs: stabilize insert range start boundary to avoid COW writeback race
xfs: use bitops interface for buf log item AIL flag check
Chen Wandun (1):
xfs: Make the symbol 'xfs_rtalloc_log_count' static
Darrick J. Wong (5):
xfs: fix log reservation overflows when allocating large rt extents
libxfs: resync with the userspace libxfs
xfs: refactor agfl length computation function
xfs: split the sunit parameter update into two parts
xfs: don't commit sunit/swidth updates to disk if that would cause repair failures
Randy Dunlap (1):
xfs: fix Sphinx documentation warning
Documentation/admin-guide/xfs.rst | 2 +-
fs/xfs/libxfs/xfs_alloc.c | 18 ++--
fs/xfs/libxfs/xfs_bmap.c | 5 +-
fs/xfs/libxfs/xfs_dir2.c | 21 +++++
fs/xfs/libxfs/xfs_dir2_priv.h | 29 ++-----
fs/xfs/libxfs/xfs_dir2_sf.c | 6 +-
fs/xfs/libxfs/xfs_ialloc.c | 64 +++++++++++++++
fs/xfs/libxfs/xfs_ialloc.h | 1 +
fs/xfs/libxfs/xfs_trans_resv.c | 96 +++++++++++++++++-----
fs/xfs/xfs_bmap_util.c | 12 +++
fs/xfs/xfs_buf_item.c | 2 +-
fs/xfs/xfs_mount.c | 168 ++++++++++++++++++++++++++------------
fs/xfs/xfs_trace.h | 21 +++++
13 files changed, 341 insertions(+), 104 deletions(-)
next reply other threads:[~2019-12-22 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 16:32 Darrick J. Wong [this message]
2019-12-22 19:10 ` [GIT PULL] xfs: fixes for 5.5-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=20191222163218.GR7489@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 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).