linux-ext4 - [PATCH RFC 0/6] add full off-line resize2fs support for flex

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]

Date:	Sat, 29 Dec 2012 03:55:22 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Cc:	George Spelvin <linux@...izon.com>, Theodore Ts'o <tytso@....edu>
Subject: [PATCH RFC 0/6] add full off-line resize2fs support for flex_bg file systems

This addresses the corruption problems reported by George Spelvin when
we created a file system with a non-default number of reserved gdt
blocks using the -E resize=NNN option.  It does this by adding full
support for flex_bg file systems, so that we don't have to worry about
allocating overlapping metadata tables while we are growing the number
of block group descriptor blocks, in the case where the resize inode
does not have enough reserved blocks, or is not present altogether.

Theodore Ts'o (6):
  mke2fs: fix crash when parsing "-E resize=NNN" with "-O 64bit"
  resize2fs: reserve fs metadata blocks first in blocks_to_move()
  resize2fs: reserve all metadata blocks for flex_bg file systems
  resize2fs: handle bg descriptors which overlap with other bg's
    metadata
  resize2fs: allow resizing flex_bg && !resize_inode file systems
  resize2fs: create optimized flex_bg block groups

 misc/mke2fs.c      |   8 +++++
 resize/main.c      |  22 ------------
 resize/resize2fs.c | 102 ++++++++++++++++++++++++++++++++++-------------------
 3 files changed, 73 insertions(+), 59 deletions(-)

-- 
1.7.12.rc0.22.gcdd159b

--
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