From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Daniel Hsu <d486250@gmail.com>
Cc: matt@codeconstruct.com.au, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Daniel Hsu <Daniel-Hsu@quantatw.com>
Subject: Re: [PATCH] mctp: Fix incorrect tx flow invalidation condition in mctp-i2c
Date: Tue, 25 Mar 2025 16:30:00 +0800 [thread overview]
Message-ID: <b24e0c05bc9ae6eb102d71119bc3dd917a7f7c6d.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250325081008.3372960-1-Daniel-Hsu@quantatw.com>
Hi Daniel,
> Previously, the condition for invalidating the tx flow in
> mctp_i2c_invalidate_tx_flow() checked if `rc` was nonzero.
> However, this could incorrectly trigger the invalidation
> even when `rc > 0` was returned as a success status.
Yes, and we should be seeing rc > 0 in normal behaviour...
> This patch updates the condition to explicitly check for `rc < 0`,
> ensuring that only error cases trigger the invalidation.
Looks good to me. I'll do some testing in my environment here, but in
the meantime:
Reviewed-by: Jeremy Kerr <jk@codeconstruct.com.au>
I figure you'll want to target the net (not net-next) tree, in which
case you'll probably need this:
Fixes: 338a93cf4a18 ("net: mctp-i2c: invalidate flows immediately on TX errors")
Thanks for the contribution.
Cheers,
Jeremy
next prev parent reply other threads:[~2025-03-25 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 8:10 Daniel Hsu
2025-03-25 8:30 ` Jeremy Kerr [this message]
2025-03-26 13:10 ` patchwork-bot+netdevbpf
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=b24e0c05bc9ae6eb102d71119bc3dd917a7f7c6d.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=Daniel-Hsu@quantatw.com \
--cc=andrew+netdev@lunn.ch \
--cc=d486250@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®