summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Correct a pair of buffer overflows in the telnet(1) command:nectar2005-03-281-6/+24
| | | | | | | | | | | | | | | | | | | | (CAN-2005-0468) A heap buffer overflow in env_opt_add() and related functions. (CAN-2005-0469) A global uninitialized data section buffer overflow in slc_add_reply() and related functions. As a result of these vulnerabilities, it may be possible for a malicious telnet server or active network attacker to cause telnet(1) to execute arbitrary code with the privileges of the user running it. Security: CAN-2005-0468, CAN-2005-0469 Security: FreeBSD-SA-05:01.telnet Security: http://www.idefense.com/application/poi/display?id=220&type=vulnerabilities Security: http://www.idefense.com/application/poi/display?id=221&type=vulnerabilities These fixes are based in part on patches Submitted by: Solar Designer <solar@openwall.com>
* - Correct the dprintf format int the _lookup routine.jeff2005-03-282-2/+2
| | | | Spotted by: pjd
* - Remove an unused variable from relookup().jeff2005-03-281-5/+2
| | | | | | | - Assert that REMOVE, CREATE, and RENAME callers have WANTPARENT or LOCKPARENT set. You can't complete any of these operations without at least a reference to the parent. Many filesystems check for this case even though it isn't possible in the current system.
* - Garbage collect an unused variable.jeff2005-03-282-9/+2
|
* - Don't panic if we can't lock a child in lookup, return an error instead.jeff2005-03-282-10/+8
| | | | | | | | - Only unlock the directory if this is a DOTDOT lookup. Previously this code could have deadlocked if there was a DOTDOT lookup with LOCKPARENT set and another thread was locking the other way up the tree. Sponsored by: Isilon Systems, Inc.
* - Remove an unused variable.jeff2005-03-281-2/+0
| | | | Sponsored by: Isilon Systems, Inc.
* - Remove unnecessary LOCKPARENT manipulation.jeff2005-03-281-20/+0
| | | | Sponsored by: Isilon Systems, Inc.
* - Rev 1.83 of kern_lock.c fixes the td_locks assert, reenable it here.jeff2005-03-281-3/+0
| | | | Sponsored by: Isilon Systems, Inc.
* - Don't bump the count twice in the LK_DRAIN case.jeff2005-03-281-2/+0
| | | | Sponsored by: Isilon Systems, Inc.
* - Fix the lockmgr flags so that external flags and internal flags arejeff2005-03-281-35/+33
| | | | | | | grouped together with room for each set to expand. This makes the external lock mask sane. Sponsored by: Isilon Systems, Inc.
* - Move code that should probably be an assert above the main body ofjeff2005-03-281-15/+14
| | | | | | | vrele so that we can decrease the indentation of the real work and make things slightly more clear. Sponsored by: Isilon Systems, Inc.
* Check that supplied facility is not bigger than LOG_NFACILITIES.glebius2005-03-281-0/+7
| | | | | PR: bin/79260 Submitted by: Shuichi KITAGUCHI
* Bump .Dd for the previous commit.brueffer2005-03-281-1/+1
|
* - Remove the now-unused LK_REENABLE flag.jeff2005-03-281-3/+1
| | | | Sponsored by: Isilon Systems, Inc.
* - nwfs_lookup() is no longer responsible for unlocking the dvp, this isjeff2005-03-281-26/+10
| | | | | | | handled in vfs_lookup.c. This code was missing PDIRUNLOCK use prior to the removal of PDIRUNLOCK in rev 1.73 of vfs_lookup.c. Sponsored by: Isilon Systems, Inc.
* - Fix the hpfs build, hpfs_hash.c was removed from the repository.jeff2005-03-281-1/+1
|
* - hpfs_lookup() is no longer responsible for unlocking the dvp, this isjeff2005-03-281-11/+6
| | | | | | | handled in vfs_lookup.c. This code was missing PDIRUNLOCK use prior to the removal of PDIRUNLOCK in rev 1.73 of vfs_lookup.c. Sponsored by: Isilon Systems, Inc.
* Fix typo - link for bsde_add_rule(3) manual page was not created.pjd2005-03-281-1/+1
| | | | MFC after: 1 week
* - ext2fs_lookup() is no longer responsible for unlocking the dvp, this isjeff2005-03-282-32/+2
| | | | | | | handled in vfs_lookup.c. This code was missing PDIRUNLOCK use prior to the removal of PDIRUNLOCK in rev 1.73 of vfs_lookup.c. Sponsored by: Isilon Systems, Inc.
* Properly return rule number.pjd2005-03-281-1/+1
| | | | | | Submitted by: Wojciech A. Koszek PR: bin/79292 MFC after: 1 week
* - UFS no longer uses PDIRUNLOCK to track the parent state. Instead, we nowjeff2005-03-281-12/+7
| | | | | | | rely on ufs to always leave the parent locked except in the ISDOTDOT case. Adjust asserts to deal with these changes. Sponsored by: Isilon Systems, Inc.
* - We no longer have to bother with PDIRUNLOCK, lookup() handles it for us.jeff2005-03-288-158/+21
| | | | Sponsored by: Isilon Systems, Inc.
* - We no longer have to bother with PDIRUNLOCK, lookup() handles it for us.jeff2005-03-281-7/+5
| | | | | | | | - In the ISDOTDOT case we have to unlock the dvp before locking the child, if this fails we must relock dvp before returning an error. This was missing before. Sponsored by: Isilon Systems, Inc.
* - We no longer have to bother with PDIRUNLOCK, lookup() handles it for us.jeff2005-03-283-146/+41
| | | | | | | | | | | - Network filesystems are written with a special idiom that checks the cache first, and may even unlock dvp before discovering that a network round-trip is required to resolve the name. I believe dvp is prevented from being recycled even in the forced unmount case by the shared lock on the mount point. If not, this code should grow checks for VI_DOOMED after it relocks dvp or it will access NULL v_data fields. Sponsored by: Isilon Systems, Inc.
* - We no longer have to bother with PDIRUNLOCK, lookup() handles it for us.jeff2005-03-281-21/+4
| | | | Sponsored by: Isilon Systems, Inc.
* - Adjust asserts in vop_lookup_post() to match the new post PDIRUNLOCKjeff2005-03-281-11/+8
| | | | | | vfs. Sponsored by: Isilon Systems, Inc.
* - Get rid of PDIRUNLOCK, instead, we fixup the lock state immediately afterjeff2005-03-281-13/+51
| | | | | | | | | | | | | calling VOP_LOOKUP(). Rather than having each filesystem check the LOCKPARENT flag, we simply check it once here and unlock as required. The only unusual case is ISDOTDOT, where we require an unlocked vnode on return. Relocking this vnode with the child locked is allowed since the child is actually its parent. - Add a few asserts for some unusual conditions that I do not believe can happen. These will later go away and turn into implementations for these conditions. Sponsored by: Isilon Systems, Inc.
* - Remove PDIRUNLOCK, it will soon be unused in every filesystems. The onlyjeff2005-03-281-1/+0
| | | | | | | | | | case where filesystems legitimately need to unlock the directory vp is in the DOTDOT case, which we can explicitly check for in lookup(). Furthermore, allowing filesystems to unlock dvp can lead to lock order reversals in lookup() when we vrele the dvp while the child is still locked. Sponsored by: Isilon Systems, Inc.
* The make_dev(9) functions no longer handle dev_ts, but struct cdevs.brueffer2005-03-281-9/+9
| | | | | | PR: 78172 Submitted by: "Wojciech A. Koszek" <dunstan@freebsd.czest.pl> MFC after: 3 days
* Note when 'stat' appeared in FreeBSD.obrien2005-03-281-1/+3
|
* Fix module build on amd64. There may be a cleaner way to do the .PATHnjl2005-03-281-0/+1
|
* You must selwakeup{,pri}() when closing a selectable object or thegreen2005-03-271-0/+1
| | | | | | | td->td_sel will get trashed and crash the system. Fix BPF's mistake in this area. MFC after: 1 day
* Clean up resources properly if acpi_perf fails to attach. First, changenjl2005-03-272-8/+20
| | | | | | acpi_bus_alloc_gas() to delete the resource it set if alloc fails. Then, change acpi_perf to delete the resource after releasing it if alloc fails. This should make probe and attach both fully restartable if either fails.
* Add powernow to kernel build target.njl2005-03-272-0/+2
|
* Hook powernow up to the build for i386 and amd64.njl2005-03-271-1/+5
|
* Add the powernow driver, which handles AMD Mobile Athlon PowerNow! (k7)njl2005-03-271-0/+928
| | | | | | | | | and AMD Cool&Quiet PowerNow! (k8) cpufreq control. This driver is enabled for both i386 and amd64 architectures. It has both acpi and legacy BIOS attachments. Thanks to Bruno Ducrot for writing this driver and Jung-uk Kim for testing. Submitted by: Bruno Ducrot (ducrot:poupinou.org)
* Serialize task queue by starting only one thread instead of three. Thisnjl2005-03-271-1/+1
| | | | | | | | may help with various interdependencies between subsystems. More testing is needed to understand what the underlying issues are here. Tested by: Juho Vuori MFC after: 2 days
* Fix AMD64 cross-builds when WITH_LIB32 is defined.ru2005-03-271-4/+4
| | | | (Initially spotted by kris@ on RELENG_5.)
* We usually say "to conform some standard" so I guess this is a typo.delphij2005-03-272-2/+2
|
* Fix copy&paste error in my previous commit.mux2005-03-271-2/+2
| | | | Spotted by: ru
* MFen: Copyright Year Updatedelphij2005-03-271-1/+2
| | | | | | - hardware/common/artheader.sgml: 1.5 -> 1.6 Obtained from: The FreeBSD Simplified Chinese Project CVS
* Unbreak style(9) breakage from last commit. We try to avoid definingimp2005-03-271-4/+2
| | | | | | variables in internal blocks. Also, go ahead and fail if we can't load the firmware. It should have failed like this, but never did (firmware loads generally don't fail).
* Sync translation with my local work. This is essentiallydelphij2005-03-271-1396/+734
| | | | | | MFen 1.761.2.11 -> 1.829. Obtained from: The FreeBSD Simplified Chinese Project CVS
* Fix a bunch of bugs I came accross when looking at the ixgb(4) driver,mux2005-03-273-41/+9
| | | | | | | | | | | | | | | | | | | | some of which are rather serious: - Use the device sysctl tree instead of rolling our own. - Don't create a bus_dmamap_t to pass to bus_dmamem_alloc(), it is bus_dmamem_alloc() that creates it itself. The DMA map created by the driver was overwritten and its memory was leaked. - Fix resource handling bugs in the error path of ixgb_dma_alloc(). - Don't use vtophys() to get the base address of the TX and RX rings when busdma already gave us the correct address to use! - Remove now useless includes and the alpha_XXX_dmamap() hack. - Don't initialize if_output to ether_output(), ether_ifattach() does it for us already. - Add proper module dependencies on ether and pci. Unfortunately, I'm not lucky enough to own an ixgb(4) card, nor a machine with a bus where to plug it in and I couldn't find anyone able to test these patches, so they are only build-tested and I won't MFC them for 5.4-RELEASE.
* Unbreak LINT.pjd2005-03-271-0/+3
|
* Don't defer the boot-time exploration of high-speed USB busses.iedowse2005-03-271-3/+9
| | | | | | | This ensures that we explore EHCI busses before their companion controllers' busses, so that ports connected to full/low speed devices will be properly routed to the companion controllers by the time the OHCI/UHCI exploration occurs.
* When PAM support was added to rexecd in revision 1.29 (just prior tonectar2005-03-271-2/+17
| | | | | | | | | | | | | | | | | | | | | 5.0-RELEASE), a visually elusive bug was introduced. A comparison operator was changed to assignment. As a result, rexecd behaved always as if the `-i' option had been specified. It would allow root logins. This commit corrects the situation in the obvious way. A separate bug was introduced at the same time. The PAM library functions are called between the invocation of getpwnam(3) and the use of the returned static object. Since many PAM library functions result in additional getpwnam(3) calls, the contents of the returned static object could be changed from under rexecd. With this commit, getpwnam_r(3) is used instead. Other PAM-using applications should be reviewed for similar errors in getpw* usage. Security: rexecd's documented default policy of disallowing root logins was not enforced. Reviewed by: cperciva
* Unstaticize config. It was being optimized away.des2005-03-271-1/+1
| | | | MFC after: 3 days
* When doing the initial open of the proc via procfs, complain if we arealfred2005-03-273-8/+14
| | | | | | unable to open the /proc/pid/mem file. Otherwise doing a truss on a nonexistant pid makes us return success even though no such process exists.
* I've been working on this somewhat so I'm moving thealfred2005-03-272-313/+329
| | | | parts I'm touching to be as style(9) compliant as I can.
OpenPOWER on IntegriCloud