summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* - Add my birthday to the calendar.lulf2007-10-251-0/+1
| | | | Approved by: kib (mentor)
* - Show that pjd@ and kib@ are my mentors, and that I work in src.lulf2007-10-251-0/+5
| | | | Approved by: kib (mentor)
* Nuke rc.d/nfslocking which has been superceeded by rc.d/{lockd,statd}mtm2007-10-253-64/+3
|
* Change a tab back to a space between #define and __FreeBSD_version.erwin2007-10-251-1/+1
| | | | | | This breaks OSVERSION determination in all ports. Reviewed by: rodrigc
* Don't attach to the "IBM0057" ID. This ID is used by IBM machines forjhb2007-10-251-1/+1
| | | | | | | | | | the PS/2 mouse controller. Thus, when acpi_ibm(4) claimed the mouse device, the mouse would stop working. The one ACPI dump of an R40 that I've looked at includes an HKEY device with the proper "IBM0068" ID, so I'm not sure how the "IBM0057" ID could have helped at all. MFC after: 1 week Approved by: njl
* Fix variable name to be clear what it means.takawata2007-10-251-3/+3
|
* Remove unnecessary whitespacemtm2007-10-251-1/+1
|
* Break out of the I/O retry loop as soon as an I/O operation succeeds ratherjhb2007-10-251-0/+2
| | | | | | than always retrying operations three times. Submitted by: nyan
* Turn EC into poll mode before device_resume invoked .takawata2007-10-251-3/+34
|
* Normalize TCP syncache-related MAC Framework entry points to match mostrwatson2007-10-258-50/+50
| | | | | | | other entry points in the form mac_<object>_method(). Discussed with: csjp Obtained from: TrustedBSD Project
* MFi386: part of 1.52nyan2007-10-251-32/+33
| | | | | Split the pc98_partition specific routine in bd_opendisk() into bd_open_pc98().
* Align.obrien2007-10-257-77/+77
|
* MFi386: part of revision 1.51nyan2007-10-251-161/+83
| | | | | | | | | Rework the read/write support in the bios disk driver some to cut down on duplicated code. - All of the bounce buffer and retry logic duplicated in bd_read() and bd_write() are merged into a single bd_io() routine that takes an extra direction argument. bd_read() and bd_write() are now simple wrappers around bd_io().
* The AWK 23-Oct-2007 release includes fixes for FreeBSD PR's bin/104795obrien2007-10-253-50/+1
| | | | and bin/100443.
* Document the bwk_20071023 import.obrien2007-10-251-4/+4
|
* This commit was generated by cvs2svn to compensate for changes in r172958,obrien2007-10-253-4/+12
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Vendor import of bwk's 23-Oct-2007 release.obrien2007-10-253-4/+12
| | | | | | | | This includes fixes for FreeBSD PR's: bin/104795, bin/100443
* | Rename mac_associate_nfsd_label() to mac_proc_associate_nfsd(), and moverwatson2007-10-258-51/+51
| | | | | | | | | | | | | | | | | | from mac_vfs.c to mac_process.c to join other functions that setup up process labels for specific purposes. Unlike the two proc create calls, this call is intended to run after creation when a process registers as the NFS daemon, so remains an _associate_ call.. Obtained from: TrustedBSD Project
* | Consistently name functions for mac_<policy> as <policy>_whatever ratherrwatson2007-10-2511-2761/+2722
| | | | | | | | | | | | | | | | | | | | | | than mac_<policy>_whatever, as this shortens the names and makes the code a bit easier to read. When dealing with label structures, name variables 'mb', 'ml', 'mm rather than the longer 'mac_biba', 'mac_lomac', and 'mac_mls', likewise making the code a little easier to read. Obtained from: TrustedBSD Project
* | Remove some debugging code that, while useful, doesn't belong in the committedtrhodes2007-10-252-16/+6
| | | | | | | | | | | | version. While here, expand a macro only used once. Discussed with/oked by: bde
* | Further MAC Framework cleanup: normalize some local variable names andrwatson2007-10-256-48/+49
| | | | | | | | | | | | clean up some comments. Obtained from: TrustedBSD Project
* | Load the bytes into the EMAC's MAC address register in the properimp2007-10-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | order. The kernel used to shuffle them around to get things right, but that was recently fixed. This makes our boot loader match the behavior of most other boot loaders for the atmel parts. This bug was inherited from the Kwikbyte loader that we started from. This bug was discovered by Bj.ANvrn KNvnig back in June, but fell on the floor. He provided patches to the kernel, include backwards compatibility options that were similar to Olivier's if_ate.c commit.
* | KERNBASE should really be KERNVIRTADDR there too.cognet2007-10-241-2/+2
| | | | | | | | MFC after: 1 week
* | In ate_get_mac(), try to get the mac address in the right order, at leastcognet2007-10-241-6/+6
| | | | | | | | | | | | | | | | in the same order as it's set in ate_set_mac. I remember a discussion about this on -arm, but apparently nothing was done. Warner, is this wrong ? X-MFC After: proper review
* | Handle the case where PHYSADDR != KERNPHYSADDR (ie we do not load the kernelcognet2007-10-241-7/+11
| | | | | | | | | | | | at the beginning of the RAM). MFC After: 1 week
* | Correct a comment, this was not true anymore.cognet2007-10-241-2/+2
| |
* | First cut at support for booting a GPT labeled disk via the BIOS bootstrapjhb2007-10-2421-210/+1217
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on i386 and amd64 machines. The overall process is that /boot/pmbr lives in the PMBR (similar to /boot/mbr for MBR disks) and is responsible for locating and loading /boot/gptboot. /boot/gptboot is similar to /boot/boot except that it groks GPT rather than MBR + bsdlabel. Unlike /boot/boot, /boot/gptboot lives in its own dedicated GPT partition with a new "FreeBSD boot" type. This partition does not have a fixed size in that /boot/pmbr will load the entire partition into the lower 640k. However, it is limited in that it can only be 545k. That's still a lot better than the current 7.5k limit for boot2 on MBR. gptboot mostly acts just like boot2 in that it reads /boot.config and loads up /boot/loader. Some more details: - Include uuid_equal() and uuid_is_nil() in libstand. - Add a new 'boot' command to gpt(8) which makes a GPT disk bootable using /boot/pmbr and /boot/gptboot. Note that the disk must have some free space for the boot partition. - This required exposing the backend of the 'add' function as a gpt_add_part() function to the rest of gpt(8). 'boot' uses this to create a boot partition if needed. - Don't cripple cgbase() in the UFS boot code for /boot/gptboot so that it can handle a filesystem > 1.5 TB. - /boot/gptboot has a simple loader (gptldr) that doesn't do any I/O unlike boot1 since /boot/pmbr loads all of gptboot up front. The C portion of gptboot (gptboot.c) has been repocopied from boot2.c. The primary changes are to parse the GPT to find a root filesystem and to use 64-bit disk addresses. Currently gptboot assumes that the first UFS partition on the disk is the / filesystem, but this algorithm will likely be improved in the future. - Teach the biosdisk driver in /boot/loader to understand GPT tables. GPT partitions are identified as 'disk0pX:' (e.g. disk0p2:) which is similar to the /dev names the kernel uses (e.g. /dev/ad0p2). - Add a new "freebsd-boot" alias to g_part() for the new boot UUID. MFC after: 1 month Discussed with: marcel (some things might still change, but am committing what I have so far)
* | Update copyright attribution.jhb2007-10-242-2/+4
| | | | | | | | MFC after: 3 days
* | Properly drop the pf mutex around all copyout (consistency still protectedmlaier2007-10-242-1/+9
| | | | | | | | | | | | | | by the sx) and avoid a WITNESS panic. Overlooked during last import. Reported and tested by: Max N. Boyarov MFC after: 3 days
* | Add ABI backwards compatibility to the FreeBSD 4/5/6 versions ofmarius2007-10-244-53/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | the PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was broken with the introduction of PCI domain support. As the size of struct pci_conf_io wasn't changed with that commit, this unfortunately requires the ABI of PCIOCGETCONF to be broken again in order to be able to provide backwards compatibility to the old version of that IOCTL. Requested by: imp Discussed with: re (kensmith) Reviewed by: PCI maintainers (imp, jhb) MFC after: 5 days
* | silence complaint about not loading the wlan_scan_monitor module;sam2007-10-241-1/+2
| | | | | | | | | | | | | | | | it does not exist and is not needed as monitor mode operation has always required setting the current channel Reviewed by: thompsa MFC after: 1 week
* | Merge first in a series of TrustedBSD MAC Framework KPI changesrwatson2007-10-24103-3518/+3601
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from Mac OS X Leopard--rationalize naming for entry points to the following general forms: mac_<object>_<method/action> mac_<object>_check_<method/action> The previous naming scheme was inconsistent and mostly reversed from the new scheme. Also, make object types more consistent and remove spaces from object types that contain multiple parts ("posix_sem" -> "posixsem") to make mechanical parsing easier. Introduce a new "netinet" object type for certain IPv4/IPv6-related methods. Also simplify, slightly, some entry point names. All MAC policy modules will need to be recompiled, and modules not updates as part of this commit will need to be modified to conform to the new KPI. Sponsored by: SPARTA (original patches against Mac OS X) Obtained from: TrustedBSD Project, Apple Computer
* | Rework the read/write support in the bios disk driver some to cut downjhb2007-10-241-196/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on duplicated code and support 64-bit LBAs for GPT. - The code to manage an EDD or C/H/S I/O request are now in their own routines. The EDD routine now handles a full 64-bit LBA instead of truncating LBAs to the lower 32-bits. (MBRs and BSD labels only have 32-bit LBAs anyway, so the only LBAs ever passed down were 32-bit). - All of the bounce buffer and retry logic duplicated in bd_read() and bd_write() are merged into a single bd_io() routine that takes an extra direction argument. bd_read() and bd_write() are now simple wrappers around bd_io(). - If a disk supports EDD then always use it rather than only using it if the cylinder is > 1023. Other parts of the boot code already do something similar to this. Also, GPT just uses LBAs, so for a GPT disk it's probably best to ignore C/H/S completely. Always using EDD when it is supported by a disk is an easy way to accomplish this. MFC after: 1 week
* | MFi386: revision 1.50nyan2007-10-241-39/+30
| | | | | | | | Reindent the read/write code of bd_realstrategy() so it is more readable.
* | MFi386: revision 1.41nyan2007-10-241-2/+1
| | | | | | | | | | | | | | Slightly cleanup the 'bootdev' concept on x86 by changing the various macros to treat the 'slice' field as a real part of the bootdev instead of as hack that spans two other fields (adaptor (sic) and controller) that are not used in any modern FreeBSD boot code.
* | Reindent the read/write code of bd_realstrategy() so it is more readable.jhb2007-10-241-39/+30
| | | | | | | | MFC after: 1 week
* | Slightly cleanup the 'bootdev' concept on x86 by changing the variousjhb2007-10-249-29/+16
| | | | | | | | | | | | | | | | macros to treat the 'slice' field as a real part of the bootdev instead of as hack that spans two other fields (adaptor (sic) and controller) that are not used in any modern FreeBSD boot code. MFC after: 1 week
* | Fix reading of files that use pax 'size' attribute to store size.kientzle2007-10-241-7/+21
| | | | | | | | | | | | | | In particular, bsdtar uses the pax 'size' attribute for any file over 8G. MFC after: 3 days
* | Stop disabling USB in the PAE kernel config. The USB code has beenjhb2007-10-241-21/+0
| | | | | | | | | | | | | | using bus_dma(9) for quite a while now and has been used on 64-bit archs as well. MFC after: 1 month
* | When processing multi-path ip6 routers, place each router entry on itscsjp2007-10-241-0/+2
| | | | | | | | | | | | | | | | | | | | own line. We made this change in traceroute(8) some time ago. This is particularly useful when you are not resolving hostnames since ip6 addresses can be quite long, and lines wrap fairly easily in the multi-path router case. Discussed with: bz MFC after: 1 month
* | Move where we audit the PID argument such that we unconditionallycsjp2007-10-241-1/+1
| | | | | | | | | | | | | | | | | | audit it at the beginning of the syscall. This fixes a problem where the user supplies an invalid process ID which is > 0 which results in the PID argument not being audited. Obtained from: TrustedBSD Project MFC after: 1 week
* | Use extended process token. The in kernel process auditcsjp2007-10-241-2/+2
| | | | | | | | | | | | | | | | | | | | state is stored in an extended subject token now. Make sure that we are using the extended data. This fixes the termID for process tokens. Obtained from: TrustedBSD Project Discussed with: rwatson MFC after: 1 week
* | Take out the single-threading code in fork.julian2007-10-231-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After discussions with jeff, alc, (various Ironport people), david Xu, and mostly Alfred (who found the problem) it has been demonstrated that this is not needed for our implementations of threads and represents a real (as in we've seen it happen a lot) deadlock danger. Several points: Since forking multiple threads is not allowed, and posix states that any mutexes owned by othre threads wilol be owned in the child by phantom threads, and therads shouldn't ba accessing shared structures without protection, It can be proved that if this leads to the child process accessing inconsistent data, it's a programming error. The mode of thread_single() being used in fork() is the wrong one. It is using SINGLE_NO_EXIT when it should be using SINGLE_BOUNDARY. Even if this we used, System processes have no need to do it as they have no userland to get inconsistent. This commmit first fixes the above bugs to get tehm correct in CVS. then removes them with #ifdef. This is so that history contains the corrected version should it be needed in the future. This code may be needed if we implement the forkall() syscall from Solaris. It may be needed for other non-posix thread libraries at some time in the future, so let the code sit for a short while while I do some work on it anyhow. This removes a reproducible lockup in NFS. It may be argued that maybe doing a fork while holding a vnode lock may not be the best idea in th efirst place but it shouldn't cause a deadlock. The removal has been running under soak test for several days now. This removal should be seriously considered for 7.0 and RELENG_6. Note. There is code in the core-dumping code that may have a similar problem with coredumping threaded processes MFC After: 4 days
* | Back out 2nd part of wrong iswascii() change in prev. commit.ache2007-10-231-1/+1
| |
* | Bump MAC_VERSION to 4 and add an 8.x line in the version table. Version 4rwatson2007-10-231-1/+2
| | | | | | | | | | | | | | will include significant synchronization to the Mac OS X Leopard version of the MAC Framework. Obtained from: TrustedBSD Project
* | Forced commit to note that rev.1.179 has the following fixes in addition tobde2007-10-230-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the ones mentioned in its log message: For mount-update from rw to ro: - don't misuse the MNT_FORCE flag to break error handling for mark volume to clean. - mark volume back to dirty if g_access() failed (not just if mark volume to clean failed). - clear pm_fmod on success. pm_fmod is bogus, since it is only used to cause a panic in unreachable code when we forgot to clear it here, but something like it will be needed. For mount-update from rw to ro and from ro to rw: - don't forget to lock mp when changing mp->mnt_flag. Giant locking may make this unnecessary, but it is simpler to copy what ffs does. Most of the style changes are near here, to copy ffs's cleaner code. For unmount: - don't misuse the MNT_FORCE flag to break error handling for mark volume to clean. Failure of markvoldirty() is similar to failure of ffs_subupdate() in ffs, and ffs has never used MNT_FORCE to ignore the corresponding error. MNT_FORCE for unmount _should_ force the unmount to succeed, but forcing away of write errors has never been supported. - explicitly return 0 instead of `error' in msdosfs_unmount() after committing to success. This is now just a style fix. With errors from markvoldirty() ignored in the MNT_FORCE case, any error in markvoldirty() caused a nonzero `error' to be returned despite committing to success. Upper layers soon paniced trying to back out of the committed unmount. This bug used to be present in another form in most file systems. VOP_CLOSE() was called after committing to success, so it was necessary to force the VOP_CLOSE() to succeed. This was not done; instead, VOP_CLOSE()'s error code was returned to upper layers so upper layers soon paniced if VOP_CLOSE() failed. I saw this panic only with a buggy device driver with a missing close method, but VOP_CLOSE() can easily fail in theory, with errors like EDQUOT and EIO for unwriteable output. Now the bug has moved. g_vfs_close() is called instead of VOP_CLOSE(), and it returns void so unmount vops cannot even detect errors in it. Hopefully, errors in it only occur when there are other bugs. E.g., with the MNT_FORCE bug in msdosfs_close(), when markvoldirty() in umount failed due to the bugs in mount-update, and when this was the only write error, g_vfs_close() was reached despite the write error being detected earlier; it found one unwriteable buffer which it can only report via printf; then after fixing the panic, umount(2) "succeeded" but the unwriteable buffer was left in the buffer cache and/or VMIO object to spam the console with printfs about failed write attempts, until the next rw mount when the write succeeds, possibly clobbering different media.
* | Avoid leaking file descriptorsmatteo2007-10-231-3/+7
| |
* | - Use pci_enable_busmaster() to turn on busmaster.kevlo2007-10-231-35/+10
| | | | | | | | | | | | | | - Don't test memory/port status and emit an error message; the PCI bus will do this. Reviewed by: sam
* | Cut over to ULE on PowerPCgrehan2007-10-237-8/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | kern/sched_ule.c - Add __powerpc__ to the list of supported architectures powerpc/conf/GENERIC - Swap SCHED_4BSD with SCHED_ULE powerpc/powerpc/genassym.c - Export TD_LOCK field of thread struct powerpc/powerpc/swtch.S - Handle new 3rd parameter to cpu_switch() by updating the old thread's lock. Note: uniprocessor-only, will require modification for MP support. powerpc/powerpc/vm_machdep.c - Set 3rd param of cpu_switch to mutex of old thread's lock, making the call a no-op. Reviewed by: marcel, jeffr (slightly older version)
* | Add a BUGS section to note that mount/chroot changes sincejb2007-10-221-0/+4
| | | | | | | | | | | | | | | | | | a module was loaded might make the pathname inaccurate. I wonder if an inode reference should be stored with the pathname to allow a validity check? Suggested by: rwatson@
OpenPOWER on IntegriCloud