summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
...
* A bogus check for a char device also matched symbolic links.paul2001-04-251-1/+1
| | | | | | Replace it with a correct check using S_ISCHR() Symbolic links will now work again in linux compatibility.
* Don't install KO's with the "schg" flag.obrien2001-04-256-46/+11
| | | | | | | We are way too inconsistent with our setting of the "schg" flag, and in our default install, it doesn't really offer any additional security. Reviewed by: arch@
* Fix SCM ID's and remove tailing blanks.obrien2001-04-258-27/+24
|
* - Make the dumping of console messages from the secondary CPU's to thejhb2001-04-251-3/+5
| | | | | kernel console be #ifdef DIAGNOSTIC. - Don't set ktr_mask in release_aps().
* alpha_fpstate_save is fairly expensive (critical enter/exit, possiblygallatin2001-04-251-0/+2
| | | | | | | saves 32 registers) to do on every context switch. This is only required for SMP, so only do it there. We should also look at moving the critical enter/exit out to the callers
* MFffs ffs_balloc.c 1.5.bde2001-04-252-0/+4
| | | | | | | | | | | | | | | | | Long ago, bread() set b_blkno to the disk block number as a side effect of doing physical i/o (or it just retained the setting from when the i/o was done). The setting is lost when buffers go away and then are reconsituted from VM. bread() originally compensated by doing a VOP_BMAP() to recover b_blkno, but this was no good since it sometimes caused extra i/o or even deadlock for bread()ing metadata to do the bmap. This was fixed in vfs_bio.c 1.33 (1995/03/03) and ffs_balloc.c 1.5, etc., by removing the VOP_BMAP() from bread() and breadn(), and changing all (?) places that used b_blkno to set it if necessary. ext2fs was not imported until later in 1995 and was still depending on the old behaviour of bread() in at least ext2_balloc(). This caused filesystem and file corruption by clobbering direct block numbers in inodes.
* Do not leave a process with no credential in zombproc.tanimura2001-04-251-17/+14
| | | | Reviewed by: jhb
* When closing the last reference to an unlinked file, it is freedmckusick2001-04-254-26/+113
| | | | | | | | | | | | | | | by the inactive routine. Because the freeing causes the filesystem to be modified, the close must be held up during periods when the filesystem is suspended. For snapshots to be consistent across crashes, they must write blocks that they copy and claim those written blocks in their on-disk block pointers before the old blocks that they referenced can be allowed to be written. Close a loophole that allowed unwritten blocks to be skipped when doing ffs_sync with a request to wait for all I/O activity to be completed.
* Move the netexport structure from the fs-specific mountstructurephk2001-04-2528-226/+174
| | | | | | | | | | | | | | to struct mount. This makes the "struct netexport *" paramter to the vfs_export and vfs_checkexport interface unneeded. Consequently that all non-stacking filesystems can use vfs_stdcheckexp(). At the same time, make it a pointer to a struct netexport in struct mount, so that we can remove the bogus AF_MAX and #include <net/radix.h> from <sys/mount.h>
* Ignore chflags errors. This makes installing to nfs mounted targetimp2001-04-255-10/+10
| | | | directories work.
* o Separate acl_t into internal and external representations asjedgar2001-04-241-3/+10
| | | | | | | | | | | required by POSIX.1e. This maintains the current 'struct acl' in the kernel while providing the generic external acl_t interface required to complete the ACL editing library. o Add the acl_get_entry() function. o Convert the existing ACL utilities, getfacl and setfacl, to fully make use of the ACL editing library. Obtained from: TrustedBSD Project
* get the parameters to pci_write_config the right way round. this may fixcg2001-04-241-2/+2
| | | | some non-functional cards/machines
* Add a new field 'md_kernnest' to the alpha machine dependent processjhb2001-04-247-15/+72
| | | | | | | | | | | | | | | | | | | | | structure. This field keeps track of how many levels deep we are nested into the kernel. The nesting level is bumped at the start of a trap, interrupt, syscall, or exception and is decremented on return. This is used to detect the case when the kernel is returning back to a kernel context in exception_return(). If we are returning to the kernel we need to update the globaldata pointer register saved in the stack frame in case we have switched CPU's between taking the initial interrupt that saved the frame and returning. If we don't do this fixup it is possible for a CPU to use the wrong per-cpu data. On UP systems this is not a problem, so the code is conditional on SMP. A count was used instead of simply checking the process status register in the frame during exception_return() since there are critical sections at the very start and end of a trap, exception, or interrupt from userland in which we could trash the t7 register being used in userland. The counter is incremented after adn before these critical sections respectively so that we will not overwrite the saved t7 register if we are interrupted during one of these critical sections.
* Change uipc_sockaddr so that a sockaddr_un without a path is returnedtmm2001-04-241-0/+2
| | | | | | | | | nam for an unbound socket instead of leaving nam untouched in that case. This way, the getsockname() output can be used to determine the address family of such sockets (AF_LOCAL). Reviewed by: iedowse Approved by: rwatson
* o Change a suser() call to a suser_xxx(..., PRISON_ROOT) call in therwatson2001-04-241-1/+1
| | | | | | | | | | linuxulator so as to allow privileged processes within a jail() to invoke the Linux initgroups() system call. This allows the Linux "su" to work properly (better) when running a complete Linux environment under jail(). This problem was reported by Attila Nagy <bra@fsn.hu>. Reviewed by: marcel
* When switching backing store during signal delivery, do the switch beforedfr2001-04-242-14/+16
| | | | | | creating the register frame for calling the handler. Also discard that frame before switching back to the old backing store after the handler returns.
* Align stack pointer and backing store pointer to 16 byte boundary whendfr2001-04-241-0/+5
| | | | delivering signals.
* Don't trash the user's pr on syscalls.dfr2001-04-242-2/+4
|
* Revert previous delta, which was completely bogus.sheldonh2001-04-241-1/+1
| | | | The perceived problem was the symptom of a local error.
* Disconnect linux from the build. The buildkernel target has beensheldonh2001-04-241-1/+1
| | | | | breaking on linux for more than two days because sys_exit_args referenced in linux_sysent.c does not exist.
* Change the pfind() and zpfind() functions to lock the process that theyjhb2001-04-2435-285/+385
| | | | | | find before releasing the allproc lock and returning. Reviewed by: -smp, dfr, jake
* Pre-dirpref versions of fsck may zero out the new superblock fieldsiedowse2001-04-241-0/+6
| | | | | | | | | | | fs_contigdirs, fs_avgfilesize and fs_avgfpdir. This could cause panics if these fields were zeroed while a filesystem was mounted read-only, and then remounted read-write. Add code to ffs_reload() which copies the fs_contigdirs pointer from the previous superblock, and reinitialises fs_avgf* if necessary. Reviewed by: mckusick
* Back out previous commit.grog2001-04-231-0/+4
| | | | Requested by: bde
* Fix a bug introduced in the last commit: vaccess_acl_posix1 only checkedtmm2001-04-233-3/+3
| | | | | | | the file gid gainst the egid of the accessing process for the ACL_GROUP_OBJ case, and ignored supplementary groups. Approved by: rwatson
* Add als4000 subdir.orion2001-04-231-3/+3
|
* Initial version of Avance Logic ALS4000 pcm driver.orion2001-04-235-0/+1005
|
* fix it so it compiles againmjacob2001-04-2312-0/+24
|
* fix it so it compiles again after twerpage elsewheremjacob2001-04-231-0/+2
|
* add this ridiculous include foo so it will compile againmjacob2001-04-232-0/+4
|
* Fix includes so it compiles again.mjacob2001-04-232-2/+4
|
* Correct #includes to work with fixed sys/mount.h.grog2001-04-2385-0/+169
|
* Correct #includes to work with fixed sys/mount.h.grog2001-04-2314-0/+28
|
* Remove bogus #include and duplicate definition of AF_MAX. These weregrog2001-04-231-4/+0
| | | | | | | | made necessary by breakage in usr.sbin/pstat and usr.bin/fstat, since fixed. Suggested by: phk Unearthed by: John Hood <jhood@sitaranetworks.com>
* Add address families AF_SLOW and AF_SCLUSTER. These are used by thegrog2001-04-232-3/+8
| | | | | | Sitara QoSworks box. Obtained from: Sitara Networks Inc.
* Fix the `tape drive spinning indefinately upon mt stat' problem.joerg2001-04-221-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the recent changes in the CAM error handling, some problems in the error handling of sa(4) have been uncovered. Basically, a number of conditions that are not actually errors have been mistreated as genuine errors. In particular: . Trying to read in variable length mode with a mismatched blocksize between the on-tape (virtual) blocks and the read(2) supplied buffer size, causing an ILI SCSI condition, have caused an attempt to retry the supposedly `errored' transfer, causing the tape to be read continuously until it eventually hit EOM. Since by default any simple mt(1) operation does an initial test read, an `mt stat' was sufficient to trigger this bug. Note that it's Justin's opinion that treating a NO SENSE as an EIO is another bug in CAM. I feel not authorized to fix cam_periph.c without another confirmation that i'm on the right track, however. . Hitting a filemark caused the read(2) syscall to return EIO, instead of returning a `short read'. Note that the current fix only solves this problem in variable length mode. Fixed length mode uses a different code path, and since i didn't grok all the intentions behind that handling, i did not touch it (IOW: it's still broken, and you get an EIO upon hitting a filemark). The solution is to keep track of those conditions inside saerror(), and upon completion to not call cam_periph_error() in that case. We need to make sure that the device gets unfrozen if needed though (in case of actual errors, cam_periph_error() does this on our behalf). Not objected by: mjacob (who currently doesn't have the time to review the patch)
* Removed old version of vaccess_acl_posix1e() that snuck back in rev 1.146.obrien2001-04-221-2/+0
| | | | Submitted by (with good eye): Niels Chr. Bank-Pedersen <ncbp@bank-pedersen.dk>
* Style(9) fixes:obrien2001-04-221-51/+53
| | | | | | | * get rid of space (0x20) before tab (^I) * indent with ^I, not 0x20 * continuation line for prototypes is for 0x20's past function's name col. * etc.
* add MARVELL to the list of phys to go into miibusmjacob2001-04-211-1/+1
|
* o Remove comment indicating policy permits loop-back debugging, butrwatson2001-04-211-1/+0
| | | | | | | semantics don't: in practice, both policy and semantics permit loop-back debugging operations, only it's just a subset of debugging operations (i.e., a proc can open its own /dev/mem), and that's at a higher layer.
* Block out all interrupts, even machine checks, for critical_enter()gallatin2001-04-212-1/+2
| | | | | | | This is will be required to prevent lowering the ipl when a critical_enter() is present in the interrupt path when handling a machine check. reviewed by: jhb
* Fix the cut'n'paste style bugs I introduced in rev 1.16jedgar2001-04-211-3/+3
| | | | (spaces -> tab(s) in #define's)
* Upper limit of mousechar start is UCHAR_MAX - 3, not UCHAR_MAX - 4ache2001-04-211-2/+4
| | | | | | | Restore original characters when mousechar start changes, not always 0-3 PR: 24437 Submitted by: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
* My fix to NEWCARD for getting the function type broke oldcard due toimp2001-04-211-2/+2
| | | | | | | | a name conflict. Pointed out by: markm # I had to login to freefall to make this commit, so something maybe up
* Set the device name for NEC PC98 PCMCIA Controller on boot.imp2001-04-211-18/+19
| | | | | # We really need to allocate i/o ports for it, but I need to learn # the pc98 bus space better before attempting that.
* Add accessor/ivar for the "function". This is so we can genericallyimp2001-04-212-1/+6
| | | | match disks and serial ports and maybe others.
* Avoid divide-by-zero for devices that the adapter has not negotiated amsmith2001-04-211-1/+5
| | | | transfer speed with.
* Add entry for swdog, Sitara Networks' watchdog timer.grog2001-04-211-0/+1
| | | | Submitted by: John Hood <jhood@sitaranetworks.com>
* Only try to delete the resource if we actually got it.imp2001-04-211-2/+3
|
* Spelling nit: acquring -> acquiring.jhb2001-04-211-1/+1
| | | | Reported by: T. William Wells <bill@twwells.com>
* Assert that when using an interlock mutex it is not recursed when lockmgr()alfred2001-04-201-1/+3
| | | | | | is called. Ok'd by: jhb
OpenPOWER on IntegriCloud