From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Ard Biesheuvel <ardb@kernel.org>, Kees Cook <keescook@chromium.org>
Cc: Tony Luck <tony.luck@intel.com>, Nick Terrell <terrelln@fb.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/5] pstore: Use zstd directly by default for compression
Date: Tue, 18 Oct 2022 11:10:53 -0300 [thread overview]
Message-ID: <8d40dad4-4b20-2ec3-a8e1-706dd415f0d2@igalia.com> (raw)
In-Reply-To: <CAMj1kXGjF63wK7m8BqC=WX6sA425BTVwQWk9ERN3gG8s==4mjw@mail.gmail.com>
On 18/10/2022 05:20, Ard Biesheuvel wrote:
> [...]
> So again, I suggest to simply drop this non-feature, and standardize
> on either zlib or zstd using the library interface exclusively. If
> someone present a compelling use case, we can always consider adding
> it back in some form.
>
> As for the choice of algorithm, given the equal performance using the
> default compression level, and the difference in code size, I don't
> see why zstd should be preferred here. If anything, it only increases
> the likelihood of hitting another error if we are panicking due to
> some memory corruption issue.
I think it's a good argument - would zlib be simpler in code than zstd?
I've checked the zstd patch from Kees - not complex per se, but would be
great if we could have a simple mechanism, without the need of the ifdef
there for example...
Cheers,
Guilherme
next prev parent reply other threads:[~2022-10-18 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 2:08 Kees Cook
2022-10-18 2:08 ` [PATCH 1/5] pstore: Remove worse-case compression size logic Kees Cook
2022-10-18 2:08 ` [PATCH 2/5] pstore: Allow for arbitrary compression algorithm Kees Cook
2022-10-18 2:08 ` [PATCH 3/5] pstore: Use size_t for compress/decompression type widths Kees Cook
2022-10-18 2:08 ` [PATCH 4/5] pstore: Refactor compression initialization Kees Cook
2022-10-18 2:08 ` [PATCH 5/5] pstore: Use zstd directly by default for compression Kees Cook
2022-10-18 8:20 ` [PATCH 0/5] " Ard Biesheuvel
2022-10-18 14:10 ` Guilherme G. Piccoli [this message]
2022-10-18 14:38 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d40dad4-4b20-2ec3-a8e1-706dd415f0d2@igalia.com \
--to=gpiccoli@igalia.com \
--cc=ardb@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®