linux-ext4 - Re: [PATCH] ext4: initialize multi-block allocator before checking block descriptors

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]

Date:	Sun, 16 Mar 2014 03:54:34 +0400
From:	Azat Khuzhin <a3at.mail@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	"open list:EXT4 FILE SYSTEM" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: initialize multi-block allocator before checking
 block descriptors

On Sun, Mar 16, 2014 at 1:40 AM,  <tytso@....edu> wrote:
>>With EXT4FS_DEBUG ext4_count_free_clusters() will call
>>ext4_read_block_bitmap() without s_group_info initialized, so we need to
>>initialize multi-block allocator before.
>>
>>And we can't initialize multi-block allocator without group descriptors,
>>since it use them.
>>Also we need to install s_op before initializing multi-block allocator,
>>because in ext4_mb_init_backend() new inode is created.
>
> I've had to drop this patch because it's causing a series of bigalloc
> failures.  I'll take a closer look at this later, but I wantd to give
> you a heads up.

Thanks Ted, I'll take a look.
Are you talking about xfs-tests failures?

>
>                                         - Ted
>
>
>



-- 
Respectfully
Azat Khuzhin
--
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