From: Eric Sandeen <sandeen@sandeen.net>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfsprogs: for-next updated to a023e1a
Date: Thu, 31 May 2018 14:16:30 -0500 [thread overview]
Message-ID: <bcd26b6c-0c04-1e6b-424d-c2dc82949ca8@sandeen.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2465 bytes --]
Hi folks,
The for-next branch of the xfsprogs repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.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.
I'm still holding out a little hope that we can get the config file
code into the xfsprogs 4.17 release, so if that gels within the next
week or so, I'll do it.
If you have other small bugfixes I've missed now's the time. Anything
else feature-wise, we'll hold off for xfsprogs 4.18.
Thanks,
-Eric
The new head of the for-next branch is commit:
a023e1a xfs_db: Don't ASSERT on unrecognized metadata
New Commits:
Carlos Maiolino (1):
[a023e1a] xfs_db: Don't ASSERT on unrecognized metadata
Darrick J. Wong (8):
[7931f86] xfs_repair: fix integer handling issues
[c2b571f] xfs_buflock: ignore if buffer already locked
[ece9fa6] xfs_buflock: record line number of trace where we locked the buf
[184798f] xfs_buflock: record buffer initialization
[e3f20e6] fsck: fix more bashisms
[6c05cc5] xfs_scrub: actually check for errors coming from close()
[7856ed0] xfs_io: fix null pointer deref when complaining about scrub comm
[87a271c] xfs_db: handle realtime bitmap / summary files as text
Eric Sandeen (2):
[585acbe] xfs_repair: fix libxfs api violations in quota repair code
[14c57d5] mkfs.xfs: if either sunit or swidth is nonzero, the other must
Goldwyn Rodrigues (1):
[25b4549] xfs_io: Make copy_range arguments understand *iB values
Code Diffstat:
db/print.c | 5 +++--
db/type.c | 12 ++++++------
fsck/xfs_fsck.sh | 12 +++++-------
io/copy_file_range.c | 28 +++++++++++++++-------------
io/scrub.c | 3 +--
libxfs/libxfs_api_defs.h | 4 ++++
mkfs/xfs_mkfs.c | 3 ++-
repair/dinode.c | 13 +++++++------
repair/sb.c | 3 ++-
scrub/phase1.c | 6 +++++-
scrub/phase3.c | 27 +++++++++++++++++++++++++--
scrub/phase5.c | 8 ++++++--
scrub/phase6.c | 10 +++++++---
scrub/vfs.c | 4 +++-
tools/xfsbuflock.py | 22 +++++++++++++++++++---
15 files changed, 110 insertions(+), 50 deletions(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
reply other threads:[~2018-05-31 19:16 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=bcd26b6c-0c04-1e6b-424d-c2dc82949ca8@sandeen.net \
--to=sandeen@sandeen.net \
--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 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.