| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
ncg * ipg calcualtion can overflow if signed types are used. Move
to uint32_t for the relevant values. Aligned with FreeBSD changes.
Also make sure newfs refuses to create an fs with more that 2^32-1
inodes. ok millert@
|
|
|
|
|
| |
find the wrong super-block for file systems with 64k block size.
ok visa@
|
|
|
|
|
|
| |
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
|
|
|
| |
resistant against memory correctup, if a corrupt filesystem is given to them.
ok krw
|
|
|
|
|
| |
delete <sys/param.h> if now possible
ok guenther
|
|
|
|
|
|
|
|
|
| |
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
|
|
|
|
| |
DEV_BSIZE. David Vasek says it still works the same on 4K-byte-sector
device. i.e. prints one value incorrectly. For which a fix should
be following soon.
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
|
| |
makes yet another utility honor DUID's
ok jsing@ miod@ deraadt@
|
|
|
|
|
|
|
| |
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
|
|
| |
and otto@.
|
|
|
|
| |
deraadt@
|
|
|
|
| |
ok thib@ millert@
|
| |
|
| |
|
|
|
|
|
| |
newfs command that can be used to make a filesystem with the
same settings. OK otto@
|
| |
|
|
|
|
|
| |
accessing FFS1 fields, okay art@, quite some testing by ckuethe@, simon@
and thib@, thanks.
|
|
|
|
| |
Various testing for a while, okay krw@
|
| |
|
| |
|
|
|
|
| |
rescinded 22 July 1999. Proofed by myself and Theo.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
millert@ ok
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD's log:
> The ffs superblock includes a 128-byte region for use by temporary
> in-core pointers to summary information. An array in this region
> (fs_csp) could overflow on filesystems with a very large number of
> cylinder groups (~16000 on i386 with 8k blocks). When this happens,
> other fields in the superblock get corrupted, and fsck refuses to
> check the filesystem.
>
> Solve this problem by replacing the fs_csp array in 'struct fs'
> with a single pointer, and add padding to keep the length of the
> 128-byte region fixed. Update the kernel and userland utilities
> to use just this single pointer.
>
> With this change, the kernel no longer makes use of the superblock
> fields 'fs_csshift' and 'fs_csmask'. Add a comment to newfs/mkfs.c
> to indicate that these fields must be calculated for compatibility
> with older kernels.
art@ ok.
|
| |
|
| |
|
|
|
|
| |
is used instead; kwesterback@home.com
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Code was derivied from observing how fsck_ffs `upgrades' to a given
level, and has been tested on recent NetBSD filesystems (reports as "3"),
SunOS ("1"), and ULTRIX ("0"). I haven't found a filesystem of level
"2" to test, but the code should detect it. Fixes [bin/1353]
|
|
|
|
| |
exist in struct fs.
|
| |
|
| |
|
| |
|
|
|