From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net 4/6] rxrpc: Fix calc of resend age
Date: Thu, 01 Sep 2022 09:07:50 +0100 [thread overview]
Message-ID: <166201967050.3817988.4307733641865890404.stgit@warthog.procyon.org.uk> (raw)
In-Reply-To: <166201964443.3817988.12088441548413332725.stgit@warthog.procyon.org.uk>
Fix the calculation of the resend age to add a microsecond value as
microseconds, not nanoseconds.
Signed-off-by: David Howells <dhowells@redhat.com>
---
net/rxrpc/call_event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/call_event.c b/net/rxrpc/call_event.c
index f8ecad2b730e..2a93e7b5fbd0 100644
--- a/net/rxrpc/call_event.c
+++ b/net/rxrpc/call_event.c
@@ -166,7 +166,7 @@ static void rxrpc_resend(struct rxrpc_call *call, unsigned long now_j)
_enter("{%d,%d}", call->tx_hard_ack, call->tx_top);
now = ktime_get_real();
- max_age = ktime_sub(now, jiffies_to_usecs(call->peer->rto_j));
+ max_age = ktime_sub_us(now, jiffies_to_usecs(call->peer->rto_j));
spin_lock_bh(&call->lock);
next prev parent reply other threads:[~2022-09-01 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:07 [PATCH net 0/6] rxrpc: Miscellaneous fixes David Howells
2022-09-01 8:07 ` [PATCH net 1/6] rxrpc: Fix ICMP/ICMP6 error handling David Howells
2022-09-01 8:07 ` [PATCH net 2/6] rxrpc: Fix an insufficiently large sglist in rxkad_verify_packet_2() David Howells
2022-09-01 8:07 ` [PATCH net 3/6] rxrpc: Fix local destruction being repeated David Howells
2022-09-01 8:07 ` David Howells [this message]
2022-09-01 8:07 ` [PATCH net 5/6] afs: Use the operation issue time instead of the reply time for callbacks David Howells
2022-09-01 8:08 ` [PATCH net 6/6] rxrpc: Remove rxrpc_get_reply_time() which is no longer used David Howells
2022-09-01 10:23 ` [PATCH net 0/6] rxrpc: Miscellaneous fixes David Howells
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=166201967050.3817988.4307733641865890404.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).