Re: [PATCH] pstore/ram: Fix console ramoops to show the previous boot logs

2019-01-17 Thread Kees Cook
On Wed, Jan 16, 2019 at 10:27 PM Sai Prakash Ranjan wrote: > > commit b05c950698fe ("pstore/ram: Simplify ramoops_get_next_prz() > arguments") changed update assignment in getting next persistent > ram zone by adding a check for record type. But the check always > returns true since the record

Re: [PATCH] pstore/ram: Fix console ramoops to show the previous boot logs

2019-01-17 Thread Sai Prakash Ranjan
On 1/17/2019 8:48 PM, Joel Fernandes wrote: On Thu, Jan 17, 2019 at 11:56:20AM +0530, Sai Prakash Ranjan wrote: commit b05c950698fe ("pstore/ram: Simplify ramoops_get_next_prz() arguments") changed update assignment in getting next persistent ram zone by adding a check for record type. But the

Re: [PATCH] pstore/ram: Fix console ramoops to show the previous boot logs

2019-01-17 Thread Joel Fernandes
On Thu, Jan 17, 2019 at 11:56:20AM +0530, Sai Prakash Ranjan wrote: > commit b05c950698fe ("pstore/ram: Simplify ramoops_get_next_prz() > arguments") changed update assignment in getting next persistent > ram zone by adding a check for record type. But the check always > returns true since the

[PATCH] pstore/ram: Fix console ramoops to show the previous boot logs

2019-01-16 Thread Sai Prakash Ranjan
commit b05c950698fe ("pstore/ram: Simplify ramoops_get_next_prz() arguments") changed update assignment in getting next persistent ram zone by adding a check for record type. But the check always returns true since the record type is assigned 0. And this breaks console ramoops by showing current