[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220211212211.GL4285@paulmck-ThinkPad-P17-Gen-1>
Date: Fri, 11 Feb 2022 13:22:11 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: keescook@...omium.org, yzaikin@...gle.com,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [BUG] Splat in __register_sysctl_table() in next-20220210
On Fri, Feb 11, 2022 at 10:02:49AM -0800, Luis Chamberlain wrote:
> On Fri, Feb 11, 2022 at 09:04:55AM -0800, Paul E. McKenney wrote:
> > Hello!
> >
> > I just wanted to be the 20th person to report the below splat in
> > init_fs_stat_sysctls() during boot. ;-)
> >
> > It happens on all rcutorture scenarios, for whatever that might be
> > worth.
>
> It should be fixed on today's linux-next, see this discussion:
>
> https://lore.kernel.org/linux-ext4/20220210091648.w5wie3llqri5kfw3@quack3.lan/T/#mfc3683a68aaec8595cd5f26e138453132a3e1d43
>
> Essentially there was a fix which Andrew merged. The Linus merged it.
> But linux-next carried Andrew's fix too, so there was a double
> registration.
>
> Please let me know if you still see the issue on next-20220211 !
And next-20220211 worked just fine, thank you!
Thanx, Paul
Powered by blists - more mailing lists