History log of /openbsd-src/sys/ufs/ext2fs/ext2fs_readwrite.c (Results 1 – 25 of 46)
Revision Date Author Comments
# 5b133f3f 08-Mar-2023 guenther <guenther@openbsd.org>

Delete obsolete /* ARGSUSED */ lint comments.

ok miod@ millert@


# f62e8f74 27-Nov-2019 beck <beck@openbsd.org>

Re-enable IO_NOCACHE, and use is in vnd.

Ensure that io to a file backing a vnd is IO_SYNC, so IO to a
vnd device is both synchronous and not cached in the buffer cache.

This allows the "mount" reg

Re-enable IO_NOCACHE, and use is in vnd.

Ensure that io to a file backing a vnd is IO_SYNC, so IO to a
vnd device is both synchronous and not cached in the buffer cache.

This allows the "mount" regress to work repeatably, and avoids
a situation where when the buffer cache cleaner runs to clear
dirty buffers while people are waiting, it actually increases the
dirty buffers when the writes to the underlying vnd are also
delayed.

ok bluhm@

show more ...


# ad4c60c0 13-Jan-2018 millert <millert@openbsd.org>

In ext2fs_write(), clear the buffer on uiomove() failure unless it
was cleared on alloc just like we do in ffs_write().


# 392d10d7 08-Jan-2018 millert <millert@openbsd.org>

Pass correct size to uvm_vnp_setsize() for large files.


# b78c6981 08-Jan-2018 millert <millert@openbsd.org>

Add kqueue support for ext2fs based on ffs. OK deraadt@


# 98edb555 30-Dec-2017 guenther <guenther@openbsd.org>

Delete unnecessary <sys/file.h> includes

ok millert@ krw@


# 13f30d2f 01-Mar-2016 natano <natano@openbsd.org>

*** empty log message ***


# 3484f39e 27-Feb-2016 natano <natano@openbsd.org>

Move mnt_maxsymlink from struct mount to struct ufsmount.

The concept of differentiating between "short" and "long" symlinks is
specific to ufs/, so it shouldn't creep into the generic fs layer.
Ins

Move mnt_maxsymlink from struct mount to struct ufsmount.

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@

show more ...


# 6006db0b 26-Feb-2016 natano <natano@openbsd.org>

Convert mnt_maxsymlinklen to unsigned.

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

Convert mnt_maxsymlinklen to unsigned.

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@

show more ...


# dc30eddb 16-Feb-2016 stefan <stefan@openbsd.org>

Convert to uiomove. From Martin Natano.


# cfc6a9ed 12-Jan-2016 mpi <mpi@openbsd.org>

Kill the "doclusterread" and "doclusterwrite" defines.

They are defined to 0 since the import of ext2fs 19 years ago.


# 21dab745 14-Mar-2015 jsg <jsg@openbsd.org>

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@


# 081bf720 10-Feb-2015 miod <miod@openbsd.org>

First step towards making uiomove() take a size_t size argument:
- rename uiomove() to uiomovei() and update all its users.
- introduce uiomove(), which is similar to uiomovei() but with a size_t.
-

First step towards making uiomove() take a size_t size argument:
- 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@

show more ...


# 7f58a11f 14-Sep-2014 jsg <jsg@openbsd.org>

remove uneeded proc.h includes
ok mpi@ kspillner@


# ea0c9824 13-Jul-2014 pelikan <pelikan@openbsd.org>

ext4 (extents) read support

Tested on amd64 with > 4GB files and 50,000 subdirectories.
From FreeBSD, thanks!

ok deraadt guenther


# 1217b0a4 11-Jul-2014 pelikan <pelikan@openbsd.org>

split ext2fs_read for the upcoming ext4 extent bits, like FreeBSD has done

ok guenther


# c7fd3f62 11-Jul-2014 pelikan <pelikan@openbsd.org>

determine and use maximum file size instead of magical constants

ok guenther


# 728d3a0e 09-May-2014 tedu <tedu@openbsd.org>

disable IO_NOCACHE B_NOCACHE conversion until it works.


# e1405772 08-Apr-2014 beck <beck@openbsd.org>

add IO_NOCACHE flag to vop_write arguments, which in turn sets B_NOCACHE
on the written buffers. Use the flag for writes from the page daemon to
ensure that we free buffers written out by the page da

add IO_NOCACHE flag to vop_write arguments, which in turn sets B_NOCACHE
on the written buffers. Use the flag for writes from the page daemon to
ensure that we free buffers written out by the page daemon rather than
caching them.
ok kettenis@

show more ...


# d4fc1c49 25-Jan-2014 guenther <guenther@openbsd.org>

ufs_setattr() was assuming that the flag bits that indicate
atime/mtime/ctime need to be updated weren't already set. When
they are, the code will end up treating the VNOVAL value from the
VFS layer

ufs_setattr() was assuming that the flag bits that indicate
atime/mtime/ctime need to be updated weren't already set. When
they are, the code will end up treating the VNOVAL value from the
VFS layer as a time_t. Port the fix from FreeBSD: the critical bit
is to process the existing flag values before possibly setting them
again in ufs_setattr(). This diff pulls in a larger change from
FreeBSD to replace the macro ITIMES() with a function ufs_itimes()
and to remove the atime and mtime arguments from ffs_update(): only
ufs_setattr() used them so it makes more sense to just do the those
bits directly there.

tweaks and ok tedu@ matthew@

show more ...


# 906c107f 14-Sep-2013 guenther <guenther@openbsd.org>

Correct the handling of I/O of >=2^32 bytes and the ktracing there of
by using size_t/ssize_t instead of int/u_int to handle I/O lengths in
uiomove(), vn_fsizechk(), and ktrgenio(). Eliminate the al

Correct the handling of I/O of >=2^32 bytes and the ktracing there of
by using size_t/ssize_t instead of int/u_int to handle I/O lengths in
uiomove(), vn_fsizechk(), and ktrgenio(). Eliminate the always-zero
'error' argument to ktrgenio() at the same time.

show more ...


# 1abdbfde 11-Jun-2013 deraadt <deraadt@openbsd.org>

final removal of daddr64_t. daddr_t has been 64 bit for a long enough
test period; i think 3 years ago the last bugs fell out.
ok otto beck others


# 543c93a8 11-Jul-2012 guenther <guenther@openbsd.org>

If the current offset is strictly less than the process filesize
rlimit, then a write that would take it over the limit should be
clamped, making it a partial write.

ok beck@


# 93f62a9e 04-Jul-2011 tedu <tedu@openbsd.org>

bread does nothing with its ucred argument. remove it. ok matthew


# 5f64cd9c 17-Jun-2007 jasper <jasper@openbsd.org>

ansify/de-register.
no binary change


12