mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sujiaxun <sujiaxun@uniontech.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: boot warning after merge of the akpm-current tree
Date: Wed, 16 Feb 2022 19:32:02 +1100	[thread overview]
Message-ID: <20220216193202.28838626@canb.auug.org.au> (raw)

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

Hi all,

After merging the akpm-current tree, today's linux-next boot tests
(qemu powerpc pseries_le_defconfig) produced these warnings:

  sysctl table check failed: vm/øIe^B Not a file
  sysctl table check failed: vm/(efault) No proc_handler
  CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.0-rc4 #3
  Call Trace:
  [c0000000073e39d0] [c0000000007b8370] dump_stack_lvl+0x74/0xa8 (unreliable)
  [c0000000073e3a10] [c000000000577ecc] __register_sysctl_table+0x60c/0x9f0
  [c0000000073e3b20] [c000000002043ea4] __register_sysctl_init+0x40/0x78
  [c0000000073e3b90] [c00000000203583c] oom_init+0x6c/0x84
  [c0000000073e3bf0] [c000000000012130] do_one_initcall+0x60/0x2d0
  [c0000000073e3cd0] [c0000000020049f0] kernel_init_freeable+0x334/0x3dc
  [c0000000073e3db0] [c000000000012730] kernel_init+0x30/0x1a0
  [c0000000073e3e10] [c00000000000cd64] ret_from_kernel_thread+0x5c/0x64
  failed when register_sysctl vm_oom_kill_table to vm

Caused by commit

  5c4a1da27403 ("mm: move oom_kill sysctls to their own file")

I have applied the following fix patch for today.

From b6c6a58898ebf468ae042b3481dccd73db32c2a9 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 16 Feb 2022 19:20:20 +1100
Subject: [PATCH] fix up for "mm: move oom_kill sysctls to their own file"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 mm/oom_kill.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 07ff90c920bc..9787e2cc51b5 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -80,7 +80,8 @@ static struct ctl_table vm_oom_kill_table[] = {
 		.maxlen		= sizeof(sysctl_oom_dump_tasks),
 		.mode		= 0644,
 		.proc_handler	= proc_dointvec,
-	}
+	},
+	{}
 };
 #endif
 
-- 
2.34.1

-- 
Cheers,
Stephen Rothwell

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

                 reply	other threads:[~2022-02-16  8:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220216193202.28838626@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sujiaxun@uniontech.com \
    /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

all inboxes | Powered by JetHome®