Hi all,
Today's linux-next boot test (powerpc pseries_le_defconfig) produced
this warning:
sysctl table check failed: kernel/usermodehelper Not a file
sysctl table check failed: kernel/usermodehelper No proc_handler
sysctl table check failed: kernel/usermodehelper bogus .mode 0555
sysctl table check failed: kernel/keys Not a file
sysctl table check failed: kernel/keys No proc_handler
sysctl table check failed: kernel/keys bogus .mode 0555
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.4.0-rc3-04222-g1999c5d1802e #1
Hardware name: IBM pSeries (emulated by qemu) POWER8 (raw) 0x4d0200 0xf000004 of:SLOF,HEAD pSeries
Call Trace:
[c0000000028bfd40] [c00000000113ea2c] dump_stack_lvl+0x70/0xa0 (unreliable)
[c0000000028bfd70] [c0000000006166f0] __register_sysctl_table+0x7f0/0x9e0
[c0000000028bfe50] [c00000000204e650] __register_sysctl_init+0x40/0x78
[c0000000028bfec0] [c00000000202d660] sysctl_init_bases+0x40/0xb4
[c0000000028bfef0] [c00000000204e6dc] proc_sys_init+0x54/0x68
[c0000000028bff10] [c00000000204dff4] proc_root_init+0xb8/0xdc
[c0000000028bff30] [c0000000020045d8] start_kernel+0x7f8/0x834
[c0000000028bffe0] [c00000000000e998] start_here_common+0x1c/0x20
failed when register_sysctl kern_table to kernel
I am not sure exactly which commit caused this.
--
Cheers,
Stephen Rothwell
On Tue, May 23, 2023 at 01:57:39PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next boot test (powerpc pseries_le_defconfig) produced
> this warning:
>
> sysctl table check failed: kernel/usermodehelper Not a file
> sysctl table check failed: kernel/usermodehelper No proc_handler
> sysctl table check failed: kernel/usermodehelper bogus .mode 0555
This is because I missed to handle the child in usermodehelper
> sysctl table check failed: kernel/keys Not a file
> sysctl table check failed: kernel/keys No proc_handler
> sysctl table check failed: kernel/keys bogus .mode 0555
Also because of the child being there.
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.4.0-rc3-04222-g1999c5d1802e #1
> Hardware name: IBM pSeries (emulated by qemu) POWER8 (raw) 0x4d0200 0xf000004 of:SLOF,HEAD pSeries
> Call Trace:
> [c0000000028bfd40] [c00000000113ea2c] dump_stack_lvl+0x70/0xa0 (unreliable)
> [c0000000028bfd70] [c0000000006166f0] __register_sysctl_table+0x7f0/0x9e0
> [c0000000028bfe50] [c00000000204e650] __register_sysctl_init+0x40/0x78
> [c0000000028bfec0] [c00000000202d660] sysctl_init_bases+0x40/0xb4
> [c0000000028bfef0] [c00000000204e6dc] proc_sys_init+0x54/0x68
> [c0000000028bff10] [c00000000204dff4] proc_root_init+0xb8/0xdc
> [c0000000028bff30] [c0000000020045d8] start_kernel+0x7f8/0x834
> [c0000000028bffe0] [c00000000000e998] start_here_common+0x1c/0x20
> failed when register_sysctl kern_table to kernel
>
> I am not sure exactly which commit caused this.
>
> --
> Cheers,
> Stephen Rothwell
Let me respin go a next version of this patch.
Thx for the test
--
Joel Granados
On Tue, May 23, 2023 at 01:57:39PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next boot test (powerpc pseries_le_defconfig) produced
> this warning:
>
> sysctl table check failed: kernel/usermodehelper Not a file
> sysctl table check failed: kernel/usermodehelper No proc_handler
> sysctl table check failed: kernel/usermodehelper bogus .mode 0555
> sysctl table check failed: kernel/keys Not a file
> sysctl table check failed: kernel/keys No proc_handler
> sysctl table check failed: kernel/keys bogus .mode 0555
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.4.0-rc3-04222-g1999c5d1802e #1
> Hardware name: IBM pSeries (emulated by qemu) POWER8 (raw) 0x4d0200 0xf000004 of:SLOF,HEAD pSeries
> Call Trace:
> [c0000000028bfd40] [c00000000113ea2c] dump_stack_lvl+0x70/0xa0 (unreliable)
> [c0000000028bfd70] [c0000000006166f0] __register_sysctl_table+0x7f0/0x9e0
> [c0000000028bfe50] [c00000000204e650] __register_sysctl_init+0x40/0x78
> [c0000000028bfec0] [c00000000202d660] sysctl_init_bases+0x40/0xb4
> [c0000000028bfef0] [c00000000204e6dc] proc_sys_init+0x54/0x68
> [c0000000028bff10] [c00000000204dff4] proc_root_init+0xb8/0xdc
> [c0000000028bff30] [c0000000020045d8] start_kernel+0x7f8/0x834
> [c0000000028bffe0] [c00000000000e998] start_here_common+0x1c/0x20
> failed when register_sysctl kern_table to kernel
>
> I am not sure exactly which commit caused this.
Its probably this one 7eec88986dce2d85012fbe516def7a2d7d77735c
>
> --
> Cheers,
> Stephen Rothwell
--
Joel Granados
On Tue, May 23, 2023 at 01:57:39PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next boot test (powerpc pseries_le_defconfig) produced
> this warning:
>
> sysctl table check failed: kernel/usermodehelper Not a file
> sysctl table check failed: kernel/usermodehelper No proc_handler
> sysctl table check failed: kernel/usermodehelper bogus .mode 0555
> sysctl table check failed: kernel/keys Not a file
> sysctl table check failed: kernel/keys No proc_handler
> sysctl table check failed: kernel/keys bogus .mode 0555
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.4.0-rc3-04222-g1999c5d1802e #1
> Hardware name: IBM pSeries (emulated by qemu) POWER8 (raw) 0x4d0200 0xf000004 of:SLOF,HEAD pSeries
> Call Trace:
> [c0000000028bfd40] [c00000000113ea2c] dump_stack_lvl+0x70/0xa0 (unreliable)
> [c0000000028bfd70] [c0000000006166f0] __register_sysctl_table+0x7f0/0x9e0
> [c0000000028bfe50] [c00000000204e650] __register_sysctl_init+0x40/0x78
> [c0000000028bfec0] [c00000000202d660] sysctl_init_bases+0x40/0xb4
> [c0000000028bfef0] [c00000000204e6dc] proc_sys_init+0x54/0x68
> [c0000000028bff10] [c00000000204dff4] proc_root_init+0xb8/0xdc
> [c0000000028bff30] [c0000000020045d8] start_kernel+0x7f8/0x834
> [c0000000028bffe0] [c00000000000e998] start_here_common+0x1c/0x20
> failed when register_sysctl kern_table to kernel
>
> I am not sure exactly which commit caused this.
>
> --
> Cheers,
> Stephen Rothwell
Does the attached patch solve the issue?
--
Joel Granados
Hi Joel,
On Tue, 23 May 2023 13:20:01 +0200 Joel Granados <[email protected]> wrote:
>
> Does the attached patch solve the issue?
Yes, it does.
Tested-by: Stephen Rothwell <[email protected]> # ppc boot only
--
Cheers,
Stephen Rothwell
On Wed, May 24, 2023 at 04:07:24PM +1000, Stephen Rothwell wrote:
> Hi Joel,
>
> On Tue, 23 May 2023 13:20:01 +0200 Joel Granados <[email protected]> wrote:
> >
> > Does the attached patch solve the issue?
>
> Yes, it does.
Awesome!. This is already in mcgrof's tree so it is on its way upstream.
thx again.
Best
>
> Tested-by: Stephen Rothwell <[email protected]> # ppc boot only
> --
> Cheers,
> Stephen Rothwell
--
Joel Granados