From: Xiang Zhang <hawkxiang.cpp@gmail.com>
To: lduncan@suse.com, cleech@redhat.com, michael.christie@oracle.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiang Zhang <hawkxiang.cpp@gmail.com>
Subject: [PATCH] scsi: iscsi: special case for GET_HOST_STATS
Date: Fri, 3 Jan 2025 19:11:09 +0800 [thread overview]
Message-ID: <20250103111109.21609-1-hawkxiang.cpp@gmail.com> (raw)
Special case for ISCSI_UEVENT_GET_HOST_STATS:
- On success: send reply and stats from iscsi_get_host_stats()
within if_recv_msg().
- On error: fall through.
Signed-off-by: Xiang Zhang <hawkxiang.cpp@gmail.com>
---
drivers/scsi/scsi_transport_iscsi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/scsi/scsi_transport_iscsi.c b/drivers/scsi/scsi_transport_iscsi.c
index fde7de3b1e55..ad4186da1cb4 100644
--- a/drivers/scsi/scsi_transport_iscsi.c
+++ b/drivers/scsi/scsi_transport_iscsi.c
@@ -4113,6 +4113,8 @@ iscsi_if_rx(struct sk_buff *skb)
break;
if (ev->type == ISCSI_UEVENT_GET_CHAP && !err)
break;
+ if (ev->type == ISCSI_UEVENT_GET_HOST_STATS && !err)
+ break;
err = iscsi_if_send_reply(portid, nlh->nlmsg_type,
ev, sizeof(*ev));
if (err == -EAGAIN && --retries < 0) {
--
2.44.0
next reply other threads:[~2025-01-03 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 11:11 Xiang Zhang [this message]
2025-01-03 18:46 ` [PATCH] scsi: iscsi: special case for GET_HOST_STATS michael.christie
2025-01-06 4:16 ` [PATCH v2] scsi: iscsi: Fix redundant response for ISCSI_UEVENT_GET_HOST_STATS request Xiang Zhang
2025-01-06 21:03 ` Mike Christie
2025-01-07 2:24 ` [PATCH v3] " Xiang Zhang
2025-01-08 1:48 ` michael.christie
2025-01-10 21:15 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 6:21 [PATCH] scsi: iscsi: special case for GET_HOST_STATS Xiang Zhang
2024-11-03 7:02 Xiang Zhang
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=20250103111109.21609-1-hawkxiang.cpp@gmail.com \
--to=hawkxiang.cpp@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cleech@redhat.com \
--cc=lduncan@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@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 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.