From: Pavel Tatashin <pasha.tatashin@soleen.com> To: Kees Cook <keescook@chromium.org> Cc: Petr Mladek <pmladek@suse.com>, Anton Vorontsov <anton@enomsg.org>, Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>, Jonathan Corbet <corbet@lwn.net>, Benson Leung <bleung@chromium.org>, Rob Herring <robh+dt@kernel.org>, Michael Ellerman <mpe@ellerman.id.au>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Enric Balletbo i Serra <enric.balletbo@collabora.com>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Steven Rostedt <rostedt@goodmis.org>, Linux Doc Mailing List <linux-doc@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v4 0/6] allow ramoops to collect all kmesg_dump events Date: Fri, 15 May 2020 15:13:24 -0400 [thread overview] Message-ID: <CA+CK2bAo163NzFn=t+MXBYcTEHPqkptFw6K0d_yMbhwROdGy2A@mail.gmail.com> (raw) In-Reply-To: <20200515184434.8470-1-keescook@chromium.org> On Fri, May 15, 2020 at 2:44 PM Kees Cook <keescook@chromium.org> wrote: > > Hello! > > I wanted to get the pstore tree nailed down, so here's the v4 of > Pavel's series, tweaked for the feedback during v3 review. Hi Kees, Thank you, I was planning to send a new version of this series later today. Let me quickly review it. Pasha > > -Kees > > v4: > - rebase on pstore tree > - collapse shutdown types into a single dump reason > https://lore.kernel.org/lkml/CA+CK2bAPv5u1ih5y9t5FUnTyximtFCtDYXJCpuyjOyHNOkRdqw@mail.gmail.com/ > - fix dump_oops vs max_reason module params > https://lore.kernel.org/lkml/20200512233504.GA118720@sequoia/ > - typos > https://lore.kernel.org/lkml/4cdeaa2af2fe0d6cc2ca8ce3a37608340799df8a.camel@perches.com/ > - rename DT parsing routines ..._size -> ..._u32 > https://lore.kernel.org/lkml/CA+CK2bCu8eFomiU+NeBjVn-o2dbuECxwRfssNjB3ys3caCbXeA@mail.gmail.com/ > v3: https://lore.kernel.org/lkml/20200506211523.15077-1-keescook@chromium.org/ > v2: https://lore.kernel.org/lkml/20200505154510.93506-1-pasha.tatashin@soleen.com > v1: https://lore.kernel.org/lkml/20200502143555.543636-1-pasha.tatashin@soleen.com > > Kees Cook (3): > printk: Collapse shutdown types into a single dump reason > printk: Introduce kmsg_dump_reason_str() > pstore/ram: Introduce max_reason and convert dump_oops > > Pavel Tatashin (3): > printk: honor the max_reason field in kmsg_dumper > pstore/platform: Pass max_reason to kmesg dump > ramoops: Add max_reason optional field to ramoops DT node > > Documentation/admin-guide/ramoops.rst | 14 +++-- > .../bindings/reserved-memory/ramoops.txt | 13 ++++- > arch/powerpc/kernel/nvram_64.c | 4 +- > drivers/platform/chrome/chromeos_pstore.c | 2 +- > fs/pstore/platform.c | 26 ++------- > fs/pstore/ram.c | 58 +++++++++++++------ > include/linux/kmsg_dump.h | 12 +++- > include/linux/pstore.h | 7 +++ > include/linux/pstore_ram.h | 2 +- > kernel/printk/printk.c | 32 ++++++++-- > kernel/reboot.c | 6 +- > 11 files changed, 114 insertions(+), 62 deletions(-) > > -- > 2.20.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Tatashin <pasha.tatashin@soleen.com> To: Kees Cook <keescook@chromium.org> Cc: Petr Mladek <pmladek@suse.com>, Tony Luck <tony.luck@intel.com>, Jonathan Corbet <corbet@lwn.net>, Anton Vorontsov <anton@enomsg.org>, Linux Doc Mailing List <linux-doc@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, Steven Rostedt <rostedt@goodmis.org>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, Paul Mackerras <paulus@samba.org>, Colin Cross <ccross@android.com>, Enric Balletbo i Serra <enric.balletbo@collabora.com>, linuxppc-dev@lists.ozlabs.org, Benson Leung <bleung@chromium.org> Subject: Re: [PATCH v4 0/6] allow ramoops to collect all kmesg_dump events Date: Fri, 15 May 2020 15:13:24 -0400 [thread overview] Message-ID: <CA+CK2bAo163NzFn=t+MXBYcTEHPqkptFw6K0d_yMbhwROdGy2A@mail.gmail.com> (raw) In-Reply-To: <20200515184434.8470-1-keescook@chromium.org> On Fri, May 15, 2020 at 2:44 PM Kees Cook <keescook@chromium.org> wrote: > > Hello! > > I wanted to get the pstore tree nailed down, so here's the v4 of > Pavel's series, tweaked for the feedback during v3 review. Hi Kees, Thank you, I was planning to send a new version of this series later today. Let me quickly review it. Pasha > > -Kees > > v4: > - rebase on pstore tree > - collapse shutdown types into a single dump reason > https://lore.kernel.org/lkml/CA+CK2bAPv5u1ih5y9t5FUnTyximtFCtDYXJCpuyjOyHNOkRdqw@mail.gmail.com/ > - fix dump_oops vs max_reason module params > https://lore.kernel.org/lkml/20200512233504.GA118720@sequoia/ > - typos > https://lore.kernel.org/lkml/4cdeaa2af2fe0d6cc2ca8ce3a37608340799df8a.camel@perches.com/ > - rename DT parsing routines ..._size -> ..._u32 > https://lore.kernel.org/lkml/CA+CK2bCu8eFomiU+NeBjVn-o2dbuECxwRfssNjB3ys3caCbXeA@mail.gmail.com/ > v3: https://lore.kernel.org/lkml/20200506211523.15077-1-keescook@chromium.org/ > v2: https://lore.kernel.org/lkml/20200505154510.93506-1-pasha.tatashin@soleen.com > v1: https://lore.kernel.org/lkml/20200502143555.543636-1-pasha.tatashin@soleen.com > > Kees Cook (3): > printk: Collapse shutdown types into a single dump reason > printk: Introduce kmsg_dump_reason_str() > pstore/ram: Introduce max_reason and convert dump_oops > > Pavel Tatashin (3): > printk: honor the max_reason field in kmsg_dumper > pstore/platform: Pass max_reason to kmesg dump > ramoops: Add max_reason optional field to ramoops DT node > > Documentation/admin-guide/ramoops.rst | 14 +++-- > .../bindings/reserved-memory/ramoops.txt | 13 ++++- > arch/powerpc/kernel/nvram_64.c | 4 +- > drivers/platform/chrome/chromeos_pstore.c | 2 +- > fs/pstore/platform.c | 26 ++------- > fs/pstore/ram.c | 58 +++++++++++++------ > include/linux/kmsg_dump.h | 12 +++- > include/linux/pstore.h | 7 +++ > include/linux/pstore_ram.h | 2 +- > kernel/printk/printk.c | 32 ++++++++-- > kernel/reboot.c | 6 +- > 11 files changed, 114 insertions(+), 62 deletions(-) > > -- > 2.20.1 >
next prev parent reply other threads:[~2020-05-15 19:14 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-15 18:44 [PATCH v4 0/6] allow ramoops to collect all kmesg_dump events Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-15 18:44 ` [PATCH v4 1/6] printk: Collapse shutdown types into a single dump reason Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-15 19:17 ` Pavel Tatashin 2020-05-15 19:17 ` Pavel Tatashin 2020-05-22 16:21 ` Petr Mladek 2020-05-22 16:21 ` Petr Mladek 2020-05-23 11:16 ` Michael Ellerman 2020-05-23 11:16 ` Michael Ellerman 2020-05-15 18:44 ` [PATCH v4 2/6] printk: honor the max_reason field in kmsg_dumper Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-22 16:51 ` Petr Mladek 2020-05-22 16:51 ` Petr Mladek 2020-05-22 17:34 ` Kees Cook 2020-05-22 17:34 ` Kees Cook 2020-05-15 18:44 ` [PATCH v4 3/6] printk: Introduce kmsg_dump_reason_str() Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-15 19:23 ` Pavel Tatashin 2020-05-15 19:23 ` Pavel Tatashin 2020-05-15 18:44 ` [PATCH v4 4/6] pstore/platform: Pass max_reason to kmesg dump Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-15 18:44 ` [PATCH v4 5/6] pstore/ram: Introduce max_reason and convert dump_oops Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-15 19:30 ` Pavel Tatashin 2020-05-15 19:30 ` Pavel Tatashin 2020-05-15 19:48 ` Kees Cook 2020-05-15 19:48 ` Kees Cook 2020-05-15 19:40 ` Pavel Tatashin 2020-05-15 19:40 ` Pavel Tatashin 2020-05-15 19:53 ` Kees Cook 2020-05-15 19:53 ` Kees Cook 2020-05-15 18:44 ` [PATCH v4 6/6] ramoops: Add max_reason optional field to ramoops DT node Kees Cook 2020-05-15 18:44 ` Kees Cook 2020-05-18 22:45 ` Rob Herring 2020-05-18 22:45 ` Rob Herring 2020-05-18 23:04 ` Kees Cook 2020-05-18 23:04 ` Kees Cook 2020-05-15 19:13 ` Pavel Tatashin [this message] 2020-05-15 19:13 ` [PATCH v4 0/6] allow ramoops to collect all kmesg_dump events Pavel Tatashin
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='CA+CK2bAo163NzFn=t+MXBYcTEHPqkptFw6K0d_yMbhwROdGy2A@mail.gmail.com' \ --to=pasha.tatashin@soleen.com \ --cc=anton@enomsg.org \ --cc=benh@kernel.crashing.org \ --cc=bleung@chromium.org \ --cc=ccross@android.com \ --cc=corbet@lwn.net \ --cc=devicetree@vger.kernel.org \ --cc=enric.balletbo@collabora.com \ --cc=keescook@chromium.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=paulus@samba.org \ --cc=pmladek@suse.com \ --cc=robh+dt@kernel.org \ --cc=rostedt@goodmis.org \ --cc=sergey.senozhatsky@gmail.com \ --cc=tony.luck@intel.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: linkBe 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.