>From: Joel Fernandes
>Sent: Wednesday, October 31, 2018 6:16
>To: Kees Cook
>Cc: Peng15 Wang 王鹏; Anton Vorontsov; Colin Cross; Tony Luck; LKML;
>vipwangerx...@gmail.com
>Subject: Re: [PATCH v4] pstore: Avoid duplicate call of persistent_ram_zap()
>
>On Tue, Oct 30,
>From: Kees Cook
>Sent: Friday, October 26, 2018 17:44
>To: Peng15 Wang 王鹏
>Cc: an...@enomsg.org; ccr...@android.com; tony.l...@intel.com;
>linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] pstore: Remove duplicate invoking of
From: Peng Wang
When initialing przs with invalid data in buffer(no PERSISTENT_RAM_SIG),
function call path is like this:
ramoops_init_prz ->
|
|-> persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
|
|--> persistent_ram_zap
As we can see, persistent_ram_zap() is called
From: Peng Wang
When initialing przs with invalid data in buffer(no PERSISTENT_RAM_SIG),
function call path is like this:
ramoops_init_prz ->
|
|-> persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
|
|--> persistent_ram_zap
As we can see, persistent_ram_zap() is called
>From: Kees Cook
>Sent: Friday, October 26, 2018 17:44
>To: Peng15 Wang 王鹏
>Cc: an...@enomsg.org; ccr...@android.com; tony.l...@intel.com;
>linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] pstore: Remove duplicate invoking of
>From: Joel Fernandes
>Sent: Wednesday, October 31, 2018 6:16
>To: Kees Cook
>Cc: Peng15 Wang 王鹏; Anton Vorontsov; Colin Cross; Tony Luck; LKML;
>vipwangerx...@gmail.com
>Subject: Re: [PATCH v4] pstore: Avoid duplicate call of persistent_ram_zap()
>
>On Tue, Oct 30,
6 matches
Mail list logo
