From: Stefan Ring <stefanrin@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/5] v4 Try to squash metadump data leaks
Date: Fri, 26 Oct 2018 22:19:38 +0200 [thread overview]
Message-ID: <20181026201943.24131-1-stefanrin@gmail.com> (raw)
I reorganized the patches as suggested and fixed the btree case.
Stefan Ring (5):
xfs_metadump: Extend data zapping to XFS_DIR{2,3}_LEAFN_MAGIC blocks
xfs_metadump: Zap multi fsb blocks
xfs_metadump: Zap freeindex blocks in directory inodes
xfs_metadump: Zap unused space in inode btrees
xfs_metadump: Zap dev inodes
db/metadump.c | 119 +++++++++++++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 105 insertions(+), 14 deletions(-)
--
2.14.5
next reply other threads:[~2018-10-27 4:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 20:19 Stefan Ring [this message]
2018-10-26 20:19 ` [PATCH 1/5] xfs_metadump: Extend data zapping to XFS_DIR{2,3}_LEAFN_MAGIC blocks Stefan Ring
2018-10-26 20:19 ` [PATCH 2/5] xfs_metadump: Zap multi fsb blocks Stefan Ring
2018-10-26 20:19 ` [PATCH 3/5] xfs_metadump: Zap freeindex blocks in directory inodes Stefan Ring
2018-10-26 20:19 ` [PATCH 4/5] xfs_metadump: Zap unused space in inode btrees Stefan Ring
2018-10-27 6:23 ` Stefan Ring
2018-10-26 20:19 ` [PATCH 5/5] xfs_metadump: Zap dev inodes Stefan Ring
2018-10-29 15:38 ` Eric Sandeen
2018-10-29 18:33 ` Stefan Ring
2018-10-29 18:37 ` Eric Sandeen
2018-10-29 18:45 ` Stefan Ring
2018-10-26 20:27 ` [PATCH 0/5] v4 Try to squash metadump data leaks Eric Sandeen
2018-10-26 23:33 ` Eric Sandeen
2018-10-26 23:38 ` Darrick J. Wong
2018-10-28 12:38 ` Stefan Ring
2018-10-28 14:36 ` Stefan Ring
2018-10-28 15:42 ` Stefan Ring
2018-10-28 17:13 ` Eric Sandeen
2018-10-30 12:29 ` Stefan Ring
2018-10-30 12:36 ` Eric Sandeen
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=20181026201943.24131-1-stefanrin@gmail.com \
--to=stefanrin@gmail.com \
--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.