linux-ext4 - Re: [PATCH 1/3] mke2fs: enable large directroy support

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

Date:   Sun, 12 Feb 2017 20:50:48 +0300
From:   Artem Blagodarenko <artem.blagodarenko@...gate.com>
To:     Andreas Dilger <adilger@...ger.ca>
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 1/3] mke2fs: enable large directroy support

Hello,

>We have kernel-side patches for this feature. Artem, could you push a version of the ext4 patches for the latest kernel to the list?

Yes, sure. I will push it here soon.

Best regards,
Artem Blagodarenko.

On Thu, Feb 2, 2017 at 8:11 PM, Andreas Dilger <adilger@...ger.ca> wrote:
> We have kernel-side patches for this feature. Artem, could you push a version of the ext4 patches for the latest kernel to the list?
>
> Cheers, Andreas
>
>> On Jan 25, 2017, at 13:31, Theodore Ts'o <tytso@....edu> wrote:
>>
>>> On Tue, Jan 24, 2017 at 07:34:13PM +0300, Artem Blagodarenko wrote:
>>> The INCOMPAT_LARGEDIR feature allows larger directories to
>>> be created, both with directory sizes over 2GB and and a
>>> maximum htree depth of 3 instead of the current limit of 2.
>>> These features are needed in order to exceed the currently
>>> limit of approximately 10M entries in a single directory.
>>>
>>> debugfs, e2fsck, ext2fs, mke2fs and tune2fs support is
>>> added.
>>>
>>> Signed-off-by: Alexey Lyashkov <alexey.lyashkov@...gate.com>
>>> Signed-off-by: Artem Blagodarenko <artem.blagodarenko@...gate.com>
>>
>> Where are the kernel-side changes for this feature?
>>
>> And could you *please* use git send-email's --chain-reply-to option,
>> or set the sendemail.chainReplyTo in your git config.  (Or if you're
>> not using git send-email, send the e-mail using that format).
>>
>> It makes it much easier to figure out which patch goes with which
>> other patch in a patch series, especially when you start sending
>> revised versions of the patches.
>>
>>                    - Ted
>>



-- 
Artem Blagodarenko Ph.D.· SW Developer on my.seagate.com
Seagate Technology, LLC
www.seagate.com