Re: [PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump

2020-05-06 Thread Pavel Tatashin
On Tue, May 5, 2020 at 5:59 PM Kees Cook wrote: > > On Tue, May 05, 2020 at 11:45:07AM -0400, Pavel Tatashin wrote: > > Add a new field to pstore_info that passes information about kmesg dump > > maximum reason. > > > > This allows a finer control of what kmesg dumps are stored on pstore > > devic

Re: [PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump

2020-05-06 Thread Pavel Tatashin
On Wed, May 6, 2020 at 9:52 AM Steven Rostedt wrote: > > On Tue, 5 May 2020 14:59:37 -0700 > Kees Cook wrote: > > > > @@ -97,6 +97,8 @@ struct pstore_record { > > > * @read_mutex:serializes @open, @read, @close, and @erase callbacks > > > * @flags: bitfield of frontends the backend can ac

Re: [PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump

2020-05-06 Thread Steven Rostedt
On Tue, 5 May 2020 14:59:37 -0700 Kees Cook wrote: > > @@ -97,6 +97,8 @@ struct pstore_record { > > * @read_mutex:serializes @open, @read, @close, and @erase callbacks > > * @flags: bitfield of frontends the backend can accept writes for > > * @data: backend-private pointer passed back

Re: [PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump

2020-05-05 Thread Kees Cook
On Tue, May 05, 2020 at 11:45:07AM -0400, Pavel Tatashin wrote: > Add a new field to pstore_info that passes information about kmesg dump > maximum reason. > > This allows a finer control of what kmesg dumps are stored on pstore > device. > > Those clients that do not explicitly set this field (k

[PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump

2020-05-05 Thread Pavel Tatashin
Add a new field to pstore_info that passes information about kmesg dump maximum reason. This allows a finer control of what kmesg dumps are stored on pstore device. Those clients that do not explicitly set this field (keep it equal to 0), get the default behavior: dump only Oops and Panics, and d