public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Joel Granados <j.granados@samsung.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: bott test warning
Date: Tue, 23 May 2023 13:57:39 +1000	[thread overview]
Message-ID: <20230523135739.73068c68@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-05-23  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230523035747eucas1p2f10754f5eb6759d6665a35562c523841@eucas1p2.samsung.com>
2023-05-23  3:57 ` Stephen Rothwell [this message]
2023-05-23 11:06   ` linux-next: bott test warning Joel Granados
2023-05-23 11:08   ` Joel Granados
2023-05-23 11:20   ` Joel Granados
2023-05-24  6:07     ` Stephen Rothwell
2023-05-24 11:03       ` Joel Granados

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230523135739.73068c68@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=j.granados@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox