Re: clkdev: report over-sized strings when creating clkdev entries

From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	open list <linux-kernel@vger.kernel.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: clkdev: report over-sized strings when creating clkdev entries
Date: Wed, 8 May 2024 23:29:24 +0100	[thread overview]
Message-ID: <Zjv8xBXcRnfShpvf@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAPLW+4=D_31Fy_W_7+_ko22y9_-8rZ9Logh6KyW8UPM3q58J0A@mail.gmail.com>

On Wed, May 08, 2024 at 04:07:57PM -0500, Sam Protsenko wrote:
> The patch [1] ("clk: samsung: Don't register clkdev lookup for the
> fixed rate clocks") fixes those. I think both have to be applied ASAP.
> In case of E850-96, I guess [1] is more critical.

The fixes to clkdev.c have been pushed out for a while now, so I think
you may need to update your tree. There's been one more fix to it more
recently (because of the whole va_copy() debacle).

Whether linux-next picks up the latest version depends when they pull
in relation to me pushing the changes out, which can take 48 hours
due to the timezone differences. linux-next tends not to pick stuff
up quickly if one's in the UK and pushes stuff out in the late
afternoon/evening. That said, the NULL fix has been pushed out for
a few days now.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!