lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aPYEaNIom6BnFgP0@hovoldconsulting.com>
Date: Mon, 20 Oct 2025 11:44:08 +0200
From: Johan Hovold <johan@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Maxime Coquelin <mcoquelin.stm32@...il.com>,
	Alexandre Torgue <alexandre.torgue@...s.st.com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] clocksource/drivers/stm: Fix section mismatches

On Mon, Oct 20, 2025 at 11:39:59AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Oct 20, 2025 at 11:32:37AM +0200, Johan Hovold wrote:
> > On Fri, Oct 17, 2025 at 07:49:43AM +0200, Johan Hovold wrote:
> > > Platform drivers can be probed after their init sections have been
> > > discarded (e.g. on probe deferral or manual rebind through sysfs) so the
> > > probe function must not live in init. Device managed resource actions
> > > similarly cannot be discarded.
> > > 
> > > The "_probe" suffix of the driver structure name prevents modpost from
> > > warning about this so replace it to catch any similar future issues.
> > > 
> > > Fixes: cec32ac75827 ("clocksource/drivers/nxp-timer: Add the System Timer Module for the s32gx platforms")
> > > Cc: stable@...r.kernel.org	# 6.16
> > > Cc: Daniel Lezcano <daniel.lezcano@...aro.org>
> > > Signed-off-by: Johan Hovold <johan@...nel.org>
> > 
> > Addressing this apparently depends on commit 84b1a903aed8
> > ("time/sched_clock: Export symbol for sched_clock register function")
> > which was merged for 6.18-rc1. 
> > 
> > So the stable tag should be dropped (e.g. unless it's possible to
> > backport also the dependency to 6.17).
> 
> Quite easy to do so, just ask us!  :)

Heh. I meant that there may be something preventing the dependency from
being backported (even if I didn't see anything obvious based on a quick
look at the series adding it).

Johan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ