summaryrefslogtreecommitdiffstats
path: root/sys/gnu
Commit message (Collapse)AuthorAgeFilesLines
* Use TAILQ macros for clean/dirty block list processing. Set b_xflagspeter1998-10-316-14/+12
| | | | rather than abusing the list next pointer with a magic number.
* error return assignment was less than ideal. Fix the part that causedpeter1998-10-292-4/+4
| | | | | warnings to be the same as the ffs code. Previously, any error from the UFS_UPDATE() call was lost (I think).
* Use vtruncbuf() to clean out cached blocks on a file shorten rather thanpeter1998-10-292-6/+8
| | | | | the more expensive vinvalbuf(), based on the FFS version of the same routine. I don't have any ext2fs filesystems to test this on.
* Oops, the redundant tests for major numbers weren't redundant here.bde1998-10-272-4/+6
| | | | | | | They checked for the magic major number for the "device" behind mfs mount points. Use a more obvious check for this device. Debugged by: Andrew Gallatin <gallatin@cs.duke.edu>
* Removed redundant bitrotted checks for major numbers instead of updatingbde1998-10-262-8/+4
| | | | them.
* Don't follow null bdevsw pointers. The `major(dev) < nblkdev' test rottedbde1998-10-252-2/+4
| | | | | when bdevsw[] became sparse. We still depend on magic to avoid having to check that (v_rdev) device numbers in vnodes are not NODEV.
* Initialize earlier (ie: before npx) in case it makes any difference.peter1998-10-181-4/+8
| | | | | Print a message when it attaches to pmath_emulate if bootverbose so that we can be sure it's online.
* OOPS!peter1998-10-181-2/+2
| | | | | | Supply the moduledata handle rather than the event dispatcher function. This should explain the panic on boot problem that's been discussed in -current at the moment. Both machines had GNU_MATH_EMULATE.
* *gulp*. Jordan specifically OK'ed this..peter1998-10-161-9/+29
| | | | | | | | This is the bulk of the support for doing kld modules. Two linker_sets were replaced by SYSINIT()'s. VFS's and exec handlers are self registered. kld is now a superset of lkm. I have converted most of them, they will follow as a seperate commit as samples. This all still works as a static a.out kernel using LKM's.
* Fixed bloatage of `struct inode'. We used 5 "spare" fields for ext2fs,bde1998-10-138-16/+16
| | | | | | | | | | | | | | but when i_effnlink was added to support soft updates, there was only room for 4 spares. The number of spares was not reduced, so the inode size became 260 (on i386's), or 512 after rounding up by malloc(). Use one spare field in `struct dinode' instead of the 5th spare field in the inode and reduced to 4 spares in the inode so that the size is 256 again. Changed the types of the spares in the inode from int to u_int32_t so that the inode size has more chance of being <= 256 under other arches, and downdated ext2fs to match (it was broken to use ints before rev.1.1).
* Quick fix for not being able to sync all the buffers in boot() ifbde1998-10-034-16/+20
| | | | | | | | | | | | | an ext2fs file system is mounted. The soft update changes added a check for B_DELWRI buffers. This exposed the complete brokenness of the previous quick fix for failing syncs (PR 3571, committed on 1997/08/04). Use a new buffer flag B_DIRTY and don't abuse B_DELWRI. B_DIRTY buffers are still written too late, as broken in the previous fix. This is fairly harmless, because B_DIRTY is only used for bitmap buffers and fsck.ext2 can fix up the bitmaps perfectly. Fixed a race in ULCK_BUF() (bremfree() was outside of the splbio() section).
* Fixed initialization of new inodes. ext2fs doesn't clear inodes whenbde1998-09-292-2/+6
| | | | | | they are deleted, so inodes must be cleared when they are reused, but we didn't clear the indirect blocks. This caused serious filesystem corruption.
* Updated ext2_reload() and ext2_sync(). Locking was broken, and MNT_LAZYbde1998-09-262-84/+126
| | | | | | | | | syncs weren't optimized properly (they probably still aren't, but are bug for bug compatible with ffs). These fixes are mostly academic, since ext2fs is too broken to mount read-write (it apparently doesn't clear indirect blocks). Obtained from: mostly from Lite2
* Fixed missing newlines in messages in ext2_check_descriptors().bde1998-09-262-16/+24
| | | | | | | Fixed vnode and memory leaks after an unlikely (?) error in ext2_mountfs(). Fixed an unconditional memory leak in ext2_unmount().
* Fixed clean flag handling:bde1998-09-264-20/+72
| | | | | | | | | | | | | | | | | | | | | | | Fixes for bugs not shared with ffs: - don't mount unclean filesystems rw unless forced to. - accept EXT2_ERROR_FS (treat it like !EXT2_VALID_FS). We still don't set this or honour the maximal mount count. - don't attempt to print the name of the mount point when mounting an unclean file system, since the name of the previous mount point is unknown and the name of the current mount point is still "". Fixes for bugs shared with ffs until recently: - don't set the clean flag on unmount of an initially-unclean filesystem that was (forcibly) mounted rw. - set the clean flag on rw -> ro update of a mounted initially-clean filesystem. - fixed some style bugs (mostly long lines). The fixes are slightly simpler than for ffs, because the relevant on-disk state is not a simple boolean variable, and the superblock has a core-only extension. Obtained from: parts from ffs_vfsops.c, parts from NetBSD
* Fixed the usual missing permissions checks in mount(). As for cd9660,bde1998-09-092-2/+70
| | | | | | the damage was limited by the default of 0 for vfs.usermount. Obtained from: Lite2 via the -current ffs_vfsops.c
* Don't forget to initialize the inode lock. This bug causedbde1998-09-092-0/+2
| | | | | | | | | surprisingly few problems. Most fields were initialized to the correct values by bzero(), but lk_prio was 0 instead of PINOD (=8), the lk_wmsg was NULL instead of "ext2in", and lk_lockholder was 0 instead of -1. Obtained from: Lite2 via the -current ffs_vfsops.c
* Support compiling with `gcc -pedantic' (don't use hard newlines inbde1998-09-092-38/+40
| | | | (asm) string constants).
* Removed statically configured mount type numbers (MOUNT_*) and allbde1998-09-072-6/+6
| | | | | | | | | references to them. The change a couple of days ago to ignore these numbers in statically configured vfsconf structs was slightly premature because the cd9660, cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number in their vfsconf struct.
* Fixed printf format errors. Only one left in LINT on i386's.bde1998-08-242-21/+17
|
* Added D_TTY to the cdevswitch flags for all tty drivers. This is requiredbde1998-08-232-16/+18
| | | | | | | | | for the Lite2 fix for always returning EIO in dead_read(). Cleaned up the cdevswitch initializers for all tty drivers. Removed explicit calls to ttsetwater() from all (tty) drivers. ttsetwater() is now called centrally for opens, not just for parameter changes.
* Quick fix for breakage of read clustering on non-IDE drives. Readbde1998-08-182-4/+4
| | | | | | | | | | | | | | clustering is obsolescent technology so hardly anyone noticed. On a DORS 32160 SCSI drive with 4 tags, read clustering makes very little difference even for huge sequential reads. However, on a ZIP SCSI drive with 0 tags, the minimum overhead per block is about 40 msec, so very large clusters must be used to get anywhere near the maximum transfer rate. Using clusters consisting of 1 8K block reduces the transfer rate to about 250K/sec. Under msdosfs, missing read clustering is normal and a cluster size of 1 512 byte block reduces the transfer rate to about 25K/sec. Broken in: rev.1.18
* Use [u]intptr_t instead of [u_]long for casts between pointers andbde1998-08-166-22/+28
| | | | integers. Don't forget to cast to (void *) as well.
* Use offsetof() to avoid some casts from pointers to integers (of abde1998-08-151-1/+3
| | | | possibly different size).
* Remove some #if 0'd and commented-out code.brian1998-08-121-34/+2
| | | | Fix a COMPAT_43 type.
* "The releaseing of the reference and lock is not temporary and belongsmsmith1998-08-122-2/+0
| | | | | | | where it is. The reference and lock(s) are acquired just above the code in VREF() and relookup()." Submitted by: Michael Hancock <michaelh@cet.co.jp>
* Synced with dgb.c. Important changes from 1.29 (ioctl handlingbde1998-08-121-52/+27
| | | | | | | | | | | | | | was broken), 1.30 (COMPAT_43 option header was missing), 1.31 (DEVFS option header was missing), 1.33 (garbage pointers were followed in debugging code). Cosmetic changes from 1.27, 1.32, 1.36, 1.37. Of course, the DEVFS code didn't even compile. Fixed. Not tested. Forgotten by: brian This file should not exist. It is the same as dgb.c except for lots of renamed variables, about 250 lines removed, and only about 100 lines of real differences.
* Fixed printf format errors.bde1998-08-121-7/+6
| | | | This file is disgusting.
* Add Id keywordbrian1998-08-053-2/+9
|
* Add driver dgm - for the Digiboard PC/Xembrian1998-08-044-0/+7023
| | | | | Submitted by: "IBS / Andre Oppermann" <andre@pipeline.ch> DEVFS additions: brian
* Fixed printf format errors.bde1998-07-302-4/+4
|
* add anti-panic workaround from chris radek (cradek@in221.inetnebr.com)julian1998-07-302-0/+4
| | | | Not sure why this is needed but but does stop crashes.
* Fixed printf format errors.bde1998-07-116-8/+12
|
* Catch a few corner cases where FreeBSD differs enough from BSD 4.4 tojulian1998-07-082-2/+4
| | | | | confuse Soft updates.. Should solve several "dangling deps" panics.
* VOP_STRATEGY grows an (struct vnode *) argumentjulian1998-07-044-6/+6
| | | | | | as the value in b_vp is often not really what you want. (and needs to be frobbed). more cleanups will follow this. Reviewed by: Bruce Evans <bde@freebsd.org>
* Sync timestamp changes for inodes of special files to disk as latebde1998-07-034-16/+18
| | | | | | | | | | | | | | as possible (when the inode is reclaimed). Temporarily only do this if option UFS_LAZYMOD configured and softupdates aren't enabled. UFS_LAZYMOD is intentionally left out of /sys/conf/options. This is mainly to avoid almost useless disk i/o on battery powered machines. It's silly to write to disk (on the next sync or when the inode becomes inactive) just because someone hit a key or something wrote to the screen or /dev/null. PR: 5577 Previous version reviewed by: phk
* Centralized in-core inode update. Update the in-core inode directlybde1998-07-032-32/+8
| | | | | | | | in ufs_setattr() so that there is no need to pass timestamps to UFS_UPDATE() (everything else just needs the current time). Ignore the passed-in timestamps in UFS_UPDATE() and always call ufs_itimes() (was: itimes()) to do the update. The timestamps are still passed so that all the callers don't need to be changed yet.
* Fixed (?) races in mark_buffer_dirty(). We abuse the buffer cachebde1998-06-212-6/+12
| | | | | | | | | | | | | | by hacking on locked buffers without getblk()ing them, and we didn't even use splbio() to prevent biodone() changing the buffer underneath use when a write completes. I think there was no problem in practice on i386's because the operations on b_flags and numdirtybufs happen to be atomic. We still depend on biodone()'s operations on b_flags not interfering with ours. I think there is only interference for B_ERROR, and this is harmless because errors for async writes are ignored anyway. Don't use mark_buffer_dirty() except for superblock-related metadata. It was used in just one case where ordinary BSD buffering is more natural.
* Removed unused function ll_w_block(). It has always had races duebde1998-06-214-38/+0
| | | | | | | | to not using splbio(), and has rotted a little. The races were probably harmless in practice because this function was only used for superblock updates, and separate superblock updates are probably prevented from running into each other by doing part of the update synchronously.
* Removed unused includes.bde1998-06-212-4/+0
|
* Removed unused includes.bde1998-06-212-2/+0
|
* Added a missing options include.bde1998-06-212-0/+2
|
* This commit fixes various 64bit portability problems required fordfr1998-06-071-2/+2
| | | | | | | | | | FreeBSD/alpha. The most significant item is to change the command argument to ioctl functions from int to u_long. This change brings us inline with various other BSD versions. Driver writers may like to use (__FreeBSD_version == 300003) to detect this change. The prototype FreeBSD/alpha machdep will follow in a couple of days time.
* Don't use "ffs" in an ext2fs sleep message string.bde1998-05-162-6/+28
| | | | | | | | | | | Don't forget to clear the inode hash lock before returning from ext2_vget() after getnewvnode() fails. Obtained from: rev.1.24 of ffs_vfsops.c (the original patch for the getnewvnode() race). Forgotten in: rev.1.4 here. Removed a duplicate comment. Duplicated in: rev.1.4 here. Fixed the MALLOC() vs getnewvnode() race in ext2_vget(). Obtained from: rev.1.39 of ffs_vfsops.c.
* Abbreviate "ext2fs_fsync" as "e2fsyn" instead of as "extfsn" in a sleepbde1998-05-162-2/+2
| | | | message string.
* In the words of the submitter:msmith1998-05-072-44/+26
| | | | | | | | | | | | | | | | | | | --------- Make callers of namei() responsible for releasing references or locks instead of having the underlying filesystems do it. This eliminates redundancy in all terminal filesystems and makes it possible for stacked transport layers such as umapfs or nullfs to operate correctly. Quality testing was done with testvn, and lat_fs from the lmbench suite. Some NFS client testing courtesy of Patrik Kudo. vop_mknod and vop_symlink still release the returned vpp. vop_rename still releases 4 vnode arguments before it returns. These remaining cases will be corrected in the next set of patches. --------- Submitted by: Michael Hancock <michaelh@cet.co.jp>
* As described by the submitter:msmith1998-05-062-2/+0
| | | | | | | | | | | | | Reverse the VFS_VRELE patch. Reference counting of vnodes does not need to be done per-fs. I noticed this while fixing vfs layering violations. Doing reference counting in generic code is also the preference cited by John Heidemann in recent discussions with him. The implementation of alternative vnode management per-fs is still a valid requirement for some filesystems but will be revisited sometime later, most likely using a different framework. Submitted by: Michael Hancock <michaelh@cet.co.jp>
* - breakage of the warnings about pessimized i/o port types.brian1998-04-212-31/+12
| | | | | | | | | | - pessimized i/o port types. - other pessimized types. - Don't use DEBUG (causes LINT warnings). Use DGB_DEBUG instead. - commented out code. - cloned code that doesn't apply ("Smarts" is for the cy driver only). Submitted by: bde
* Correct the digiboard device names in agreementbrian1998-04-211-11/+16
| | | | with the man page (POLA).
* o Move debug stuff down a bit so that it doesn't try tobrian1998-04-211-31/+38
| | | | | | | | dereference uninitialized pointers. o Fix DEVFS permissions o Fix DEVFS minor numbers o Add initial & lock devices for cua device. o Fix permissions in line with sio.
OpenPOWER on IntegriCloud