On 7/27/17 5:52 AM, Eryu Guan wrote: > On Wed, Jul 26, 2017 at 03:33:20PM -0500, Eric Sandeen wrote: >> xfs_metadump by default sanitizes the image so that all strings >> longer than 5 chars are obfusccated, and all stale data in metadata >> blocks (i.e. unused/unwritten data) is zeroed out. We didn't have >> a test for this, though, so this does it. >> >> It patterns 256M of the scratch device, then uses djwong's >> populate infrastructure to write all types of metadata, >> metadumps & mdrestores it, then looks for either the leaked >> pre-pattern or any leaked strings or filenames. >> >> The strings we look for are, unfortunately, a bit ad-hoc based on >> what is currently used in the populate routines. > > I don't have a better idea to avoid this either.. > > Some minor issues below. comment typo: will fix whitespace: sigh, will fix ;) groups: a patch to new script to check for this might be nice ;) will fix. out file: Argh, always forget to add that to git will resend, thanks. -Eric -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
