[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7419 [Tor]: Choose a faster memwipe implementation

#7419: Choose a faster memwipe implementation
-----------------------------+------------------------------------
     Reporter:  nickm        |      Owner:
         Type:  enhancement  |     Status:  needs_review
     Priority:  normal       |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  tor-relay, nickm-patch
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------------------

Comment (by nickm):

 To be clear, I don't think any of my patch requires undefined behavior; do
 you?  In most cases, it accesses non-volatile objects through a volatile
 pointer; not the other way around.  Does the standard forbid that too?  Or
 have I misunderstood?

 Also fwiw, the "external memset wrapper" solution isn't going to work with
 any  compiler that does whole-program optimization.

 The check-after-memset thing you propose might work too .. but I think
 that a compiler is also technically allowed to optimize that whole thing
 out, along with the memset, if it can prove that nothing else will look at
 the buffer afterwards.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7419#comment:11>
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