Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: James Bottomley <james.bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
	Robert Elliott <Elliott@hp.com>,
	"Ewan D. Milne" <emilne@redhat.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: [PATCH] Avoid that long log lines are truncated
Date: Mon, 14 Mar 2016 07:19:55 -0700	[thread overview]
Message-ID: <56E6C88B.6010201@sandisk.com> (raw)

While testing the latest version of the SRP initiator and target
drivers I encountered the following message in the kernel log:

sd 16:0:0:0: Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatical

This is a truncated message. Avoid that such truncation happens
by increasing the SCSI_LOG_BUFSIZE constant.

Fixes: ded85c193a39 (scsi: Implement per-cpu logging buffer)
Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Robert Elliott <elliott@hp.com>
Cc: Ewan D. Milne <emilne@redhat.com>
Cc: <stable@vger.kernel.org> # v4.0+
---
 include/scsi/scsi_dbg.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/scsi/scsi_dbg.h b/include/scsi/scsi_dbg.h
index 56710e0..05d36eb 100644
--- a/include/scsi/scsi_dbg.h
+++ b/include/scsi/scsi_dbg.h
@@ -5,7 +5,7 @@ struct scsi_cmnd;
 struct scsi_device;
 struct scsi_sense_hdr;
 
-#define SCSI_LOG_BUFSIZE 128
+#define SCSI_LOG_BUFSIZE 256
 
 extern void scsi_print_command(struct scsi_cmnd *);
 extern size_t __scsi_format_command(char *, size_t,
-- 
2.7.2


             reply	other threads:[~2016-03-14 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:19 Bart Van Assche [this message]
2016-03-14 14:32 ` [PATCH] Avoid that long log lines are truncated Johannes Thumshirn
2016-03-14 14:36 ` Hannes Reinecke
2016-03-14 14:38 ` Ewan Milne
2016-03-14 14:45   ` Hannes Reinecke

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=56E6C88B.6010201@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=Elliott@hp.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --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