public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <james.smart@emulex.com>
To: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] lpfc: fix the max value of lpfc_log_verbose
Date: Mon, 1 Feb 2010 08:35:25 -0500	[thread overview]
Message-ID: <4B66D89D.8060505@emulex.com> (raw)
In-Reply-To: <4B666AC4.10109@jp.fujitsu.com>

Nack...   I'd rather move it to an unsigned int.  In any case, Emulex will 
take care of this issue in its next patch series.

-- james s


Kei Tokunaga wrote:
> Hi,
> 
> The max value of lpfc_log_verbose is intended to be 0xffffffff, but since
> it was treated as int, 0xffffffff was not actually accepted.  Correcting
> it to the actual max value (0x7fffffff)  (Bits up to 18th are defined and
> bits up to 15th are actually used today.)
> 
> This is the message when tried to store 0xffffffff to lpfc_log_verbose.
> 
>   kernel: lpfc 0000:02:03.0: 0:(0):0424 lpfc_log_verbose attribute cannot be set to -1, allowed range is [0x0, 0xffffffff]
> 
> Changing its type from 'int' to 'unsigned int' might be another option.
> 
> Signed-off-by: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
> 
> 
> ---
> 
>  linux-2.6.33-rc5-v-kei/drivers/scsi/lpfc/lpfc_attr.c   |    2 +-
>  linux-2.6.33-rc5-v-kei/drivers/scsi/lpfc/lpfc_logmsg.h |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff -puN drivers/scsi/lpfc/lpfc_attr.c~fix_max_of_log_verbose drivers/scsi/lpfc/lpfc_attr.c
> --- linux-2.6.33-rc5-v/drivers/scsi/lpfc/lpfc_attr.c~fix_max_of_log_verbose	2010-01-25 20:23:43.000000000 +0900
> +++ linux-2.6.33-rc5-v-kei/drivers/scsi/lpfc/lpfc_attr.c	2010-01-25 20:24:06.000000000 +0900
> @@ -2086,7 +2086,7 @@ static DEVICE_ATTR(lpfc_devloss_tmo, S_I
>  # You can set a bit mask to record specific types of verbose messages:
>  # See lpfc_logmsh.h for definitions.
>  */
> -LPFC_VPORT_ATTR_HEX_RW(log_verbose, 0x0, 0x0, 0xffffffff,
> +LPFC_VPORT_ATTR_HEX_RW(log_verbose, 0x0, 0x0, 0x7fffffff,
>  		       "Verbose logging bit-mask");
>  
>  /*
> diff -puN drivers/scsi/lpfc/lpfc_logmsg.h~fix_max_of_log_verbose drivers/scsi/lpfc/lpfc_logmsg.h
> --- linux-2.6.33-rc5-v/drivers/scsi/lpfc/lpfc_logmsg.h~fix_max_of_log_verbose	2010-01-25 20:24:24.000000000 +0900
> +++ linux-2.6.33-rc5-v-kei/drivers/scsi/lpfc/lpfc_logmsg.h	2010-01-25 20:24:55.000000000 +0900
> @@ -35,7 +35,7 @@
>  #define LOG_VPORT	0x00004000	/* NPIV events */
>  #define LOF_SECURITY	0x00008000	/* Security events */
>  #define LOG_EVENT	0x00010000	/* CT,TEMP,DUMP, logging */
> -#define LOG_ALL_MSG	0xffffffff	/* LOG all messages */
> +#define LOG_ALL_MSG	0x7fffffff	/* LOG all messages */
>  
>  #define lpfc_printf_vlog(vport, level, mask, fmt, arg...) \
>  do { \
> 
> _
> 
> 
> 
> 

  reply	other threads:[~2010-02-01 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  5:46 [PATCH] lpfc: fix the max value of lpfc_log_verbose Kei Tokunaga
2010-02-01 13:35 ` James Smart [this message]
2010-02-03  4:09   ` Kei Tokunaga

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=4B66D89D.8060505@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tokunaga.keiich@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox