From: "Li, Zhijian" <lizhijian@fujitsu.com>
To: <fthain@linux-m68k.org>
Cc: <jejb@linux.ibm.com>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <lizhijian@fujitsu.com>,
<martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: Enlarge log buffer length to 256
Date: Tue, 28 Jun 2022 17:38:06 +0800 [thread overview]
Message-ID: <6cbb4340-abc2-d902-7ae6-0ae169a97132@fujitsu.com> (raw)
In-Reply-To: <9831381e-f9c7-f7af-e6da-a757a76f34@linux-m68k.org>
Sorry for the late reply. (Strange! this reply didn't arrive to my mailbox)
> On Fri, 24 Jun 2022, Li Zhijian wrote:
>
> > scsi_report_sense() is possble to print messages exceeding 128 bytes: > [ 475.156955] sd 9:0:0:0: Warning! Received an indication that the
> LUN assignments on this target have changed. The Linux SCSI layer does
> not automatical > > Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> > --- > drivers/scsi/scsi_logging.c | 2 +- > 1 file changed, 1
> insertion(+), 1 deletion(-) > > diff --git
> a/drivers/scsi/scsi_logging.c b/drivers/scsi/scsi_logging.c > index
> b02af340c2d3..edc3fe8c7e0f 100644 > --- a/drivers/scsi/scsi_logging.c
> > +++ b/drivers/scsi/scsi_logging.c > @@ -17,7 +17,7 @@ > > static
> char *scsi_log_reserve_buffer(size_t *len) > { > - *len = 128; > +
> *len = 256; > return kmalloc(*len, GFP_ATOMIC); > } >
> Perhaps it's better to waste fewer words (both kinds). E.g.
Yes, it's an option. if no objection, i will apply your suggestion in
24h later. hahaha :)
Thanks
Zhijian
>
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index 49ef864df581..e7283bf23db3 100644 ---
> a/drivers/scsi/scsi_error.c +++ b/drivers/scsi/scsi_error.c @@ -463,13
> +463,11 @@ static void scsi_report_sense(struct scsi_device *sdev, evt_type = SDEV_EVT_LUN_CHANGE_REPORTED;
> scsi_report_lun_change(sdev);
> sdev_printk(KERN_WARNING, sdev,
> - "Warning! Received an indication that the " "LUN assignments on this target have "
> "changed. The Linux SCSI layer does not "
> "automatically remap LUN assignments.\n");
> } else if (sshdr->asc == 0x3f)
> sdev_printk(KERN_WARNING, sdev,
> - "Warning! Received an indication that the " "operating parameters on this target have "
> "changed. The Linux SCSI layer does not "
> "automatically adjust these parameters.\n");
prev parent reply other threads:[~2022-06-28 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 1:25 Li Zhijian
2022-06-24 1:39 ` Finn Thain
2022-06-28 9:38 ` Li, Zhijian [this message]
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=6cbb4340-abc2-d902-7ae6-0ae169a97132@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=fthain@linux-m68k.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®