[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4s3egeo2fhq6hk7pcsxplsqomiiw6vbnnswhimlekfrl6tsixt@wzf5x63pdvp6>
Date: Sun, 29 Jun 2025 22:56:01 +0200
From: Joel Granados <joel.granados@...nel.org>
To: Jon Hunter <jonathanh@...dia.com>
Cc: Bert Karwatzki <spasswolf@....de>, linux-kernel@...r.kernel.org,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: register_syctl_init error in linux-next-20250612
On Fri, Jun 27, 2025 at 12:02:48PM +0100, Jon Hunter wrote:
> Hi Joel,
>
> On 20/06/2025 10:42, Joel Granados wrote:
...
> > + .data = &max_lock_depth,
> > + .maxlen = sizeof(int),
> > + .mode = 0644,
> > + .proc_handler = proc_dointvec,
> > + },
> > +};
> > +
> > +static int __init init_rtmutex_sysctl(void)
> > +{
> > + printk("registering rtmutex");
Well that just slipped in there undetected :).
> > + register_sysctl_init("kernel", rtmutex_sysctl_table);
> > + return 0;
> > +}
>
>
> With recent -next trees I am seeing the following kernel warning when
> booting -next on our Tegra boards ...
>
> boot: logs: [ 0.231226] WARNING KERN registering rtmutex
>
> This warning triggers a test failure for us because this is a new/unexpected
> warning. Looking at the above it seems that making this a pr_debug() or
> pr_info() would be more appropriate. Let me know if it is OK to update this.
this is just a debug print statement that made its way to next. I'll
remove it. Thx for the report.
Best
>
> Thanks!
> Jon
>
> --
> nvpublic
>
--
Joel Granados
Download attachment "signature.asc" of type "application/pgp-signature" (660 bytes)
Powered by blists - more mailing lists