Age | Commit message (Collapse) | Author |
|
random data on the disk as an inode. Thus avoiding crashes when
translating a bogus filehandle to a vnode. Yes, I'm looking at you,
NFS!
Adapted from a diff by Christos Zoulas via NetBSD, pointed out by
kurt@.
ok beck@
|
|
assumptions in fsck_ext2fs and eliminates spurious "VALUES IN SUPER
BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE" messages.
Part of the problem reported to bugs@ by Lampshade.
ok beck@
|
|
msdosfs and nfsv2 don't set f_namemax. ntfs and ext2fs don't set
f_namemeax and f_favail. fusefs doesn't set f_mntfromspec, f_favail and
f_iosize. Also, make all filesystems use copy_statfs_info(), so that all
statfs information is filled in correctly for the (sb != &mp->mnt-stat)
case.
ok stefan
|
|
logical block is contiguous to the previous one.
This logic is a left-over of the pre-bread_cluster() area. When the
read-ahead version of bread(9) was used to prefetch blocks. Nowadays
bread_cluster() do the right thing (tm).
ok stefan@
|
|
anymore since the kernel VM space increase work done in sparc about one
year ago.
from Miod Vallat; thanks!
ok tobiasu
|
|
could end up in an inconsistent state. The fstype dependent
mp->mnt_data was NULL, but the general mp was still listed as a
valid mount point. Next access to the file system would crash with
a NULL pointer dereference.
If closing the device fails, the mount point must go away anyway.
There is nothing we can do about it. Remove the workaround for the
EIO error in the general unmount code, but do not generate any error
in the file system specific unmount functions.
OK natano@ beck@
|
|
ok millert
|
|
torture tested on amd64, i386 and macppc
ok beck mpi stefan
"the change looks right" deraadt
|
|
OK krw@ natano@ as part of a larger diff
|
|
ok beck@ deraadt@
|
|
|
|
The concept of differentiating between "short" and "long" symlinks is
specific to ufs/, so it shouldn't creep into the generic fs layer.
Inspired by a similar commit to NetBSD.
While there replace all references to mnt_maxsymlinklen in ufs/ext2fs
with EXT2_MAXSYMLINKLEN, which is the constant max short symlink len for
ext2fs. This allows to get rid of some (mnt_maxsymlinklen == 0) checks
there, which is always false for ext2fs.
input and ok stefan@
ok millert@
|
|
This allows to remove some truncating casts in symlink handling code.
Also, validate fs_maxsymlinklen in the superblock at mount time and on
fsck to make sure we don't use bogus data.
discussion & ok millert@, stefan@
|
|
|
|
Reported and fixed by Martin Natano <natano at natano ! net>, thanks!
ok stefan
|
|
They are defined to 0 since the import of ext2fs 19 years ago.
|
|
Cluster read is unconditionnally enabled for FFS since some years and
toggling "doclusterread" has no effect.
OpenBSD no longer support write clustering since the Dynamic Buffer
Cache went in, so there is reason to delay the call to bawrite(9).
Tested by Mathieu, ok dlg@
|
|
|
|
ok mpi@
|
|
(others require more care)
|
|
|
|
atime and mtime are UTIME_OMIT (at least for ufs, tmpfs, and ext2fs), and
to correctly handle a timestamp of -1.
ok millert@
|
|
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.
ok tedu@ deraadt@
|
|
- rename uiomove() to uiomovei() and update all its users.
- introduce uiomove(), which is similar to uiomovei() but with a size_t.
- rewrite uiomovei() as an uiomove() wrapper.
ok kettenis@
|
|
used in disklabel type tools, newfs, fsck, when related to ufs or
ufs-derived filesystems, but also in a struct. Those things always include
<ufs/ffs/fs.h>. Move it there
ok guenther, tested in ports by sthen
|
|
|
|
|
|
architectures.
|
|
that these don't need to support interrupts
|
|
ok dlg@ mpi@ bcook@ millert@ miod@
|
|
|
|
|
|
adapted from a freebsd commit by david hill
|
|
|
|
ok deraadt@ tedu@
|
|
to include that than rdnvar.h. ok deraadt dlg
|
|
ok tedu@
|
|
|
|
ok millert@
|
|
type, and path shouldn't leak vnode or ucred references.
ok millert@
|
|
ok mpi@ kspillner@
|
|
Damn those memcpy-wrapping macros!
"do it" deraadt
|
|
Reported by Roman Yakovlev, thanks!
"do it now" deraadt
|
|
Because ext2fs has only 32-bit inode numbers, use ufsino_t as in FFS.
Disk blocks are u_int32_t as well, because we don't support the 64BIT flag.
When we do, there's going to be a lot more going on than just daddr_t.
While there, add some journaling-related bits into the superblock to play with.
ok guenther
|
|
moment and now is not the time. hitting these in here causes chaos.
We need to do these, but at a better time than right after a hackathon
and before release.
ok guenther@
|
|
|
|
|
|
The reason being that ext2 structures are little-endian but JBD2 journal
is big-endian. Don't confuse readers by talking about "file system endian".
Some KNF while there.
ok guenther
|
|
|
|
Tested on amd64 with > 4GB files and 50,000 subdirectories.
From FreeBSD, thanks!
ok deraadt guenther
|