From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>,
Joel Fernandes <joel@joelfernandes.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pstore: Refactor compression initialization
Date: Thu, 18 Oct 2018 10:14:19 -0700 [thread overview]
Message-ID: <10d9618bf794d6e07b537455344b30238d5f4e80.camel@perches.com> (raw)
In-Reply-To: <20181017214124.GA8239@beast>
On Wed, 2018-10-17 at 14:41 -0700, Kees Cook wrote:
> With compression initialization now separated from pstore_register(),
> there is no longer a good reason to do compression method selection
> during fs init. Instead, merge everything together into the late init.
> Additionally cleans up the reporting to be more clear.
[]
> diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c
[]
> @@ -274,36 +274,56 @@ static int pstore_decompress(void *in, void *out,
[]
> - big_oops_buf = kmalloc(big_oops_buf_sz, GFP_KERNEL);
> - if (!big_oops_buf) {
> - pr_err("allocate compression buffer error!\n");
> + buf = kmalloc(size, GFP_KERNEL);
> + if (!buf) {
> + pr_err("Failed %d byte compression buffer allocation for: %s\n",
> + size, zbackend->name);
Given that there is a generic OOM message emitted on
kmalloc failures, rather than expanding the unnecessary
alloc failure message, how about just deleting it instead?
next prev parent reply other threads:[~2018-10-18 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 21:41 [PATCH] pstore: Refactor compression initialization Kees Cook
2018-10-18 1:30 ` Joel Fernandes
2018-10-18 4:42 ` Sai Prakash Ranjan
2018-10-18 4:44 ` Kees Cook
2018-10-18 4:44 ` Kees Cook
2018-10-18 17:14 ` Joe Perches [this message]
2018-10-18 18:01 ` Kees Cook
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=10d9618bf794d6e07b537455344b30238d5f4e80.camel@perches.com \
--to=joe@perches.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
/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