linux-kernel - Re: [GIT PULL][PATCH v9 0/3] Update to zstd-1.4.10

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: <CANr2Dbc+2rS7seuXGtU6Y+x0Qv+hrtwz71r+akKeQUXECZaJZA@mail.gmail.com>
Date:   Wed, 14 Apr 2021 11:53:51 -0700
From:   Nick Terrell <nickrterrell@...il.com>
To:     Eric Biggers <ebiggers@...nel.org>
Cc:     Herbert Xu <herbert@...dor.apana.org.au>,
        squashfs-devel@...ts.sourceforge.net,
        Johannes Weiner <jweiner@...com>,
        Christoph Hellwig <hch@...radead.org>,
        Yann Collet <cyan@...com>, David Sterba <dsterba@...e.cz>,
        linux-kernel@...r.kernel.org,
        linux-f2fs-devel@...ts.sourceforge.net, Petr Malat <oss@...at.biz>,
        Chris Mason <clm@...com>, Nick Terrell <terrelln@...com>,
        linux-crypto@...r.kernel.org,
        Oleksandr Natalenko <oleksandr@...alenko.name>,
        Kernel Team <Kernel-team@...com>,
        Michał Mirosław <mirq-linux@...e.qmqm.pl>,
        Niket Agarwal <niketa@...com>, linux-btrfs@...r.kernel.org
Subject: Re: [GIT PULL][PATCH v9 0/3] Update to zstd-1.4.10

On Wed, Apr 14, 2021 at 11:35 AM Eric Biggers <ebiggers@...nel.org> wrote:
>
> On Wed, Apr 14, 2021 at 11:01:29AM -0700, Nick Terrell wrote:
> > Hi all,
> >
> > I would really like to make some progress on this and get it merged.
> > This patchset offsers:
> > * 15-30% better decompression speed
> > * 3 years of zstd bug fixes and code improvements
> > * Allows us to import zstd directly from upstream so we don't fall 3
> > years out of date again
> >
> > Thanks,
> > Nick
> >
>
> I think it would help get it merged if someone actually volunteered to maintain
> it.  As-is there is no entry in MAINTAINERS for this code.

I was discussing with Chris Mason about volunteering to maintain the
code myself.
We wanted to wait until this series got merged before going that
route, because there
was already a lot of comments about it, and I didn't want to appear to
be trying to bypass
any review or criticisms. But, please let me know what you think.

Best,
Nick

> - Eric