Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: emilne@redhat.com, Bart Van Assche <bart.vanassche@sandisk.com>
Cc: James Bottomley <james.bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>, Robert Elliott <Elliott@hp.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Avoid that long log lines are truncated
Date: Mon, 14 Mar 2016 15:45:32 +0100	[thread overview]
Message-ID: <56E6CE8C.5020600@suse.de> (raw)
In-Reply-To: <1457966320.4188.17.camel@localhost.localdomain>

On 03/14/2016 03:38 PM, Ewan Milne wrote:
> On Mon, 2016-03-14 at 07:19 -0700, Bart Van Assche wrote:
>> 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,
> 
> Hmm.  Perhaps we should make the message less verbose instead?
> It looks like if we increase SCSI_LOG_BUFSIZE then we get fewer
> per-message buffers unless we also increase SCSI_LOG_SPOOLSIZE.
> 
Or just shorten the message itself.
It's really annoying having these really long messages showing up in
the system log ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:19 [PATCH] Avoid that long log lines are truncated Bart Van Assche
2016-03-14 14:32 ` Johannes Thumshirn
2016-03-14 14:36 ` Hannes Reinecke
2016-03-14 14:38 ` Ewan Milne
2016-03-14 14:45   ` Hannes Reinecke [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=56E6CE8C.5020600@suse.de \
    --to=hare@suse.de \
    --cc=Elliott@hp.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=emilne@redhat.com \
    --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