From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, John Garry <john.g.garry@oracle.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>
Subject: Re: [PATCH v2 2/2] scsi: core: Eliminate scsi_log_{reserve,release}_buffer()
Date: Thu, 10 Sep 2026 06:28:44 -0700 [thread overview]
Message-ID: <26af649e-20bd-4caf-8409-1db757b585c8@acm.org> (raw)
In-Reply-To: <97644265-c807-412f-92a8-7866f5ae9b50@suse.de>
On 9/10/26 3:45 AM, Hannes Reinecke wrote:
> But in removing scsi_log we're back to square one, namely that we
> cannot assemble a single line of logging with several calls
> (eg as required when dumping a hex buffer or a SCSI command).
This patch uses %*ph to dump hex buffers. No temporary buffers are
required to dump a hex buffer. The temporary buffers introduced by
this patch are as follows:
+ char opcode_name[64];
+ char sense_hdr[64];
+ char extd_sense[96];
+ char mlret_buf[32];
+ char hb_buf[40];
Personally I prefer the introduction of these temporary buffers rather
than making every sdev_prefix_printk() call perform a fixed-size
GFP_ATOMIC allocation. This patch eliminates the risk of log line
suppression because of GFP_ATOMIC memory allocation failure and also
eliminates the 128 byte line limit length.
Thanks,
Bart.
next prev parent reply other threads:[~2026-09-10 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 17:58 [PATCH v2 0/2] scsi: core: Optimize the SCSI printk() variants Bart Van Assche
2026-08-31 17:58 ` [PATCH v2 1/2] scsi: core: Add KUnit tests for scsi_logging.c Bart Van Assche
2026-08-31 20:05 ` sashiko-bot
2026-08-31 17:58 ` [PATCH v2 2/2] scsi: core: Eliminate scsi_log_{reserve,release}_buffer() Bart Van Assche
2026-09-07 14:44 ` Hannes Reinecke
2026-09-09 16:37 ` Bart Van Assche
2026-09-10 10:45 ` Hannes Reinecke
2026-09-10 13:28 ` Bart Van Assche [this message]
2026-09-10 3:50 ` Bart Van Assche
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=26af649e-20bd-4caf-8409-1db757b585c8@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mkp@kernel.org \
/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