linux-ext4 - [PATCH 0/6] Patches to improve/fix e2freefrag

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1249875118-26291-1-git-send-email-tytso@mit.edu>
Date:	Sun,  9 Aug 2009 23:31:52 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Cc:	Andreas Dilger <adilger@....com>, Theodore Ts'o <tytso@....edu>
Subject: [PATCH 0/6] Patches to improve/fix e2freefrag 

As we had discussed earlier, here are the patches to make the output of
e2freefrag either to understand.  While I was working with the program,
I found a number of bugs that caused it to behave incorrectly on file
systems with 1k block size, and to give incorrect information in some
circumstances.  These patches fix all of this bugs I was able to find.

Theodore Ts'o (6):
  e2freefrag: Clarify e2freefrag's messages
  e2freefrag: Do not print chunk-related information by default
  e2freefrag: Fix to work correctly for file systems with 1kb block
    sizes
  e2freefrag: Take into account the last free extent in the file system
  Add V=1 support when linking e2freefrag in misc/Makefile.in
  libext2fs: Treat uninitialized parts of bitmaps as unallocated

 lib/ext2fs/rw_bitmaps.c |    4 +-
 misc/Makefile.in        |    4 +-
 misc/e2freefrag.8.in    |   23 +++++------
 misc/e2freefrag.c       |   99 +++++++++++++++++++++++++++++-----------------
 tests/m_uninit/expect.1 |   48 +++++++++++-----------
 5 files changed, 100 insertions(+), 78 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html