[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202005061540.88ECA85@keescook>
Date: Wed, 6 May 2020 15:40:22 -0700
From: Kees Cook <keescook@...omium.org>
To: Joe Perches <joe@...ches.com>
Cc: Pavel Tatashin <pasha.tatashin@...een.com>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
Jonathan Corbet <corbet@....net>,
Rob Herring <robh+dt@...nel.org>,
Benson Leung <bleung@...omium.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>, jmorris@...ei.org,
sashal@...nel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 2/6] pstore/platform: Pass max_reason to kmesg dump
On Wed, May 06, 2020 at 02:25:41PM -0700, Joe Perches wrote:
> On Wed, 2020-05-06 at 14:15 -0700, Kees Cook wrote:
> > From: Pavel Tatashin <pasha.tatashin@...een.com>
> >
> > Add a new member to struct pstore_info for passing information about
> > kmesg dump maximum reason. This allows a finer control of what kmesg
> > dumps are sent to pstore storage backends.
>
> trivia:
>
> > diff --git a/include/linux/pstore.h b/include/linux/pstore.h
> []
> > @@ -96,6 +96,12 @@ struct pstore_record {
> > *
> > * @read_mutex: serializes @open, @read, @close, and @erase callbacks
> > * @flags: bitfield of frontends the backend can accept writes for
> > + * @max_reason: Used when PSTORE_FLAGS_DMESG is set. Contains the
> > + * kmsg_dump_reason enum value. KMSG_DUMP_UNDEF means
> > + * "use existing kmsg_dump() filtering, based on the
> > + * printk.always_kmsg_dump boot param" (which is either
> > + * KMSG_DUMP_OOPS when false, or KMSG_DUMP_MAX when
> > + * tree); see printk.always_kmsg_dump for more details.
>
> s/tree/true/
Eek, thanks. I'll fix my typo. :)
--
Kees Cook
Powered by blists - more mailing lists