linux-ext4 - [PATCH 0/5] meta_bg online resize patches

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: <1346561485-6413-1-git-send-email-tytso@mit.edu>
Date:	Sun,  2 Sep 2012 00:51:20 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Cc:	xiaoqiangnk@...il.com, Theodore Ts'o <tytso@....edu>
Subject: [PATCH 0/5] meta_bg online resize patches

This patch series is based on a set of patches from Yongqiang Yang, with
some bug fixes.  In particular, we have to grow certain arrays which are
allocated at mount time.  Originally, they were allocated to be big
enough to cover the largest possible size they could be given the number
of reserved gdt blocks.  This wasted memory and doesn't work in the
meta_bg scheme, since there is no limit imposed at mkfs time.

Theodore Ts'o (2):
  ext4: grow the s_flex_groups array as needed when resizing
  ext4: grow the s_group_info array as needed

Yongqiang Yang (3):
  ext4: when resizing, do not copy gdt blocks for groups that do not
    have them
  ext4: avoid duplicate writes of the backup bg descriptor blocks
  ext4: add online resizing support for meta_bg and bit64

 fs/ext4/ext4.h    |   6 ++
 fs/ext4/ioctl.c   |  15 ----
 fs/ext4/mballoc.c |  79 +++++++++--------
 fs/ext4/resize.c  | 249 ++++++++++++++++++++++++++++++++++++++++--------------
 fs/ext4/super.c   |  48 ++++++++---
 5 files changed, 267 insertions(+), 130 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