All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] scsi: target: core: Make logs less verbose
@ 2021-09-29 11:50 Konstantin Shelekhin
  2021-10-04 20:36 ` Lee Duncan
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Konstantin Shelekhin @ 2021-09-29 11:50 UTC (permalink / raw)
  To: Martin Petersen, Mike Christie, target-devel
  Cc: linux-scsi, linux, Konstantin Shelekhin, Roman Bolshakov

Change the log level of the following message to debug:

	Unsupported SCSI Opcode 0xXX, sending CHECK_CONDITION.

This message is mostly helpful during debugging sessions in order to
understand errors on the initiator side. But most of the time it's just
useless and makes reading logs much harder.

It gets particularly annoying if there are many initiators that come and
go or if an initiator runs a program that does not care whether the
command is supported and just keeps sending it.

Signed-off-by: Konstantin Shelekhin <k.shelekhin@yadro.com>
Reviewed-by: Roman Bolshakov <r.bolshakov@yadro.com>
---
 drivers/target/target_core_transport.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
index 14c6f2bb1b01..4a0055ab9151 100644
--- a/drivers/target/target_core_transport.c
+++ b/drivers/target/target_core_transport.c
@@ -1511,10 +1511,10 @@ target_cmd_parse_cdb(struct se_cmd *cmd)
 
 	ret = dev->transport->parse_cdb(cmd);
 	if (ret == TCM_UNSUPPORTED_SCSI_OPCODE)
-		pr_warn_ratelimited("%s/%s: Unsupported SCSI Opcode 0x%02x, sending CHECK_CONDITION.\n",
-				    cmd->se_tfo->fabric_name,
-				    cmd->se_sess->se_node_acl->initiatorname,
-				    cmd->t_task_cdb[0]);
+		pr_debug_ratelimited("%s/%s: Unsupported SCSI Opcode 0x%02x, sending CHECK_CONDITION.\n",
+				     cmd->se_tfo->fabric_name,
+				     cmd->se_sess->se_node_acl->initiatorname,
+				     cmd->t_task_cdb[0]);
 	if (ret)
 		return ret;
 
-- 
2.33.0


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: target: core: Make logs less verbose
  2021-09-29 11:50 [PATCH] scsi: target: core: Make logs less verbose Konstantin Shelekhin
@ 2021-10-04 20:36 ` Lee Duncan
  2021-10-05  3:13 ` Martin K. Petersen
  2021-10-12 20:35 ` Martin K. Petersen
  2 siblings, 0 replies; 4+ messages in thread
From: Lee Duncan @ 2021-10-04 20:36 UTC (permalink / raw)
  To: Konstantin Shelekhin, Martin Petersen, Mike Christie, target-devel
  Cc: linux-scsi, linux, Roman Bolshakov

On 9/29/21 4:50 AM, Konstantin Shelekhin wrote:
> Change the log level of the following message to debug:
> 
> 	Unsupported SCSI Opcode 0xXX, sending CHECK_CONDITION.
> 
> This message is mostly helpful during debugging sessions in order to
> understand errors on the initiator side. But most of the time it's just
> useless and makes reading logs much harder.
> 
> It gets particularly annoying if there are many initiators that come and
> go or if an initiator runs a program that does not care whether the
> command is supported and just keeps sending it.
> 
> Signed-off-by: Konstantin Shelekhin <k.shelekhin@yadro.com>
> Reviewed-by: Roman Bolshakov <r.bolshakov@yadro.com>
> ---
>  drivers/target/target_core_transport.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
> index 14c6f2bb1b01..4a0055ab9151 100644
> --- a/drivers/target/target_core_transport.c
> +++ b/drivers/target/target_core_transport.c
> @@ -1511,10 +1511,10 @@ target_cmd_parse_cdb(struct se_cmd *cmd)
>  
>  	ret = dev->transport->parse_cdb(cmd);
>  	if (ret == TCM_UNSUPPORTED_SCSI_OPCODE)
> -		pr_warn_ratelimited("%s/%s: Unsupported SCSI Opcode 0x%02x, sending CHECK_CONDITION.\n",
> -				    cmd->se_tfo->fabric_name,
> -				    cmd->se_sess->se_node_acl->initiatorname,
> -				    cmd->t_task_cdb[0]);
> +		pr_debug_ratelimited("%s/%s: Unsupported SCSI Opcode 0x%02x, sending CHECK_CONDITION.\n",
> +				     cmd->se_tfo->fabric_name,
> +				     cmd->se_sess->se_node_acl->initiatorname,
> +				     cmd->t_task_cdb[0]);
>  	if (ret)
>  		return ret;
>  
> 

Reviewed-by: Lee Duncan <lduncan@suse.com>


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: target: core: Make logs less verbose
  2021-09-29 11:50 [PATCH] scsi: target: core: Make logs less verbose Konstantin Shelekhin
  2021-10-04 20:36 ` Lee Duncan
@ 2021-10-05  3:13 ` Martin K. Petersen
  2021-10-12 20:35 ` Martin K. Petersen
  2 siblings, 0 replies; 4+ messages in thread
From: Martin K. Petersen @ 2021-10-05  3:13 UTC (permalink / raw)
  To: Konstantin Shelekhin
  Cc: Martin Petersen, Mike Christie, target-devel, linux-scsi, linux,
	Roman Bolshakov


Konstantin,

> Change the log level of the following message to debug:
>
> 	Unsupported SCSI Opcode 0xXX, sending CHECK_CONDITION.

Applied to 5.16/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] scsi: target: core: Make logs less verbose
  2021-09-29 11:50 [PATCH] scsi: target: core: Make logs less verbose Konstantin Shelekhin
  2021-10-04 20:36 ` Lee Duncan
  2021-10-05  3:13 ` Martin K. Petersen
@ 2021-10-12 20:35 ` Martin K. Petersen
  2 siblings, 0 replies; 4+ messages in thread
From: Martin K. Petersen @ 2021-10-12 20:35 UTC (permalink / raw)
  To: Konstantin Shelekhin, target-devel, Mike Christie
  Cc: Martin K . Petersen, Roman Bolshakov, linux-scsi, linux

On Wed, 29 Sep 2021 14:50:00 +0300, Konstantin Shelekhin wrote:

> Change the log level of the following message to debug:
> 
> 	Unsupported SCSI Opcode 0xXX, sending CHECK_CONDITION.
> 
> This message is mostly helpful during debugging sessions in order to
> understand errors on the initiator side. But most of the time it's just
> useless and makes reading logs much harder.
> 
> [...]

Applied to 5.16/scsi-queue, thanks!

[1/1] scsi: target: core: Make logs less verbose
      https://git.kernel.org/mkp/scsi/c/05787e3456ff

-- 
Martin K. Petersen	Oracle Linux Engineering

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-10-12 20:35 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-29 11:50 [PATCH] scsi: target: core: Make logs less verbose Konstantin Shelekhin
2021-10-04 20:36 ` Lee Duncan
2021-10-05  3:13 ` Martin K. Petersen
2021-10-12 20:35 ` Martin K. Petersen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.