src-test2/lib/libthr/thread, branch release/8.0.0_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.0.0_cvs2009-11-21T06:13:29ZCreate release/8.0.0 for the 8.0-RELEASE.2009-11-21T06:13:29ZKen Smithkensmith@FreeBSD.org2009-11-21T06:13:29Zurn:sha1:a4d3b78df842614c46b116fc5a6f470be637dccd
Approved by: re (implicit)
This commit was manufactured to restore the state of the 8.0-RELEASE image.
MFC r197445:2009-09-24T08:35:17ZAttilio Raoattilio@FreeBSD.org2009-09-24T08:35:17Zurn:sha1:917c07ca1da7b9a0ab3b31a0d842163c104e8ce5
Let fall down in the hard path (thus handling shared waiters wakeup
correctly) for the shared waiters also in the rwlock held in shared mode
as well, fixing possible deadlocks.
Please note that this is a special condition as we want this fix in
before RC2 as we assume it is critical and so it has been handled
as an instant-merge. For the STABLE_7 branch, 1 week before the MFC
is assumed.
Approved by: re (kib)
In the current code, rdlock_count is not correctly handled for some cases.2009-07-06T09:31:04ZAttilio Raoattilio@FreeBSD.org2009-07-06T09:31:04Zurn:sha1:137ae5d29191831b000584e869096796f9a88213
The most notable is that it is not bumped in rwlock_rdlock_common() when
the hard path (__thr_rwlock_rdlock()) returns successfully.
This can lead to deadlocks in libthr when rwlocks recursion in read mode
happens.
Fix the interested parts by correctly handling rdlock_count.
PR: threads/136345
Reported by: rink
Tested by: rink
Reviewed by: jeff
Approved by: re (kib)
MFC: 2 weeks
These are some cosmetic changes to improve the clarity of libthr's fork implementation.2009-05-11T16:45:53ZBrian Feldmangreen@FreeBSD.org2009-05-11T16:45:53Zurn:sha1:43af51a2b5e92a4b4a9f345800a929e0dc438737Now that the kernel defines CACHE_LINE_SIZE in machine/param.h, use2009-04-19T23:02:50ZRobert Watsonrwatson@FreeBSD.org2009-04-19T23:02:50Zurn:sha1:d1f2f1c3f3e9e3ce60528824509b42c1a9424b70
that definition in the custom locking code for the run-time linker
rather than local definitions.
Pointed out by: tinderbox
MFC after: 2 weeks
Forcibly unlock the malloc() locks in the child process after fork(),2009-03-19T10:32:25ZKonstantin Belousovkib@FreeBSD.org2009-03-19T10:32:25Zurn:sha1:29986e1bac92a068da1db1d7e68eb031e4fc49a7
by temporary pretending that the process is still multithreaded.
Current malloc lock primitives do nothing for singlethreaded process.
Reviewed by: davidxu, deischen
Don't ignore other fcntl functions, directly call __sys_fcntl if2009-03-09T05:54:43ZDavid Xudavidxu@FreeBSD.org2009-03-09T05:54:43Zurn:sha1:5b71b82e7029f3f02763c23fa24b149c0cb30c46
WITHOUT_SYSCALL_COMPAT is not defined.
Reviewed by: deischen
Don't reference non-existent __fcntl_compat if WITHOUT_SYSCALL_COMPAT is defined.2009-03-09T02:34:02ZDavid Xudavidxu@FreeBSD.org2009-03-09T02:34:02Zurn:sha1:c30c187d60572568da72c86d475e958d9a9bdc88
Submitted by: Pawel Worach "pawel dot worach at gmail dot com"
When libthr and rtld start up, there are a number of magic spells cast2008-12-07T02:32:49ZPeter Wemmpeter@FreeBSD.org2008-12-07T02:32:49Zurn:sha1:70ba1e8fc192b8d7e85bcf0869bfe0254bd1ef4d
in order to get the symbol binding state "just so". This is to allow
locking to be activated and not run into recursion problems later.
However, one of the magic bits involves an explicit call to _umtx_op()
to force symbol resolution. It does a wakeup operation on a fake,
uninitialized (ie: random contents) umtx. Since libthr isn't active, this
is harmless. Nothing can match the random wakeup.
However, valgrind finds this and is not amused. Normally I'd just
write a suppression record for it, but the idea of passing random
args to syscalls (on purpose) just doesn't feel right.
Provide custom simple allocator for rtld locks in libthr. The allocator2008-12-02T11:58:31ZKonstantin Belousovkib@FreeBSD.org2008-12-02T11:58:31Zurn:sha1:10b4034657dfc714985bcb76bdb93fdd7346a6c2
does not use any external symbols, thus avoiding possible recursion into
rtld to resolve symbols, when called.
Reviewed by: kan, davidxu
Tested by: rink
MFC after: 1 month