Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-12 Thread Kees Cook
On Wed, Mar 12, 2014 at 2:48 AM, Liu ShuoX wrote: > On Tue 11.Mar'14 at 13:37:23 -0700, Kees Cook wrote: >> >> On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX wrote: >>> >>> From: Liu ShuoX >>> >>> In case that ramoops_init_przs failed, max_dump_cnt won't be reset to >>> zero in error handle path.

Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-12 Thread Liu ShuoX
On Tue 11.Mar'14 at 13:37:23 -0700, Kees Cook wrote: On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX wrote: From: Liu ShuoX In case that ramoops_init_przs failed, max_dump_cnt won't be reset to zero in error handle path. Signed-off-by: Liu ShuoX --- fs/pstore/ram.c | 4 ++-- 1 file changed, 2

Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-12 Thread Kees Cook
On Wed, Mar 12, 2014 at 2:48 AM, Liu ShuoX shuox@intel.com wrote: On Tue 11.Mar'14 at 13:37:23 -0700, Kees Cook wrote: On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX shuox@intel.com wrote: From: Liu ShuoX shuox@intel.com In case that ramoops_init_przs failed, max_dump_cnt won't be

Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-12 Thread Liu ShuoX
On Tue 11.Mar'14 at 13:37:23 -0700, Kees Cook wrote: On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX shuox@intel.com wrote: From: Liu ShuoX shuox@intel.com In case that ramoops_init_przs failed, max_dump_cnt won't be reset to zero in error handle path. Signed-off-by: Liu ShuoX

Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-11 Thread Kees Cook
On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX wrote: > From: Liu ShuoX > > In case that ramoops_init_przs failed, max_dump_cnt won't be reset to > zero in error handle path. > > Signed-off-by: Liu ShuoX > --- > fs/pstore/ram.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff

[PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-11 Thread Liu ShuoX
From: Liu ShuoX In case that ramoops_init_przs failed, max_dump_cnt won't be reset to zero in error handle path. Signed-off-by: Liu ShuoX --- fs/pstore/ram.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c index 6f96d8c..522e530

[PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-11 Thread Liu ShuoX
From: Liu ShuoX shuox@intel.com In case that ramoops_init_przs failed, max_dump_cnt won't be reset to zero in error handle path. Signed-off-by: Liu ShuoX shuox@intel.com --- fs/pstore/ram.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/pstore/ram.c

Re: [PATCH 2/2] pstore: correct the max_dump_cnt clearing of ramoops

2014-03-11 Thread Kees Cook
On Mon, Mar 10, 2014 at 11:17 PM, Liu ShuoX shuox@intel.com wrote: From: Liu ShuoX shuox@intel.com In case that ramoops_init_przs failed, max_dump_cnt won't be reset to zero in error handle path. Signed-off-by: Liu ShuoX shuox@intel.com --- fs/pstore/ram.c | 4 ++-- 1 file