| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
the construct like printf("%\s", NULL) resulting from macroexpand of
ERROR(u, NULL), making it impossible to use LIBUFS_DEBUGGING.
With inline function, compiler cannot detect the NULL argument to
known function and does not try to convert it into puts().
In collaboration with: pho
|
|
|
|
| |
Submitted by: jeff
|
|
|
|
|
|
|
|
| |
brings in support for an optional intent log which eliminates the need
for background fsck on unclean shutdown.
Sponsored by: iXsystems, Yahoo!, and Juniper.
With help from: McKusick and Peter Holm
|
| |
|
| |
|
| |
|
|
|
|
|
| |
0 until it can be properly tested by those raising the warnings.
Remember: make universe is required when changing the WARNS level.
|
|
|
|
|
|
|
|
|
| |
Similar to libexec/, do the same with lib/. Make WARNS=6 the norm and
lower it when needed.
I'm setting WARNS?=0 for secure/. It seems secure/ includes the
Makefile.inc provided by lib/. I'm not going to touch that directory.
Most of the code there is contributed anyway.
|
|
|
|
|
|
|
|
|
| |
possible to
use almost anything that uses libufs(3) against a file as an unprivileged user, e.g.
tunefs(8) and dumpfs(8) against a makefs(8)-created image.
Prodded by: kensmith
|
|
|
|
|
|
|
| |
a NULL pointer.
PR: kern/94480
Submitted by: Michiel Pelt <m.pelt xs4all nl>
|
|
|
|
| |
of the disk.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
prefix) as an argument and mount point path. At the end it has to find
device name file system is stored on, which means when mount point path is
given, it tries to look into /etc/fstab and find special device
corresponding to the given mount point. This is not perfect, because it
doesn't handle the case when file system is mounted by hand and mount point
is given as an argument.
I found this problem while trying to use snapinfo(8), which passes mount
points to the ufs_disk_fillout(3) function, but I had file system mounted
manually, so snapinfo(8) was exiting with the error below:
ufs_disk_fillout: No such file or directory
I modified libufs(3) to handle those arguments (the order is important):
1. special device with /dev/ prefix
2. special device without /dev/ prefix
3. mount point listed in /etc/fstab, directory exists
4. mount point listed in /etc/fstab, directory doesn't exist
5. mount point of a file system mounted by hand
|
|
|
|
| |
Sponsored by: home.pl
|
|
|
|
|
|
|
| |
- WARNS before CFLAGS
- CFLAGS -DXXX before -IXXX
Approved by: ru
|
|
|
|
|
|
|
| |
not get documented, and what it does document isn't going to come to CVS any
time in the immediate future.
Patience of a saint: trhodes
|
|
|
|
| |
Discussed with: jmallett
|
|
|
|
| |
PR: 83820
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
header.
Sys/param.h includes sys/types.h internally unless LOCORE is
defined.
Approved by: des (mentor)
|
| |
|
| |
|
|
|
|
|
|
| |
binaries in /bin and /sbin installed in /lib. Only the versioned files
reside in /lib, the .so symlink continues to live /usr/lib so the
toolchain doesn't need to be modified.
|
|
|
|
|
|
| |
PR: bin/53515
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
Approved by: jmallett
|
|
|
|
|
| |
PR: 53149
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
|
|
|
|
|
|
| |
that this file is (these files are) in the public domain.
PR: 53149
|
|
|
|
|
|
|
|
|
|
|
| |
getino(3)/putino(3), inode.c has been reworked in Perforce to the point
where a manual page may not be accurate. Certainly putino(3) has not
even been merged back yet.
These will need a lot of improvement for most applications, but they
document the API enough to get someone on their feet, most likely. The
best documentation still exists in the form of libufs(3) consumers in the
base system.
|
|
|
|
|
| |
not know of any software using them, and there is no "published API" for
libufs, as it were.
|
|
|
|
| |
Parenthesise return values.
|
| |
|
|
|
|
|
|
|
|
|
| |
new one, and do not fall back to the RO fd. There was a bug here
in that the RO fd was never closed, if the RDRW open succeeded, but
this code is bogus anyway, and it breaks newfs of floppies, at least
for me, due to "Device busy." Anything that wants to fall back is
doing something significantly odd that it should have some more complex
code on its end.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the sorts of errors we run into[1]. This also gives us room to put in a
vaguely appropriate casts to silence warnings since our compiler doesn't like
when we compare ssize_t to size_t[2]. Add a cast in sblock.c[3] to silence
a warning because of signed vs. size_t hell (again). Clean up nearby
excessive parenthemutilation[4].
Reviewed by: bde [2] [3]
Suggested by: bde, many [1]
Submitted by: bde [4]
An aside about [4], bde notes that we do not check for a negative value for
the fs bsize. I'm nto going to do that in every situation we use it, one must
expect a reasonable program to pass down reasonable values. Some foot shooting
protection I will tolerate, some I will not. Also he suggests some possible
conditional improvements there, which I may take to heart.
PS: For me at least, this is now WARNS=5 clean...
|
| |
|
|
|
|
|
| |
Big pointy hat to: jmallett
Spotted by: peter
|
| |
|
|
|
|
|
|
|
| |
get it from the fs structure. Really libufs should have interfaces to generate
both what we export, and what we import, based on eachother, and this should
be full of redundant code to make sure everything is right... But really, we
don't even deal with checksums, so plenty of room to improve.
|
| |
|
| |
|
|
|
|
|
| |
to be read in) but also the last cylinder group in the series (i.e. what is
stored in the structure).
|
|
|
|
|
| |
size (dumpfs may try to read the cylinder size (or is is sector size?) by way
of bread). Prevents a bounds error.
|
| |
|
|
|
|
| |
Concept reviewed by: phk
|
| |
|
|
|
|
|
| |
DEBUG and d_error initialisation into an ERROR macro, which can both trace and
set the d_error field. Much a more meaningful thing, I should say.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the old 8-bit fs_old_flags to the new location the first time that the
filesystem is mounted by a new kernel. One of the unused flags in
fs_old_flags is used to indicate that the flags have been moved.
Leave the fs_old_flags word intact so that it will work properly if
used on an old kernel.
Change the fs_sblockloc superblock location field to be in units
of bytes instead of in units of filesystem fragments. The old units
did not work properly when the fragment size exceeeded the superblock
size (8192). Update old fs_sblockloc values at the same time that
the flags are moved.
Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk>
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
|
|
| |
superblock.
Submitted by: kkenn
Can't use it verbatim, at least I hate to, as the ", skipped" bit doesn't
make much sense in a library, to me.
|
|
|
|
| |
along with the errno, if one is set.
|