From: Quan Nguyen <quan@os.amperecomputing.com>
To: Cosmo Chou <chou.cosmo@gmail.com>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, cosmo.chou@quantatw.com,
potin.lai@quantatw.com, minyard@acm.org
Subject: Re: [PATCH] ipmi: ssif_bmc: Move smbus_cmd assignment after cleanup
Date: Fri, 3 Jan 2025 10:44:46 +0700 [thread overview]
Message-ID: <c92cab21-ca41-4f34-b507-e773c463d82f@os.amperecomputing.com> (raw)
In-Reply-To: <20250101165431.2113407-1-chou.cosmo@gmail.com>
On 01/01/2025 23:54, Cosmo Chou wrote:
> Move smbus_cmd assignment to the end of process_smbus_cmd() to ensure
> the new command is not lost when complete_response() is triggered.
>
Thanks Cosmo for the catch.
And, IMHO, the root cause is the memset() on part buffer called in
complete_response() is not quite correct. In the current implementation,
the complete_response() should only be called when the READ is
completed, ie: only on I2C_SLAVE_STOP of READ transaction, otherwise all
the info of current on-going request will be mistakenly cleared as in
this case.
This patch is good and I wonder if we can make this a bit further as below?
diff --git a/drivers/char/ipmi/ssif_bmc.c b/drivers/char/ipmi/ssif_bmc.c
index a14fafc583d4..310f17dd9511 100644
--- a/drivers/char/ipmi/ssif_bmc.c
+++ b/drivers/char/ipmi/ssif_bmc.c
@@ -292,7 +292,6 @@ static void complete_response(struct ssif_bmc_ctx
*ssif_bmc)
ssif_bmc->nbytes_processed = 0;
ssif_bmc->remain_len = 0;
ssif_bmc->busy = false;
- memset(&ssif_bmc->part_buf, 0, sizeof(struct ssif_part_buffer));
wake_up_all(&ssif_bmc->wait_queue);
}
@@ -744,9 +743,11 @@ static void on_stop_event(struct ssif_bmc_ctx
*ssif_bmc, u8 *val)
ssif_bmc->aborting = true;
}
} else if (ssif_bmc->state == SSIF_RES_SENDING) {
- if (ssif_bmc->is_singlepart_read || ssif_bmc->block_num
== 0xFF)
+ if (ssif_bmc->is_singlepart_read || ssif_bmc->block_num
== 0xFF) {
+ memset(&ssif_bmc->part_buf, 0, sizeof(struct
ssif_part_buffer));
/* Invalidate response buffer to denote it is
sent */
complete_response(ssif_bmc);
+ }
ssif_bmc->state = SSIF_READY;
}
Thanks and Happy New Year.
- Quan
next prev parent reply other threads:[~2025-01-03 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 16:54 [PATCH] ipmi: ssif_bmc: Move smbus_cmd assignment after cleanup Cosmo Chou
2025-01-03 3:20 ` Corey Minyard
2025-01-03 3:49 ` Quan Nguyen
2025-01-03 3:44 ` Quan Nguyen [this message]
2025-01-03 13:01 ` Corey Minyard
2025-01-06 2:32 ` Quan Nguyen
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=c92cab21-ca41-4f34-b507-e773c463d82f@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=chou.cosmo@gmail.com \
--cc=cosmo.chou@quantatw.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=potin.lai@quantatw.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