[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
Sat Jan 13 08:36:00 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):

 Hm:
 {{{
 Jan 13 02:51:31.465 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 5058 ms. Delta 6ms
 Jan 13 02:51:38.308 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 6843 ms. Delta 20ms
 Jan 13 02:51:42.244 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 3938 ms. Delta 4ms
 Jan 13 02:54:28.603 [notice] Channel padding timeout scheduled 159796ms in
 the past.
 Jan 13 02:54:28.603 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 166359 ms. Delta 159798ms
 Jan 13 02:54:33.863 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 5260 ms. Delta 6ms
 Jan 13 02:54:43.120 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 9258 ms. Delta 10ms
 Jan 13 02:54:50.978 [info]
 channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive
 on 3895 to 99.107.176.235:57814 (988E6BEC7AB2451AA66D2F9B2A9FA2A928C9795C)
 after 7860 ms. Delta 6ms
 }}}

 I wonder if my conn to this relay was full of stuff that was trying to
 flush, during this 160s that surprised the netflow padder. That is, maybe
 if the outbuf-or-whatever never goes empty, we're never updating the "time
 to next netflow" timer? And it finally does go empty, and the netflow
 timer says "omg why did nobody call me until now?"

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


More information about the tor-bugs mailing list