From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 4a9bca86806f
Date: Wed, 12 Jan 2022 09:57:29 -0800 [thread overview]
Message-ID: <20220112175729.GB19198@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 posting is all bug fixes, but I /would/ like to
complete reviews of the ioctl removal series that I posted yesterday.
The new head of the for-next branch is commit:
4a9bca86806f xfs: fix online fsck handling of v5 feature bits on secondary supers
New Commits:
Darrick J. Wong (2):
[65552b02a10a] xfs: take the ILOCK when readdir inspects directory mapping data
[4a9bca86806f] xfs: fix online fsck handling of v5 feature bits on secondary supers
Code Diffstat:
fs/xfs/scrub/agheader.c | 53 ++++++++++++++++++++--------------------
fs/xfs/scrub/agheader_repair.c | 12 +++++++++
fs/xfs/xfs_dir2_readdir.c | 55 +++++++++++++++++++++++++++---------------
3 files changed, 73 insertions(+), 47 deletions(-)
reply other threads:[~2022-01-12 17:57 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=20220112175729.GB19198@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