op public repos

Commits

Commit:: 7bf2db4c2ae30c0f7b320e57060715bf6279e98a
From:: Dan Cross <cross@gajendra.net>
Date:: Thu Jan 16 16:54:19 2020 UTC

malloc: remove locking 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>

diff | patch | tree

Commit:: fa325e9b42b0bdfb48857d1958d9fb7ceac55151
From:: Dan Cross <cross@gajendra.net>
Date:: Fri Jan 10 14:54:30 2020 UTC

Trivial changes: whitespace and modes. 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>

diff | patch | tree

Commit:: 8be32ce2cb17950569b94273cee6099289c4d022
From:: rsc <devnull@localhost>
Date:: Thu Jul 14 00:06:43 2005 UTC

cannot trust system libraries to lock properly. sigh.

diff | patch | tree

Commit:: 72a653997c4835aeddea5a8aeda377e2b611fcae
From:: wkj <devnull@localhost>
Date:: Thu Jun 17 01:59:07 2004 UTC

Unused variable.

diff | patch | tree

Commit:: 9c635587071dcd7db349ec24ece1b397d24ac486
From:: rsc <devnull@localhost>
Date:: Wed Jun 9 14:22:08 2004 UTC

asdf

diff | patch | tree

Commit:: 7e0e6522e576bc35b55a7182c23fb752cc1ec636
From:: rsc <devnull@localhost>
Date:: Sun May 23 00:58:23 2004 UTC

lock malloc ourselves

diff | patch | tree

Commit:: b3994ec5c78e6c18885079b58abb7fb997899c3f
From:: rsc <devnull@localhost>
Date:: Thu Dec 11 17:50:28 2003 UTC

More files related to user-level file servers. Also add acme!

diff | patch | tree