From: Jan Tulak <jtulak@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: Jan Tulak <jtulak@redhat.com>
Subject: [PATCH 2/2] xfsprogs: update man for metadump about dirty log/obfuscation issue
Date: Thu, 13 Apr 2017 10:13:54 +0200 [thread overview]
Message-ID: <20170413081354.22170-3-jtulak@redhat.com> (raw)
In-Reply-To: <20170413081354.22170-1-jtulak@redhat.com>
This is something that should be documented, as it is not obvious to
everyone.
Signed-off-by: Jan Tulak <jtulak@redhat.com>
---
man/man8/xfs_metadump.8 | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/man/man8/xfs_metadump.8 b/man/man8/xfs_metadump.8
index 3731d6a..1b40fb8 100644
--- a/man/man8/xfs_metadump.8
+++ b/man/man8/xfs_metadump.8
@@ -59,6 +59,12 @@ options where
are not obfuscated. Names between 5 and 8 characters in length inclusively
are partially obfuscated.
.PP
+Log recovery of an obfuscated metadata image can leak
+unobfuscated metadata and/or cause image corruption. Please mount
+the source filesystem to clean the log or disable obfuscation, if possible.
+If you have to obfuscate an image with a dirty log, tell about it to whoever
+you are sending the image to.
+.PP
.B xfs_metadump
should not be used for any purposes other than for debugging and reporting
filesystem problems. The most common usage scenario for this tool is when
--
2.1.4
next prev parent reply other threads:[~2017-04-13 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 8:13 [PATCH 0/2 v2] xfsprogs: metadump warns about dirty journal Jan Tulak
2017-04-13 8:13 ` [PATCH 1/2] metadump: warn about corruption if log is dirty Jan Tulak
2017-04-13 11:54 ` Brian Foster
2017-06-15 0:06 ` Eric Sandeen
2017-06-15 11:23 ` Brian Foster
2017-04-13 8:13 ` Jan Tulak [this message]
2017-04-13 12:01 ` [PATCH 2/2] xfsprogs: update man for metadump about dirty log/obfuscation issue Brian Foster
2017-04-13 12:29 ` Jan Tulak
2017-04-13 13:04 ` Brian Foster
2017-04-13 13:49 ` Eric Sandeen
2017-04-13 15:50 ` Darrick J. Wong
2017-04-13 17:01 ` Eric Sandeen
2017-04-13 17:06 ` Darrick J. Wong
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=20170413081354.22170-3-jtulak@redhat.com \
--to=jtulak@redhat.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 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).