From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 6ed6356b0771
Date: Tue, 21 Dec 2021 10:29:46 -0800 [thread overview]
Message-ID: <20211221182946.GX27664@magnolia> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.
This is nominally the 5.17 merge branch, though so far I only have lower
severity bug fixes and a backlog of patch review (nrext64 and
investigating transaction overruns in Dave's log scalability fixes,
iirc) that probably isn't going to make it given the 2.8 days I have
left before winter break.
The new head of the for-next branch is commit:
6ed6356b0771 xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list()
New Commits:
Dan Carpenter (1):
[6ed6356b0771] xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list()
Darrick J. Wong (5):
[47a6df7cd317] xfs: shut down filesystem if we xfs_trans_cancel with deferred work items
[59d7fab2dff9] xfs: fix quotaoff mutex usage now that we don't support disabling it
[7b7820b83f23] xfs: don't expose internal symlink metadata buffers to the vfs
[7993f1a431bc] xfs: only run COW extent recovery when there are no live extents
[e5d1802c70f5] xfs: fix a bug in the online fsck directory leaf1 bestcount check
Dave Chinner (1):
[09654ed8a18c] xfs: check sb_meta_uuid for dabuf buffer recovery
Yang Xu (1):
[132c460e4964] xfs: Fix comments mentioning xfs_ialloc
Code Diffstat:
fs/xfs/scrub/dir.c | 15 +++++++++++----
fs/xfs/scrub/quota.c | 4 ++--
fs/xfs/scrub/repair.c | 3 +++
fs/xfs/scrub/scrub.c | 4 ----
fs/xfs/scrub/scrub.h | 1 -
fs/xfs/xfs_buf_item_recover.c | 2 +-
fs/xfs/xfs_icache.c | 3 ++-
fs/xfs/xfs_ioctl.c | 2 +-
fs/xfs/xfs_ioctl.h | 5 +++--
fs/xfs/xfs_iops.c | 40 ++++------------------------------------
fs/xfs/xfs_log_recover.c | 24 +++++++++++++++++++++++-
fs/xfs/xfs_mount.c | 10 ----------
fs/xfs/xfs_qm_syscalls.c | 11 +----------
fs/xfs/xfs_reflink.c | 5 ++++-
fs/xfs/xfs_super.c | 9 ---------
fs/xfs/xfs_symlink.c | 27 ++++++++++++++++++---------
fs/xfs/xfs_trans.c | 11 ++++++++++-
17 files changed, 83 insertions(+), 93 deletions(-)
reply other threads:[~2021-12-21 18:29 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=20211221182946.GX27664@magnolia \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.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