[tor-bugs] #22212 [Core Tor/Tor]: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel padding timeout scheduled 164729ms in the past. Did the monotonic clock just jump?

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Jan 29 10:04:06 UTC 2018


#22212: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel
padding timeout scheduled 164729ms in the past. Did the monotonic clock
just jump?
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:  mikeperry
     Type:  defect        |         Status:  reopened
 Priority:  Medium        |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal        |     Resolution:
 Keywords:  tor-client    |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:  Sponsor2
--------------------------+------------------------------------

Comment (by arma):

 For those who want to try the patch, here is what I'm running currently:

 {{{
 diff --git a/src/or/connection_or.c b/src/or/connection_or.c
 index dadfdc4..ecc1ae4 100644
 --- a/src/or/connection_or.c
 +++ b/src/or/connection_or.c
 @@ -603,6 +603,9 @@ connection_or_flushed_some(or_connection_t *conn)
  {
    size_t datalen;

 +  /* Update the channel's active timestamp */
 +  channel_timestamp_active(TLS_CHAN_TO_BASE(conn->chan));
 +
    /* The channel will want to update its estimated queue size */
    channel_update_xmit_queue_size(TLS_CHAN_TO_BASE(conn->chan));

 }}}
 It is alas a rare log message for me, so it's hard to easily tell if I
 have resolved the issue. Maybe somebody who is getting the log message
 more often than I am can try it too?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22212#comment:35>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list