From: Kees Cook <keescook@chromium.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] pstore: migrate to crypto acomp interface (take 2)
Date: Thu, 6 Oct 2022 16:45:58 -0700 [thread overview]
Message-ID: <202210061645.1BA58DED4D@keescook> (raw)
In-Reply-To: <20221006234138.1835739-1-keescook@chromium.org>
On Thu, Oct 06, 2022 at 04:41:38PM -0700, Kees Cook wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> The crypto 'compress' interface is deprecated, so before adding new
> features, migrate to the acomp interface. Note that we are only using
> synchronous implementations of acomp, so we don't have to deal with
> asynchronous completion.
>
> [ Tweaked error paths to avoid memory leak, as pointed out byGuilherme
^^
gah, I'll fix this typo locally. :P
--
Kees Cook
next prev parent reply other threads:[~2022-10-06 23:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 23:41 [PATCH] pstore: migrate to crypto acomp interface (take 2) Kees Cook
2022-10-06 23:45 ` Kees Cook [this message]
2022-10-07 18:46 ` Guilherme G. Piccoli
2022-10-17 16:26 ` Guilherme G. Piccoli
2022-10-17 18:01 ` Kees Cook
2022-10-17 18:14 ` Ard Biesheuvel
2022-10-17 18:22 ` Guilherme G. Piccoli
2022-10-17 19:11 ` Ard Biesheuvel
2022-10-17 19:29 ` Kees Cook
2022-10-17 19:33 ` Ard Biesheuvel
2022-10-17 19:40 ` Kees Cook
2022-10-17 19:45 ` Ard Biesheuvel
2022-10-17 20:11 ` Kees Cook
2022-10-17 20:13 ` Ard Biesheuvel
2022-10-17 20:35 ` Kees Cook
2022-10-17 21:01 ` Ard Biesheuvel
2022-10-17 21:10 ` Guilherme G. Piccoli
2022-10-17 21:16 ` Ard Biesheuvel
2022-10-17 21:25 ` Guilherme G. Piccoli
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=202210061645.1BA58DED4D@keescook \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ardb@kernel.org \
--cc=ccross@android.com \
--cc=gpiccoli@igalia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.