From: "Ewan D. Milne" <emilne@redhat.com>
To: Martin Kepplinger <martin.kepplinger@puri.sm>,
jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: dgilbert@interlog.com, bvanassche@acm.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi_logging: print cdb into new line after opcode
Date: Fri, 22 Jan 2021 14:52:56 -0500 [thread overview]
Message-ID: <c0c7b4cde76c9b15aad9fa213dcaeb75295763fd.camel@redhat.com> (raw)
In-Reply-To: <20210122083918.901-1-martin.kepplinger@puri.sm>
On Fri, 2021-01-22 at 09:39 +0100, Martin Kepplinger wrote:
> The current log message results in a line like the following where
> the first byte is duplicated, giving a wrong impression:
>
> sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 60 40 00 00 01
> 00
>
> Print the cdb into a new line in any case, not only when cmd_len is
> greater than 16. The above example error will then read:
>
> sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28
> 28 00 01 c0 09 00 00 00 08 00
>
> Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
> ---
> drivers/scsi/scsi_logging.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/scsi_logging.c
> b/drivers/scsi/scsi_logging.c
> index 8ea44c6595ef..0081d3936f83 100644
> --- a/drivers/scsi/scsi_logging.c
> +++ b/drivers/scsi/scsi_logging.c
> @@ -200,10 +200,11 @@ void scsi_print_command(struct scsi_cmnd *cmd)
> if (off >= logbuf_len)
> goto out_printk;
>
> + /* Print opcode in one line and use separate lines for CDB */
> + off += scnprintf(logbuf + off, logbuf_len - off, "\n");
> +
> /* print out all bytes in cdb */
> if (cmd->cmd_len > 16) {
> - /* Print opcode in one line and use separate lines for
> CDB */
> - off += scnprintf(logbuf + off, logbuf_len - off, "\n");
> dev_printk(KERN_INFO, &cmd->device->sdev_gendev, "%s",
> logbuf);
> for (k = 0; k < cmd->cmd_len; k += 16) {
> size_t linelen = min(cmd->cmd_len - k, 16);
> @@ -224,7 +225,6 @@ void scsi_print_command(struct scsi_cmnd *cmd)
> goto out;
> }
> if (!WARN_ON(off > logbuf_len - 49)) {
> - off += scnprintf(logbuf + off, logbuf_len - off, " ");
> hex_dump_to_buffer(cmd->cmnd, cmd->cmd_len, 16, 1,
> logbuf + off, logbuf_len - off,
> false);
I'd rather we not change this.
-Ewan
next prev parent reply other threads:[~2021-01-22 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:39 Martin Kepplinger
2021-01-22 19:52 ` Ewan D. Milne [this message]
2021-01-23 3:09 ` Martin K. Petersen
2021-01-25 7:29 ` Martin Kepplinger
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=c0c7b4cde76c9b15aad9fa213dcaeb75295763fd.camel@redhat.com \
--to=emilne@redhat.com \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.kepplinger@puri.sm \
--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®