From: Domenico Andreoli <domenico.andreoli@linux.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Tong Zhang <ztong0001@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: boottime warning from todays linux-next
Date: Thu, 10 Feb 2022 19:06:15 +0100 [thread overview]
Message-ID: <YgVUF5cyWWjPDdvv@m4> (raw)
In-Reply-To: <20220210193302.686fa61a@canb.auug.org.au>
On Thu, Feb 10, 2022 at 07:33:02PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 10 Feb 2022 18:43:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > My qemu boot of a powerpc pseries_le_defconfig kernel produced these
> > kernel messages:
> >
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.0-rc3 #2
> > Call Trace:
> > [c0000000073e3a80] [c0000000007bfd40] dump_stack_lvl+0x74/0xa8 (unreliable)
> > [c0000000073e3ac0] [c00000000057e3dc] __register_sysctl_table+0x60c/0x9f0
> > [c0000000073e3bd0] [c000000002041170] init_fs_stat_sysctls+0x48/0x60
> > [c0000000073e3bf0] [c000000000012110] do_one_initcall+0x60/0x2d0
> > [c0000000073e3cd0] [c0000000020049f0] kernel_init_freeable+0x334/0x3dc
> > [c0000000073e3db0] [c000000000012710] kernel_init+0x30/0x1a0
> > [c0000000073e3e10] [c00000000000cd64] ret_from_kernel_thread+0x5c/0x64
> >
> > Presumably introduced by commit
> >
> > b42bc9a3c511 ("Fix regression due to "fs: move binfmt_misc sysctl to its own file"")
>
> OK, I cannot reproduce this with just Linus' tree. I will try to bisect.
I could not reproduce it on either my amd64 or arm64.
Dom
--
rsa4096: 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA 356E CC79 2832 ED38 CB05
next prev parent reply other threads:[~2022-02-10 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:43 linux-next: boottime warning from todays linux-next Stephen Rothwell
2022-02-10 8:33 ` Stephen Rothwell
2022-02-10 10:41 ` Stephen Rothwell
2022-02-10 11:29 ` Stephen Rothwell
2022-02-10 23:19 ` Luis Chamberlain
2022-02-11 1:33 ` Stephen Rothwell
2022-02-11 1:38 ` Luis Chamberlain
2022-02-11 7:46 ` Stephen Rothwell
2022-02-11 18:51 ` Luis Chamberlain
2022-02-11 19:12 ` Tong Zhang
2022-02-10 18:06 ` Domenico Andreoli [this message]
2022-02-10 23:35 ` Tong Zhang
2022-02-11 1:43 ` Stephen Rothwell
2022-02-11 17:36 ` Tong Zhang
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=YgVUF5cyWWjPDdvv@m4 \
--to=domenico.andreoli@linux.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=ztong0001@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.