summaryrefslogtreecommitdiff
path: root/lib/libpthread/pthread_kill.3
diff options
context:
space:
mode:
Diffstat (limited to 'lib/libpthread/pthread_kill.3')
0 files changed, 0 insertions, 0 deletions
4fc762a5644c8422c1a732028'>fix the function pointer and callback mess:christos - callback functions return 0 and their result is not checked; make them void. - there are two types of callbacks and they used to overload their parameters and the callback structure; separate them into "function" and "value" callbacks. - make the wait function signature consistent. 2019-02-09- Change the allocation macros to be more like function callschristos - Change sizeof(type) -> sizeof(*variable) - Use macros for the long buffer length allocations - Remove "bit polishing" memsets() -- do them only once - Remove unnecessary casts Thanks to oster@ for finding bugs and testing. 2014-06-14Change dk_lookup() to return an anonymous vnode not associated withhannken any file system. Change all consumers of dk_lookup() to get the device from "v_rdev" instead of VOP_GETATTR() as specfs does not support VOP_GETATTR(). Devices obtained with dk_lookup() will no longer disappear on forced unmounts. Fix for PR kern/48849 (root mirror raid fails on shutdown) Welcome to 6.99.44 2011-10-14Change the vnode locking protocol of VOP_GETATTR() to request at leasthannken a shared lock. Make all calls outside of file systems respect it. The calls from file systems need review. No objections from tech-kern. 2011-08-03Remove unused 'struct lwp *' from rf_getdisksize. No functional changes.oster 2011-05-11convert the main raidPtr mutex to a kmutex, and add a couple of cv's tomrg cover the old sleep/wakeup points for adding_hot_spare and waitForReconCond. convert all remaining simple_lock's to kmutexes (they're not used or compiled right now... even with all options enabled) and remove the support for them. this leaves just a pair of tsleep()/wakeup() calls using old scheduling APIs. 2011-05-01convert mcpair to kmutex.mrg 2011-02-19Define accessors for number of blocks and partition size in theenami component label and use them where appropriate. Disscussed on tech-kern. 2010-11-19Introduce struct pathbuf. This is an abstraction to hold a pathnamedholland and the metadata required to interpret it. Callers of namei must now create a pathbuf and pass it to NDINIT (instead of a string and a uio_seg), then destroy the pathbuf after the namei session is complete. Update all namei call sites accordingly. Add a pathbuf(9) man page and update namei(9). The pathbuf interface also now appears in a couple of related additional places that were passing string/uio_seg pairs that were later fed into NDINIT. Update other call sites accordingly. 2010-11-01add support for >2TB raid devices.mrg - add two new members to the component label: u_int numBlocksHi u_int partitionSizeHi and store the top 32 bits of the real number of blocks and partition size. modify rf_print_component_label(), rf_does_it_fit(), rf_AutoConfigureDisks() and rf_ReconstructFailedDiskBasic(). - call disk_blocksize() after disk_attach() [ from mlelstv ] - shift the block number relative to DEV_BSHIFT in raidstart() and InitBP() so that accesses work for non 512-byte devices. [ from mlelstv ] - update rf_getdisksize() to use the new getdisksize() [ from mlelstv. this part needs a separate change for netbsd-5. ] reviewed by: oster, christos and darrenr 2009-11-17Finally commit the RAIDframe parity map Summer Of Code project.jld Drastically reduces the amount of time spent rewriting parity after an unclean shutdown by keeping better track of which regions might have had outstanding writes. Enabled by default; can be disabled on a per-set basis, or tuned, with the new raidctl(8) commands. Discussed on tech-kern@ to a general air of approval; exhortations to commit from mrg@, christos@, and others. Thanks to Google for their sponsorship, oster@ for mentoring the project, assorted developers for trying very hard to break it, and probably more I'm forgetting. 2008-01-26In a land before time, when kernel processes roamed the system, weoster needed to keep track of the kernel process that opened a device in order to close it with the right credentials. Flash forward to today where curlwp is now quite sufficient. 2007-11-26Remove the "struct lwp *" argument from all VFS and VOP interfaces.pooka The general trend is to remove it from all kernel interfaces and this is a start. In case the calling lwp is desired, curlwp should be used. quick consensus on tech-kern 2007-07-18Fix fallout from recent kthread changes.ad 2007-06-26Change dk_lookup() to accept an additional argument of the type enum uio_segcube that tells whether the given path is in user space or kernel space, so it can tell NDINIT(). While the raidframe calls were ok, both ccd(4) and cgd(4) were passing pointers to user space data, which leads to strange error on i386, as reported by Jukka Salmi on current-users. The issue has been there since last august, I'm actually a bit surprised that no one in the meantime has used ccd(4) or cgd(4) on an arch where it would have simply faulted. 2006-11-16__unused removal on arguments; approved by core.christos 2006-10-12- sprinkle __unused on function decls.christos - fix a couple of unused bugs - no more -Wno-unused for i386