All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: shuox.liu@intel.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org
Cc: tony.luck@intel.com, keescook@chromium.org, ccross@android.com,
	anton@enomsg.org
Subject: Re: [PATCH] pstore: skip zero size persistent ram buffer in traverse
Date: Sun, 02 Mar 2014 17:06:03 +0800	[thread overview]
Message-ID: <5312F47B.8080603@linux.intel.com> (raw)
In-Reply-To: <1393569501-14952-1-git-send-email-shuox.liu@intel.com>

On 2014/2/28 14:38, shuox.liu@intel.com wrote:
> From: Liu ShuoX <shuox.liu@intel.com>
>
> In ramoops_pstore_read, a valid prz pointer with zero size buffer will
> break traverse of all persistent ram buffers. The latter buffer might
> be lost.

Andrew,

Would you like to merge it to your testing tree?
pstore is a very important feature for debugging hard issues on
Android mobiles.

Yanmin

>
> Signed-off-by: Liu ShuoX <shuox.liu@intel.com>
> ---
>   fs/pstore/ram.c | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
> index a5d0cab..929ea55 100644
> --- a/fs/pstore/ram.c
> +++ b/fs/pstore/ram.c
> @@ -119,12 +119,12 @@ ramoops_get_next_prz(struct persistent_ram_zone *przs[], uint *c, uint max,
>   
>   	prz = przs[i];
>   
> -	if (update) {
> -		/* Update old/shadowed buffer. */
> +	/* Update old/shadowed buffer. */
> +	if (update)
>   		persistent_ram_save_old(prz);
> -		if (!persistent_ram_old_size(prz))
> -			return NULL;
> -	}
> +
> +	if (!persistent_ram_old_size(prz))
> +		return NULL;
>   
>   	*typep = type;
>   	*id = i;


  reply	other threads:[~2014-03-02  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28  6:38 [PATCH] pstore: skip zero size persistent ram buffer in traverse shuox.liu
2014-03-02  9:06 ` Zhang, Yanmin [this message]
2014-03-03 19:46 ` Kees Cook

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=5312F47B.8080603@linux.intel.com \
    --to=yanmin_zhang@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuox.liu@intel.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: link
Be 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.