Re: [PATCH RESEND] scsi: Output error messages using structured printk in single line

[Hannes Reinecke]

On 05/21/2014 05:18 AM, Elliott, Robert (Server Storage) wrote:
> > -----Original Message-----
> > From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-
> > owner@xxxxxxxxxxxxxxx] On Behalf Of James Bottomley
> > Sent: Tuesday, May 20, 2014 9:22 PM
> > To: Yoshihiro YUNOMAE
> > Cc: Hannes Reinecke; Prarit Bhargava; linux-scsi@xxxxxxxxxxxxxxx; Kay
> > Sievers; linux-kernel@xxxxxxxxxxxxxxx; Hidehiro Kawai; yrl.pp-
> > manager.tt@xxxxxxxxxxx; Masami Hiramatsu
> > Subject: Re: [PATCH RESEND] scsi: Output error messages using structured
> > printk in single line
> >
> > On Thu, 2014-02-27 at 13:17 +0900, Yoshihiro YUNOMAE wrote:
> > > +/* Maximum size of a local buffer for structured printk */
> > > +#define SCSI_LOG_LINE_MAX 512
> > > +
> > > +/* Local buffer for structured printk */
> > > +struct scsi_log_line {
> > > +	int offset;
> > > +	char buf[SCSI_LOG_LINE_MAX];
> > > +};
> >
> > This piece isn't going to fly; it's an on stack allocation of 0.5kb;
> > that's too much for small stack kernels.  Just changing this to a kalloc
> > is going be problematic too because we're in the io paths and the
> > allocation may fail.  So I appreciate the problem, but I don't think the
> > solution works.  Could we just tag the messages and use grep to put them
> > back together?
> >
> > James
>
> When the system gets busy, I've seen CDB bytes strung out with each
> byte getting its own timestamp, with messages from different devices
> and threads interleaved together, so like the idea of printing each
> line with a single printk() call.
>
> Most lines aren't anywhere near 512 bytes long.  Can this be coded to
> let the calling function define an appropriate buffer size for
> whatever it is printing, with sizeof() used to bounds check?
As mentioned several times, I'm working on a patchset to update
scsi logging.

The original patchset tried to convert any logging message into a 
single statement, which wouldn't be broken up even under heavy load.

While this works reasonably well for most things, printing out 
decoded sense with just one line (and not end up in massive switch()
statements) is near impossible.

Plus you'll end up having to use a static buffer at one point, which
again increases the stack size.

The alternative approach as discussed at LSF is to move scsi_logging
over to tracing. There is already some coding for scsi tracing, but
in most cases it just duplicates existing logging statements.
So if we were to replace the entire scsi_logging infrastructure
with scsi tracing most of the issues (like chopped-up CDBs) would
be gone.
Plus we would have a far better control about _what_ is being printed.

And yes, I do have some patches for that :-)

Cheers,

Hannes
--
Dr. Hannes Reinecke		      zSeries & Storage
hare@xxxxxxx			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/