[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18322 [Core Tor/Tor]: Log unparseable votes so they can be analysed
#18322: Log unparseable votes so they can be analysed
-------------------------------------------------+-------------------------
Reporter: teor | Owner: andrea
Type: defect | Status:
Priority: Medium | needs_revision
Component: Core Tor/Tor | Milestone: Tor:
Severity: Normal | 0.2.9.x-final
Keywords: tor-dos, TorCoreTeam201606, review- | Version:
group-4 | Resolution:
Parent ID: #17293 | Actual Points: 3
Reviewer: | Points: 2
| Sponsor:
| SponsorU-can
-------------------------------------------------+-------------------------
Comment (by nickm):
> Files we generate here can't be, since they had to fit in process memory
to get written, but I guess you can make up some weird case where we also
do the scanning for existing files thing, and the user switches between
running a 32-bit and a 64-bit Tor on the same directory. I'll switch it to
uint64_t, though, just to be safe.
Also there's the case where we get some number of objects that fit into
address space one at a time, but when you add them up, the sum overflows.
>What does this mean?
I have no idea. I'll let you know if I remember. Sometimes I start
writing sentences and they just
wrt all other stuff, I agree with you. :) Thanks!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18322#comment:23>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs