From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Ring <stefanrin@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs_metadump: Extend zapping to multi fsb dir blocks
Date: Tue, 23 Oct 2018 10:10:22 -0500 [thread overview]
Message-ID: <c07f1405-0ff0-71e1-56bb-d327d1acd564@sandeen.net> (raw)
In-Reply-To: <20181011194424.20306-2-stefanrin@gmail.com>
On 10/11/18 2:44 PM, Stefan Ring wrote:
> The processing for data zeroing was never added to process_multi_fsb_objects.
> It is now the same thing that process_single_fsb_objects does.
First, thanks for doing this, seems about right.
But I could use more changelog words here. ;)
AFAICT, the intent was for process_multi_fsb_objects to call
process_dir_data_block() in order to handle the zeroing for multi-fsb
objects, so at least some of the cases /were/ handled, right?
Your patch seems to be splitting that 3 ways, so we go to
process_dir_free_block or process_dir_leaf_block or process_dir_data_block,
the first two are new cases that are now handled? (I do see that this is
the same as the process_single_fsb_objects code.)
Given the old case:
if ((!obfuscate && !zero_stale_data) ||
o >= mp->m_dir_geo->leafblk) {
ret = write_buf(iocur_top);
it looks like we were just directly writing the leaf blocks and
never obfuscating them, is that correct? I guess I need to go make
some test filesystems... do you know from your testing if this is true?
This seems quite reasonable, I just think it might be doing more
than the changelog says it is...?
-Eric
> ---
> db/metadump.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/db/metadump.c b/db/metadump.c
> index cc2ae9af..ff96860d 100644
> --- a/db/metadump.c
> +++ b/db/metadump.c
> @@ -1862,6 +1862,7 @@ process_multi_fsb_objects(
> typnm_t btype,
> xfs_fileoff_t last)
> {
> + char *dp;
> int ret = 0;
>
> switch (btype) {
> @@ -1902,14 +1903,16 @@ process_multi_fsb_objects(
>
> }
>
> - if ((!obfuscate && !zero_stale_data) ||
> - o >= mp->m_dir_geo->leafblk) {
> - ret = write_buf(iocur_top);
> - goto out_pop;
> + dp = iocur_top->data;
> + if (o >= mp->m_dir_geo->freeblk) {
> + process_dir_free_block(dp);
> + } else if (o >= mp->m_dir_geo->leafblk) {
> + process_dir_leaf_block(dp);
> + } else {
> + process_dir_data_block(
> + dp, o, last == mp->m_dir_geo->fsbcount);
> }
>
> - process_dir_data_block(iocur_top->data, o,
> - last == mp->m_dir_geo->fsbcount);
> iocur_top->need_crc = 1;
> ret = write_buf(iocur_top);
> out_pop:
>
next prev parent reply other threads:[~2018-10-23 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 19:44 [PATCH v3 0/2] Try to squash metadump data leaks Stefan Ring
2018-10-11 19:44 ` [PATCH 1/2] xfs_metadump: Extend zapping to multi fsb dir blocks Stefan Ring
2018-10-23 15:10 ` Eric Sandeen [this message]
2018-10-25 15:08 ` Eric Sandeen
2018-10-25 16:44 ` Stefan Ring
2018-10-11 19:44 ` [PATCH 2/2] xfs_metadump: Zap more stale data Stefan Ring
2018-10-23 15:49 ` Darrick J. Wong
2018-10-25 16:42 ` Stefan Ring
2018-10-26 20:23 ` Stefan Ring
2018-10-26 5:32 ` Stefan Ring
2018-10-25 15:50 ` [PATCH v3 0/2] Try to squash metadump data leaks Eric Sandeen
2018-10-26 0:36 ` Eric Sandeen
2018-10-26 5:29 ` Stefan Ring
2018-10-26 12:36 ` Eric Sandeen
2018-10-26 18:37 ` Stefan Ring
-- strict thread matches above, loose matches on Subject: below --
2018-10-11 19:23 [PATCH v2 " Stefan Ring
2018-10-11 19:23 ` [PATCH 1/2] xfs_metadump: Extend zapping to multi fsb dir blocks Stefan Ring
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=c07f1405-0ff0-71e1-56bb-d327d1acd564@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@vger.kernel.org \
--cc=stefanrin@gmail.com \
/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).