summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Added sysctl security.jail.jailed.pjd2004-02-191-0/+13
| | | | | | | | | | | | It returns 1 is process is inside of jail and 0 if it is not. Information if we are in jail or not is not a secret, there is plenty of ways to discover it. Many people are using own hack to check this and this will be a legal way from now on. It will be great if our starting scripts will take advantage of this sysctl to allow clean "boot" inside jail. Approved by: rwatson, scottl (mentor)
* Simplify check. We are only able to check exclusive lock and ifpjd2004-02-191-1/+5
| | | | | | 2nd condition is true, first one is true for sure. Approved by: jhb, scottl (mentor)
* Fixed ucred structure leak.pjd2004-02-192-0/+4
| | | | | | Approved by: scottl (mentor) PR: 54163 MFC after: 3 days
* MFi386: revision 1.466nyan2004-02-191-0/+1
|
* Add BSD compatibility tty ioctls LINUX_TIOCSBRK and LINUX_TIOCCBRK. Thisbms2004-02-192-0/+13
| | | | | | | addition appears to allow VMware 3 Workstation to operate with nmdm(4) as a virtual COM device. Tested by: Guido van Rooij
* When reparenting a process in the PT_DETACH code, only set p_sigparenttruckman2004-02-191-1/+2
| | | | | | to SIGCHLD if the new parent process is initproc. MFC after: 2 weeks
* Use size_t or ssize_t wherever appropriate instead of casting from int *tjr2004-02-192-26/+27
| | | | | | | to size_t *, which is incorrect because they may have different widths. This caused some subtle forms of corruption, the mostly frequently reported one being that the last character of a filename was sometimes duplicated on amd64.
* Enforce the file size limit in VOP_WRITE() as well as VOP_TRUNCATE();tjr2004-02-198-32/+22
| | | | pointed out by bde.
* - Correct a long-standing race condition in vm_page_try_to_free() thatalc2004-02-191-4/+3
| | | | | | | | could result in a dirty page being unintentionally freed. - Simplify the dirty page check in vm_page_dontneed(). Reviewed by: tegge MFC after: 7 days
* A Linux thread created using clone() should not send SIGCHLD to itstruckman2004-02-191-3/+3
| | | | | | | parent if no signal is specified in the clone() flags argument. PR: 42457 MFC after: 2 weeks
* Fix problem caused by previous commit where some users' buttonsnjl2004-02-192-11/+2
| | | | | | | stopped returning events. Don't disable the event when removing the handler because it still needs to be enabled for the other handler. Also, remove duplicate AcpiEnableEvent calls since the install function now does this for us.
* Add support for 'h' and 'hh' modifiers for printf(9).njl2004-02-191-2/+21
| | | | | Submitted by: Bruno Ducrot <ducrot AT poupinou.org> Reviewed by: bde
* Checkpoint the NOTES I was working on.obrien2004-02-191-152/+114
|
* Fix a long-standing bug where select on vchans doesn't workmatk2004-02-191-3/+13
| | | | | | (never wake up) by iterating over them when they exist. Approved by: tanimura (mentor)
* Switch to using the new $PIR interrupt routing code and remove the oldjhb2004-02-184-436/+22
| | | | | code. The pci_cfgreg.c file now just controls reading/writing PCI config registers.
* Rework the $PIR (aka PCIBIOS) PCI interrupt routing code and split it offjhb2004-02-181-609/+445
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into its own file: - All of the $PIR interrupt routing is now done in a link-centric fashion. When a host-PCI bridge that uses the $PIR attaches, it calls pir_parse() to parse the table. This scans for link devices and merges all the masks for each link device from the table entries. It then looks at the intline register of PCI devices connected to a link to figure out if the BIOS has routed this link and if so to which IRQ. - The IRQ for any given link can be overridden via a hint like so: 'hw.pci.link.0x62.irq=10' Any IRQ set in this matter is treated as if it were set that way by the BIOS. - We only call the BIOS to route each link device once. - When a PCI device wants to route an interrupt, we look it up in the $PIR to find the associated link. If the link is routed, we simply return the IRQ it is using. If it is not routed, we have to pick one. This uses a different algorithm from the old code. First off, when we try to pick an interrupt from a mask of possible interrupts, we try to pick the one that is least loaded as far as PCI devices. We maintain this weight based on the number of devices attached to each link device. When choosing an IRQ, we first attempt to route using any PCI only interrupts (the old code did this as well). If that doesn't work, we try to use the list of IRQs that the BIOS has used. This is a new step that the new code didn't do and avoids using IRQ 3 or 4 for every virgin interrupt routing. If none of the IRQs that the BIOS used worked, then we fall back to trying anything. - The fallback mask for !PC98 was fixed to include IRQ 3 and not allow IRQ 2. - We don't use the $PIR to route interrupts on a PCI-PCI bridge unless it has already been used to route on at least one Host-PCI bridge. This helps to avoid mixing and matching x86 firmware PCI interrupt routing methods (which is a Bad Thing(tm)). Silence on: current@
* Change the disk(9) API in order to make device removal more robust.phk2004-02-1828-273/+335
| | | | | | | | | | | | | | | | | | | | | | | | Previously the "struct disk" were owned by the device driver and this gave us problems when the device disappared and the users of that device were not immediately disappearing. Now the struct disk is allocate with a new call, disk_alloc() and owned by geom_disk and just abandonned by the device driver when disk_create() is called. Unfortunately, this results in a ton of "s/\./->/" changes to device drivers. Since I'm doing the sweep anyway, a couple of other API improvements have been carried out at the same time: The Giant awareness flag has been flipped from DISKFLAG_NOGIANT to DISKFLAG_NEEDSGIANT A version number have been added to disk_create() so that we can detect, report and ignore binary drivers with old ABI in the future. Manual page update to follow shortly.
* Add partial support for large (>4GB) files on ext2 filesystems. Thistjr2004-02-186-2/+32
| | | | | | | | support is partial in that it will refuse to create large files on filesystems that haven't been upgraded to EXT2_DYN_REV or that don't have the EXT2_FEATURE_RO_COMPAT_LARGE_FILE flag set in the superblock. MFC after: 2 weeks
* Don't ignore errors from vfs_allocate_syncvnode.cperciva2004-02-181-1/+1
| | | | | | PR: kern/18503 Submitted by: Anatoly Vorobey <mellon@pobox.com> Approved by: rwatson (mentor)
* Fixed some style bugs (spaces instead of tabs in macro definitions ...).bde2004-02-181-11/+11
|
* Checkpoint a hack to enable running i386 libc_r binaries on a 64 bitpeter2004-02-181-4/+22
| | | | | | kernel. I'm not happy with it yet - refinements are to come. This hack allows the kern.ps_strings and kern.usrstack sysctls to respond to a 32 bit request, such as those coming from emulated i386 binaries.
* Backout MT_TAG removal (i.e. bring back MT_TAGs) for now, as dummynet ismlaier2004-02-1817-465/+442
| | | | | | not working properly with the patch in place. Approved by: bms(mentor)
* Add vector for memmove() (currently aliased to memcpy()) a implementwpaul2004-02-171-0/+20
| | | | ExInterlockedAddLargeStatistic().
* Dont use the bio_taskqueue if we are in timeout.sos2004-02-171-2/+2
| | | | | Use taskqueue_thread rather than taskqueue_swi (maybe we should have a taskqueue_ata).
* Do not place dirmask in unnamed padding. Move it to the bottom of thistrhodes2004-02-171-1/+1
| | | | | | list where it should have been added originally. Prodded by: bde
* IPSEC and FAST_IPSEC have the same internal API now;ume2004-02-177-105/+42
| | | | | | so merge these (IPSEC has an extra ipsecstat) Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
* Correct a comment.dwmalone2004-02-172-2/+2
| | | | Reviewed by: alfred, tanimura
* Backed out previous commit since it just causes panics unless a specialbde2004-02-171-1/+1
| | | | | | | | | | | | value for MSGBUF_SIZE is configured. MSGBUF_SIZE = (32768 * bootverbose ? 2 : 1) is always 1 or 2, so there is not enough space in the buffer for metadata, and blindly using the nonexistent space tends to cause fatal pagefaults. I think MSGBUF_SIZE = (32768 * (bootverbose ? 2 : 1)) would be always 32768 since bootverbose is only statically initialized to 0 early when MSGBUF_SIZE is used. MSGBUF_SIZE = (32768 * ((boothowto & RB_VERBOSE) ? 2 : 1)) should work, but this belongs in <sys/msgbuf.h> even less than previous versions. MSGBUF_SIZE shouldn't be a macro.
* Mechanical whistespace cleanup.des2004-02-171-19/+19
|
* If the "next free cluster" field of the FSInfo block is 0xFFFFFFFF,tjr2004-02-171-2/+4
| | | | | | | | | | it means that the correct value is unknown. Since this value is just a hint to improve performance, initially assume that the first non-reserved cluster is free, then correct this assumption if necessary before writing the FSInfo block back to disk. PR: 62826 MFC after: 2 weeks
* Re-add sio.S, and properly deal with assembler files.ru2004-02-174-383/+8
| | | | Repocopied by: joe
* Fix the AMD64 build: this file shouldn't exist.obrien2004-02-161-80/+0
|
* Remove some more 'makedev' related macros.le2004-02-161-10/+0
| | | | Approved by: grog (mentor)
* Shorten the name of the socket option used to enable TCP-MD5 packetbms2004-02-162-3/+3
| | | | | | treatment. Submitted by: Vincent Jardin
* Back out previous commit due to objections.des2004-02-161-2/+0
|
* Back out previous commit; it doesn't seem to do what I thought it does.des2004-02-161-8/+0
|
* Increase the size of MSGBUF_SIZE if booted with -v.obrien2004-02-161-1/+1
|
* Don't panic if we fail to satisfy an M_WAITOK request; return 0 instead.des2004-02-161-0/+2
| | | | The calling code will either handle that gracefully or cause a page fault.
* Don't bother storing a result when all you need are the side effects.des2004-02-161-5/+5
|
* Avoid code duplication on platforms where int and long are the same size.des2004-02-161-0/+8
|
* Random style fixes and a comment update. No functional changes.des2004-02-161-4/+4
|
* correct function name in comment.ume2004-02-161-18/+18
| | | | Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
* We aren't D_TAPE. We aren't anything. The reasons why this was ever setmjacob2004-02-161-1/+0
| | | | at all is lost in the mists of time.
* Fix type in a sysctl. It used to be: net.key.prefered_oldsaguido2004-02-161-5/+5
| | | | | | | and is corrected to net.key.preferred_oldsa This makes it consistent with the KAME IPsec implementation. Approved by: sam
* don't update outgoing ifp, if ipsec tunnel mode encapsulationume2004-02-161-3/+5
| | | | | | was not made. Obtained from: KAME
* nuke unused functions.ume2004-02-163-53/+0
| | | | Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
* we don't need to include ipsec.h.ume2004-02-161-8/+0
| | | | Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
* Spell types consistently throughout this file. Do not use the __packed ↵bms2004-02-161-4/+4
| | | | | | attribute, as we are often #include'd from userland without <sys/cdefs.h> in front of us, and it is not strictly necessary. Noticed by: Sascha Blank
* - Clean up global data.simokawa2004-02-163-38/+58
| | | | | | - Force dcons to be the high-level console after dcons_crom has been attached. - Add a tunable to be the high-level console.
* Correct a long-standing race condition in vm_contig_launder() that couldalc2004-02-161-0/+2
| | | | | | | | | result in a panic "vm_page_cache: caching a dirty page, ...": Access to the page must be restricted or removed before calling vm_page_cache(). This race condition is identical in nature to that which was addressed by vm_pageout.c's revision 1.251 and vm_page.c's revision 1.275. MFC after: 7 days
OpenPOWER on IntegriCloud