From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-hyperv@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Douglas Anderson <dianders@chromium.org>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Thomas Meyer <thomas@m3y3r.de>,
Vignesh Raghavendra <vigneshr@ti.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Richard Weinberger <richard@nod.at>,
Anton Vorontsov <anton@enomsg.org>,
Jordan Niethe <jniethe5@gmail.com>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Wei Li <liwei391@huawei.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
Kees Cook <keescook@chromium.org>,
Alistair Popple <alistair@popple.id.au>,
Jeff Dike <jdike@addtoit.com>, Colin Cross <ccross@android.com>,
linux-um@lists.infradead.org, Wei Liu <wei.liu@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Nicholas Piggin <npiggin@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Michael Kelley <mikelley@microsoft.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
Sumit Garg <sumit.garg@linaro.org>,
Tony Luck <tony.luck@intel.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Jason Wessel <jason.wessel@windriver.com>,
kgdb-bugreport@lists.sourceforge.net,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Mike Rapoport <rppt@kernel.org>
Subject: [PATCH next v4 00/15] printk: remove logbuf_lock
Date: Wed, 3 Mar 2021 11:15:13 +0100 [thread overview]
Message-ID: <20210303101528.29901-1-john.ogness@linutronix.de> (raw)
Hello,
Here is v4 of a series to remove @logbuf_lock, exposing the
ringbuffer locklessly to both readers and writers. v3 is
here [0].
Since @logbuf_lock was protecting much more than just the
ringbuffer, this series clarifies and cleans up the various
protections using comments, lockless accessors, atomic types,
and a new finer-grained @syslog_lock.
Removing @logbuf_lock required changing the semantics of the
kmsg_dumper callback in order to work locklessly. This series
adjusts all kmsg_dumpers and users of the kmsg_dump_get_*()
functions for the new semantics.
This series is based on next-20210303.
Changes since v3:
- disable interrupts in the arch/um kmsg_dumper
- reduce CONSOLE_LOG_MAX value from 4096 back to 1024 to revert
the increasd 3KiB static memory footprint
- change the kmsg_dumper() callback prototype back to how it
was because some dumpers need the registered object for
container_of() usage
- for kmsg_dump_get_line()/kmsg_dump_get_buffer() restrict the
minimal allowed sequence number to the cleared sequence number
John Ogness
[0] https://lore.kernel.org/lkml/20210225202438.28985-1-john.ogness@linutronix.de/
John Ogness (15):
um: synchronize kmsg_dumper
mtd: mtdoops: synchronize kmsg_dumper
printk: limit second loop of syslog_print_all
printk: kmsg_dump: remove unused fields
printk: refactor kmsg_dump_get_buffer()
printk: consolidate kmsg_dump_get_buffer/syslog_print_all code
printk: introduce CONSOLE_LOG_MAX
printk: use seqcount_latch for clear_seq
printk: use atomic64_t for devkmsg_user.seq
printk: add syslog_lock
printk: kmsg_dumper: remove @active field
printk: introduce a kmsg_dump iterator
printk: remove logbuf_lock
printk: kmsg_dump: remove _nolock() variants
printk: console: remove unnecessary safe buffer usage
arch/powerpc/kernel/nvram_64.c | 8 +-
arch/powerpc/xmon/xmon.c | 6 +-
arch/um/kernel/kmsg_dump.c | 13 +-
drivers/hv/vmbus_drv.c | 4 +-
drivers/mtd/mtdoops.c | 17 +-
fs/pstore/platform.c | 5 +-
include/linux/kmsg_dump.h | 47 ++--
kernel/debug/kdb/kdb_main.c | 10 +-
kernel/printk/internal.h | 4 +-
kernel/printk/printk.c | 464 +++++++++++++++++----------------
kernel/printk/printk_safe.c | 27 +-
11 files changed, 310 insertions(+), 295 deletions(-)
--
2.20.1
next reply other threads:[~2021-03-03 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 10:15 John Ogness [this message]
2021-03-03 10:15 ` [PATCH next v4 11/15] printk: kmsg_dumper: remove @active field John Ogness
2021-03-03 10:15 ` [PATCH next v4 12/15] printk: introduce a kmsg_dump iterator John Ogness
2021-03-03 13:48 ` Petr Mladek
2021-03-03 10:15 ` [PATCH next v4 14/15] printk: kmsg_dump: remove _nolock() variants John Ogness
2021-03-03 13:18 ` lkml delivery: was: Re: [PATCH next v4 00/15] printk: remove logbuf_lock Petr Mladek
2021-03-03 14:34 ` Steven Rostedt
2021-03-03 15:34 ` Petr Mladek
2021-03-08 15:09 ` Petr Mladek
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=20210303101528.29901-1-john.ogness@linutronix.de \
--to=john.ogness@linutronix.de \
--cc=alistair@popple.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=christophe.leroy@c-s.fr \
--cc=daniel.thompson@linaro.org \
--cc=dave@stgolabs.net \
--cc=dianders@chromium.org \
--cc=haiyangz@microsoft.com \
--cc=jason.wessel@windriver.com \
--cc=jdike@addtoit.com \
--cc=jniethe5@gmail.com \
--cc=keescook@chromium.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liwei391@huawei.com \
--cc=maddy@linux.ibm.com \
--cc=mikelley@microsoft.com \
--cc=miquel.raynal@bootlin.com \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=paulus@samba.org \
--cc=pmladek@suse.com \
--cc=ravi.bangoria@linux.ibm.com \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sthemmin@microsoft.com \
--cc=sumit.garg@linaro.org \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=tony.luck@intel.com \
--cc=vigneshr@ti.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).