From: Qian Cai <cai@lca.pw>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <will@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Steven Rostedt \(VMware\)" <rostedt@goodmis.org>,
Alexei Starovoitov <ast@kernel.org>,
clang-built-linux@googlegroups.com,
Catalin Marinas <catalin.marinas@arm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Ingo Molnar <mingo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: "ftrace: Rework event_create_dir()" triggers boot error messages
Date: Wed, 18 Dec 2019 22:58:23 -0500 [thread overview]
Message-ID: <0FA8C6E3-D9F5-416D-A1B0-5E4CD583A101@lca.pw> (raw)
The linux-next commit "ftrace: Rework event_create_dir()” [1] triggers boot warnings
for Clang-build (Clang version 8.0.1) kernels (reproduced on both arm64 and powerpc).
Reverted it (with trivial conflict fixes) on the top of today’s linux-next fixed the issue.
configs:
https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
https://raw.githubusercontent.com/cailca/linux-mm/master/powerpc.config
[1] https://lore.kernel.org/lkml/20191111132458.342979914@infradead.org/
[ 115.799327][ T1] Registered efivars operations
[ 115.849770][ T1] clocksource: Switched to clocksource arch_sys_counter
[ 115.901145][ T1] Could not initialize trace point events/sys_enter_rt_sigreturn
[ 115.908854][ T1] Could not create directory for event sys_enter_rt_sigreturn
[ 115.998949][ T1] Could not initialize trace point events/sys_enter_restart_syscall
[ 116.006802][ T1] Could not create directory for event sys_enter_restart_syscall
[ 116.062702][ T1] Could not initialize trace point events/sys_enter_getpid
[ 116.069828][ T1] Could not create directory for event sys_enter_getpid
[ 116.078058][ T1] Could not initialize trace point events/sys_enter_gettid
[ 116.085181][ T1] Could not create directory for event sys_enter_gettid
[ 116.093405][ T1] Could not initialize trace point events/sys_enter_getppid
[ 116.100612][ T1] Could not create directory for event sys_enter_getppid
[ 116.108989][ T1] Could not initialize trace point events/sys_enter_getuid
[ 116.116058][ T1] Could not create directory for event sys_enter_getuid
[ 116.124250][ T1] Could not initialize trace point events/sys_enter_geteuid
[ 116.131457][ T1] Could not create directory for event sys_enter_geteuid
[ 116.139840][ T1] Could not initialize trace point events/sys_enter_getgid
[ 116.146908][ T1] Could not create directory for event sys_enter_getgid
[ 116.155163][ T1] Could not initialize trace point events/sys_enter_getegid
[ 116.162370][ T1] Could not create directory for event sys_enter_getegid
[ 116.178015][ T1] Could not initialize trace point events/sys_enter_setsid
[ 116.185138][ T1] Could not create directory for event sys_enter_setsid
[ 116.269307][ T1] Could not initialize trace point events/sys_enter_sched_yield
[ 116.276811][ T1] Could not create directory for event sys_enter_sched_yield
[ 116.527652][ T1] Could not initialize trace point events/sys_enter_munlockall
[ 116.535126][ T1] Could not create directory for event sys_enter_munlockall
[ 116.622096][ T1] Could not initialize trace point events/sys_enter_vhangup
[ 116.629307][ T1] Could not create directory for event sys_enter_vhangup
[ 116.783867][ T1] Could not initialize trace point events/sys_enter_sync
[ 116.790819][ T1] Could not create directory for event sys_enter_sync
[ 117.723402][ T1] pnp: PnP ACPI init
[ 117.736379][ T1] system 00:00: [mem 0x30000000-0x3fffffff window] could not be reserved
[ 126.020353][ T1] pnp: PnP ACPI: found 1 devices
[ 126.093919][ T1] NET: Registered protocol family 2
[ 126.180007][ T1] tcp_listen_portaddr_hash hash table entries: 65536 (order: 6, 4718592 bytes, vmalloc)
[ 126.206510][ T1] TCP established hash table entries: 524288 (order: 6, 4194304 bytes, vmalloc)
[ 126.227766][ T1] TCP bind hash table entries: 65536 (order: 6, 4194304 bytes, vmalloc)
[ 126.240146][ T1] TCP: Hash tables configured (established 524288 bind 65536)
next reply other threads:[~2019-12-19 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 3:58 Qian Cai [this message]
2019-12-19 4:31 ` "ftrace: Rework event_create_dir()" triggers boot error messages Steven Rostedt
2019-12-19 6:06 ` Qian Cai
2020-01-06 17:05 ` Qian Cai
2020-01-06 17:54 ` Steven Rostedt
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=0FA8C6E3-D9F5-416D-A1B0-5E4CD583A101@lca.pw \
--to=cai@lca.pw \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=will@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