linux-ext4 - journal_dev + metadata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <BAY406-EAS34578C88C7F39934F1D8730FDC50@phx.gbl>
Date:	Thu, 4 Sep 2014 00:14:32 -0400
From:	TR Reardon <thomas_reardon@...mail.com>
To:	linux-ext4@...r.kernel.org, darrick.wong@...cle.com
Subject: journal_dev + metadata_csum issues

1) tune2fs hiccups when presented with journal device fs.  Should it instead at least report "this is a journal device" rather than "invalid super block"?

2) no way to create journal_dev with metadata_csum.  This would provide checksum for the fs superblock.

3) dumpe2fs should still display journal flags for journal_dev; currently it fails to display journal flags.

4) s_jnl_blocks in the superblock should be zeroed when removing a journal (ie ^has_journal) or when setting the journal to journal_dev.  Currently, the legacy (now dead) block list is maintained.  I'd argue that will invite misuse.