linux-kernel - Re: [BUG] Splat in __register_sysctl

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 11 Feb 2022 10:02:49 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     "Paul E. McKenney" <paulmck@...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 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 !

  Luis