All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: linux-crypto@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kernel/padata.c: share code between CPU_ONLINE and CPU_DOWN_FAILED, same to CPU_DOWN_PREPARE and CPU_UP_CANCELED
Date: Fri, 23 Aug 2013 11:46:59 +0800	[thread overview]
Message-ID: <5216DB33.80404@asianux.com> (raw)
In-Reply-To: <5215B319.3020908@asianux.com>

On 08/22/2013 02:43 PM, Chen Gang wrote:
> Share code between CPU_ONLINE and CPU_DOWN_FAILED, same to
> CPU_DOWN_PREPARE and CPU_UP_CANCELED.
> 
> It will fix 2 bugs:
> 
>   "not check the return value of __padata_remove_cpu() and __padata_add_cpu()".
>   "need add 'break' between CPU_UP_CANCELED and CPU_DOWN_FAILED".
> 

Do we need more details descriptions ?

If so, could Steffen give more expert details information ?

Thanks.

> 
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
>  kernel/padata.c |   20 ++++----------------
>  1 files changed, 4 insertions(+), 16 deletions(-)
> 
> diff --git a/kernel/padata.c b/kernel/padata.c
> index 072f4ee..2f0037a 100644
> --- a/kernel/padata.c
> +++ b/kernel/padata.c
> @@ -846,6 +846,8 @@ static int padata_cpu_callback(struct notifier_block *nfb,
>  	switch (action) {
>  	case CPU_ONLINE:
>  	case CPU_ONLINE_FROZEN:
> +	case CPU_DOWN_FAILED:
> +	case CPU_DOWN_FAILED_FROZEN:
>  		if (!pinst_has_cpu(pinst, cpu))
>  			break;
>  		mutex_lock(&pinst->lock);
> @@ -857,6 +859,8 @@ static int padata_cpu_callback(struct notifier_block *nfb,
>  
>  	case CPU_DOWN_PREPARE:
>  	case CPU_DOWN_PREPARE_FROZEN:
> +	case CPU_UP_CANCELED:
> +	case CPU_UP_CANCELED_FROZEN:
>  		if (!pinst_has_cpu(pinst, cpu))
>  			break;
>  		mutex_lock(&pinst->lock);
> @@ -865,22 +869,6 @@ static int padata_cpu_callback(struct notifier_block *nfb,
>  		if (err)
>  			return notifier_from_errno(err);
>  		break;
> -
> -	case CPU_UP_CANCELED:
> -	case CPU_UP_CANCELED_FROZEN:
> -		if (!pinst_has_cpu(pinst, cpu))
> -			break;
> -		mutex_lock(&pinst->lock);
> -		__padata_remove_cpu(pinst, cpu);
> -		mutex_unlock(&pinst->lock);
> -
> -	case CPU_DOWN_FAILED:
> -	case CPU_DOWN_FAILED_FROZEN:
> -		if (!pinst_has_cpu(pinst, cpu))
> -			break;
> -		mutex_lock(&pinst->lock);
> -		__padata_add_cpu(pinst, cpu);
> -		mutex_unlock(&pinst->lock);
>  	}
>  
>  	return NOTIFY_OK;
> 


-- 
Chen Gang

  reply	other threads:[~2013-08-23  3:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  3:43 [PATCH] kernel/padata.c: always check the return value of __padata_remove_cpu() and __padata_add_cpu() Chen Gang
2013-08-20  3:44 ` Chen Gang
2013-08-22  5:11   ` Steffen Klassert
2013-08-22  5:27     ` Chen Gang
2013-08-22  6:05       ` Steffen Klassert
2013-08-22  6:16         ` Chen Gang
2013-08-22  6:43         ` [PATCH v2] kernel/padata.c: share code between CPU_ONLINE and CPU_DOWN_FAILED, same to CPU_DOWN_PREPARE and CPU_UP_CANCELED Chen Gang
2013-08-23  3:46           ` Chen Gang [this message]
2013-08-23 10:44           ` Steffen Klassert
2013-08-23 10:44             ` Steffen Klassert
2013-08-23 10:47             ` Herbert Xu
2013-08-23 10:47               ` Herbert Xu
2013-08-26  1:11               ` Chen Gang
2013-08-26  1:11                 ` Chen Gang
2013-08-29  4:42             ` Herbert Xu
2013-08-29  4:42               ` Herbert Xu
2013-08-29  5:22               ` Chen Gang
2013-08-29  5:22                 ` Chen Gang

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=5216DB33.80404@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen.klassert@secunet.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.