From: Eugen Hristev <eugen.hristev@linaro.org>
To: kees@kernel.org
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Eugen Hristev <eugen.hristev@linaro.org>
Subject: [PATCH] pstore/zone: fix return value for psz_init_zones
Date: Tue, 21 Jan 2025 17:06:17 +0200 [thread overview]
Message-ID: <20250121150617.608118-1-eugen.hristev@linaro.org> (raw)
psz_init_zones is not supposed to return NULL. It returns an errno,
and its caller always checks for an errno to look for a problem.
If the caller receives a NULL as a return, this code will go further
without any errors:
cxt->kpszs = psz_init_zones(PSTORE_TYPE_DMESG, &off,
info->total_size - off_size,
info->kmsg_size, &cxt->kmsg_max_cnt);
if (IS_ERR(cxt->kpszs)) {
err = PTR_ERR(cxt->kpszs);
cxt->kpszs = NULL;
goto free_out;
}
Later, when dereferencing kpszs, a panic would occur.
Thus, to avoid this possible crash, it's better to avoid returning NULL
in psz_init_zones, and just return -EINVAL if the parameters received
are wrong (in this case, a zero size request).
Fixes: d26c3321fe18 ("pstore/zone: Introduce common layer to manage storage zones")
Signed-off-by: Eugen Hristev <eugen.hristev@linaro.org>
---
fs/pstore/zone.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/pstore/zone.c b/fs/pstore/zone.c
index 5fa2fa2e7aa7..dbafc72a2f68 100644
--- a/fs/pstore/zone.c
+++ b/fs/pstore/zone.c
@@ -1204,7 +1204,7 @@ static struct pstore_zone **psz_init_zones(enum pstore_type_id type,
*cnt = 0;
if (!total_size || !record_size)
- return NULL;
+ return ERR_PTR(-EINVAL);
if (*off + total_size > info->total_size) {
pr_err("no room for zones %s (0x%zx@0x%llx over 0x%lx)\n",
--
2.43.0
next reply other threads:[~2025-01-21 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 15:06 Eugen Hristev [this message]
2025-01-22 12:00 ` [PATCH] pstore/zone: fix return value for psz_init_zones Eugen Hristev
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=20250121150617.608118-1-eugen.hristev@linaro.org \
--to=eugen.hristev@linaro.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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