src-test2/sys/kern, branch release/5.5.0

MFC: kern_event.c v1.97

2006-04-04T17:32:20Z

clear any action flags on the register knote Approved by: re (scottl)

MFC: kern_event.c v1.96

2006-04-02T08:22:43Z

fix race condition Approved by: re (hrs)

MFC link_elf.c:1.86 to RELENG_5:

2006-03-11T14:19:22Z

Check to see if the hash table is present in link_elf_lookup_symbol() before dereferencing it. Certain corrupt kernel modules might not have a valid hash table, and would cause a kernel panic when they were loaded. Instead of panic'ing, the kernel now prints out a warning that it is missing the symbol hash table. Approved by: re (mux)

MFC kern_sig.c 1.319 sys_process.c 1.134 to RELENG_5:

2006-02-28T15:02:51Z

Avoid kernel panic when attaching a process which may not be stopped by debugger, e.g process is dumping core. Only access p_xthread if P_STOPPED_TRACE is set, this means thread is ready to exchange signal with debugger, print a warning if P_STOPPED_TRACE is not set due to some bugs in other code, if there is. The patch has been tested by Anish Mistry mistry.7 at osu dot edu, and is slightly adjusted. Approved by: re (scottl)

MFC kern_kse.c 1.215 sys_process.c 1.132 to RELENG_5:

2006-02-28T14:58:36Z

Fix a LOR between sched_lock and sleep queue lock. kern_kse.c 1.216: Add missing brackets. LOR ID: 060 Approved by: re (scottl)

MFC:

2006-01-30T12:17:29Z

Add bounds checking to the setenv part of the kernel environment. This has no security implications since only root is allowed to use kenv(1) (and corrupt the kernel memory after adding too much variables previous to this commit). This is based upon the PR [1] mentioned below, but extended to check both bounds (in case of an overflow of the counting variable) and to comply to the style of the function. An overflow of the counting variable shouldn't happen after adding the check for the upper bound, but better safe than sorry (in case some other function in the kernel overwrites random memory). An interested soul may want to add a printf to notify root in case the bounds are hit. Also allocate KENV_SIZE+1 entries (the array is NULL-terminated), since the comment for KENV_SIZE says it's the maximum number of environment strings. [2] Reorder statements to avoid accessing unknown memory. In theory, invoking kenv with very long string can panic kernel. PR: 83687 [1] Submitted by: Harry Coin [1]

MFC:

2006-01-30T12:15:58Z

The resource_xxx routines in subr_hints.c are called before and after the kenv environment in kern_environment.c switches to dynamic kenv. The prior call sets the static variable hintp to the static hints in subr_hints.c (hintmode==0). However, changes to the environment are not detected by the resource_xxx lookups after the change to dynamic kernel environment, so the lookup routines only report the old stuff of hintmode==0, even after the change to the dynamic kenv. This causes kenv users to see a different environment than the kernel routines. This is a problem in the mixer.c code that looks up initial mixer volume settings from the hints: If the hints are dynamic and not from the device.hints file, mixer.c doesn't see them, but kenv does. The patch from the PR (modified to comply to the style of the function) solves this. PR: 83686 Submitted by: Harry Coin

MFC Rev 1.31: Don't use Giant for fast taskqueues.

2006-01-29T21:51:33Z

MFC kern_sysctl.c 1.168

2006-01-28T00:43:53Z

Touch all the pages wired by sysctl_wire_old_buffer() to avoid PTE modified bit emulation traps on Alpha while holding locks in the sysctl handler.

MFC subr_witness.c 1.198 and 1.200.

2006-01-26T02:33:36Z

Original commit messages: Log: Track all lock relationships instead of pruning direct relationships if an indirect relationship exists (keep both A->B->C and A->C). This allows witness_checkorder() to use isitmychild() instead of the much more expensive isitmydescendant() to check for valid lock ordering. Don't do an expensive tree walk to update the w_level values when the tree is updated. Only update the w_level values when using the debugger to display the tree. Nuke the experimental "witness_watch > 1" mode that only compared w_level for the two locks. This information is no longer maintained at run time, and the use of isitmychild() in witness_checkorder should bring performance close enough to the acceptable level that this hack is not needed. Report witness data structure allocation statistics under the debug.witness sysctl. Reviewed by: jhb MFC after: 30 days Log: Relocate witness_levelall(), witness_leveldescendents(), and witness_displaydescendants() so that they are protected by "#ifdef DDB/#endif" to unbreak kernels not using "option DDB". MFC after: 3 weeks