From: Sam Protsenko <semen.protsenko@linaro.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] clkdev: fix potential NULL pointer dereference
Date: Wed, 8 May 2024 15:52:08 -0500 [thread overview]
Message-ID: <CAPLW+4=0_ErruqVsSUkKfzw0+m3i8J=jn8A_SEnwLKWZX1Oyuw@mail.gmail.com> (raw)
In-Reply-To: <20240507064434.3213933-1-m.szyprowski@samsung.com>
On Tue, May 7, 2024 at 1:45 AM Marek Szyprowski
<m.szyprowski@samsung.com> wrote:
>
> dev_fmt argument is optional, so avoid dereferencing it unconditionally.
>
> Fixes: 4d11c62ca8d7 ("clkdev: report over-sized strings when creating clkdev entries")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
>
Thanks for fixing this, Marek! I tested it on the E850-96 board, and
it fixes the boot on current kernel-next for me (next-20240508). Feel
free to add:
Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
Tested-by: Sam Protsenko <semen.protsenko@linaro.org>
[snip]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-08 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240507064445eucas1p1bfc17da4f824ef46567774634482f12f@eucas1p1.samsung.com>
2024-05-07 6:44 ` [PATCH] clkdev: fix potential NULL pointer dereference Marek Szyprowski
2024-05-07 9:34 ` Russell King (Oracle)
2024-05-07 16:42 ` André Draszik
2024-05-07 17:58 ` Russell King (Oracle)
2024-05-08 20:52 ` Sam Protsenko [this message]
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='CAPLW+4=0_ErruqVsSUkKfzw0+m3i8J=jn8A_SEnwLKWZX1Oyuw@mail.gmail.com' \
--to=semen.protsenko@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).