| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Don't grab the fd read lock for getsockopt(2), setsockopt(2), |   kurt | 2008-06-03 | 1 | -5/+17 |
| | | | | | | | | | getpeername(2) or getsockname(2). Its not needed and causes threads to block when another thread is blocked and holding the read lock. Instead just protect against fd state transitions. Blocking problem reported by David S H Rosenthal from lockss.org okay beck@ "looks sane" deraadt@ | ||||
| * | sync with FreeBSD |   d | 1999-11-25 | 1 | -3/+4 |
| | | |||||
| * | deal with socklen_t |   deraadt | 1999-02-16 | 1 | -2/+2 |
| | | |||||
| * | ident | d | 1999-01-06 | 1 | -0/+1 |
| | | |||||
| * | experimental threaded libc - kernel only | d | 1998-08-27 | 1 | -0/+50 |
 |
index : wireguard-openbsd | |
| WireGuard implementation for the OpenBSD kernel | Matt Dunwoodie |
| summaryrefslogtreecommitdiffstats |