From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kernel-team@fb.com, mingo@kernel.org, tglx@linutronix.de,
elver@google.com, andreyknvl@google.com, glider@google.com,
dvyukov@google.com, cai@lca.pw, boqun.feng@gmail.com,
gregkh@linuxfoundation.org, nathan@kernel.org, ojeda@kernel.org,
arnd@arndb.de
Subject: [GIT PULL] kcsan: Fix debugfs initcall return type
Date: Thu, 20 May 2021 13:01:27 -0700 [thread overview]
Message-ID: <20210520200127.GA2227122@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
This pull request provides a fix for a regression introduced in the v5.13
merge window by commit e36299efe7d7 ("kcsan, debugfs: Move debugfs file
creation out of early init"). The regression is not easy to trigger,
requiring a KCSAN build using clang with CONFIG_LTO_CLANG=y. The fix
simply makes the kcsan_debugfs_init() function's type initcall-compatible.
This fix has been posted to the relevant mailing lists:
https://lore.kernel.org/lkml/20210514140015.2944744-1-arnd@kernel.org/
It has also been exposed to -next testing and has been subject to more
than the usual number of reviews.
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git urgent.2021.05.20a
for you to fetch changes up to 976aac5f882989e4f6c1b3a7224819bf0e801c6a:
kcsan: Fix debugfs initcall return type (2021-05-18 10:58:02 -0700)
----------------------------------------------------------------
Arnd Bergmann (1):
kcsan: Fix debugfs initcall return type
kernel/kcsan/debugfs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2021-05-20 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 20:01 Paul E. McKenney [this message]
2021-05-21 0:48 ` pr-tracker-bot
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=20210520200127.GA2227122@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®