| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2020-01-16 | malloc: remove locking | Dan Cross | 1 | -22/+3 | |
| The issue manifests in fork: POSIX fork mandates that a fork'd process is created with a single thread. If a multithreaded program forks, and some thread was in malloc() when the fork() happened, then in the child the lock will be held but there will be no thread to release it. We assume the system malloc() must already know how to deal with this and is thread-safe, but it won't know about our custom spinlock. Judging that this is no longer necessary (the lock code was added 15 years ago) we remove it. Signed-off-by: Dan Cross <cross@gajendra.net> | |||||
| 2020-01-10 | Trivial changes: whitespace and modes. | Dan Cross | 1 | -2/+2 | |
| Remote whitespace at the ends of lines. Remove blank lines from the ends of files. Change modes on source files so that they are not executable. Signed-off-by: Dan Cross <cross@gajendra.net> | |||||
| 2005-07-14 | cannot trust system libraries to lock properly. sigh. | rsc | 1 | -3/+20 | |
| 2004-06-17 | Unused variable. | wkj | 1 | -2/+0 | |
| 2004-06-09 | asdf | rsc | 1 | -30/+13 | |
| 2004-05-23 | lock malloc ourselves | rsc | 1 | -1/+48 | |
| 2003-12-11 | More files related to user-level file servers. | rsc | 1 | -0/+11 | |
| Also add acme! | |||||