| Age | Commit message (Collapse) | Author |
|---|
|
The Linux NFS server does not accept a setting of file size to 0 for
sockets and FIFOs so there is code to strip that for those cases. I also
spotted that the file modification times were not being applied to a
created file so there is now just one rpc to set all file attributes using
xdr_encode_create_state(). This sets the times to be server time which is
appropriate for a new file (even though it was created in the previous RPC
call). The previous code was supplying the 'gid' based on that returned by
the 'stat' but I don't think that can be relied on since the V3 protocol
states that CREATE3 using EXCLUSIVE cannot guarantee any file attributes
until after the SETATTR3.
|
|
to allow it to be used for MKNOD and SYMLINK rpc calls. These file types
work differently to others in that a temporary file is created earlier and
its 'struct node' is migrated to the new file later. A few adjustments to
the mutex locking to comply with the locking rules. A couple of mutex unlock
errors spotted: not being unlocked on malloc failure and an unnecessary
unlock in netfs_attempt_rename()
|
|
so that it can be used in a slightly different context in a following
patch. I also removed the caching of rpc call results that were failed for
errors other than ENOENT. For example, EPERM doesn't say anything about the
lookup validity for other credentials that might be used.
|
|
|
|
That e.g. happens with qemu -kernel option.
|
|
Note that I have altered the specification of the argument value so that the
version can be specified without the program number rather than the other way
around. I think it is much more likely the version would be specified than the
program number.
|
|
|
|
to retrieve the true identity.
|
|
|
|
as its conclusion was valid and now implemented.
|
|
There was little overlap with the v2 code so it got an entirely separate
implementation. There is the possibility of completing statfs.f_namelen
properly using FSINFO3 and PATHCONF3 rpc calls but I didn't know if
f_namelen should be the maximum length for a file name component or the
entire file name path.
|
|
|
|
|
|
whilst attempting to lock an already held mutex.
|
|
|
|
We want to drop the slice part only in the partstore case.
(but still want to change the device in case of USB disk)
|
|
|
|
The v3 netfs_attempt_create_file() uses the 'exclusive' creation protocol
which cannot specify the file permission bits or uid/gid. These need to be
applied post-creation using SETATTR3. There was a missing call to do the chmod
part which I've added. Previously the call to chown that was present did not
consider the return value. I have done so.
|
|
Use the 64 bit value required for v3 'offset' and process opaque_data part
of the reply properly.
|
|
for unlikely case of RPC init failure and processing of v3 reply
|
|
This adds new code to process the reply from a file creation operation that
applies equally to CREATE3, MKDIR3, SYMLINK3 and MKNOD3. RFC1813 permits
a reply without the created file's handle and it might be necessary to
perform a LOOKUP3 on the created file post-creation. Debian Linux NFSV3
server actually always returns the handle when compiling gnumach however
I have tested the case where it might not by adding code (now removed) to
pretend the handle wasn't present in the reply. I expect therefore that the
'skip_returned_stat' function that is added is rarely called.
Fixed netfs_attempt_mkdir() to process the NFSv3 reply properly.
|
|
|
|
|
|
|
|
Better use the stdint.
Also export them, they will be useful generally.
|
|
|
|
This allows top to show Cpu0 to CpuN idle stats when you press 1.
TESTED: on UP and SMP gnumach with debian hurd-i386.
Message-ID: <20250707092520.62819-1-damien@zamaudio.com>
|
|
|
|
|
|
|
|
rumpusbdisk's driving of USB sticks won't interfere with gnumach
operating SATA.
|
|
This provides a functional rumpdisk and rumpusbdisk
with or without static linkage of librump.
Message-ID: <20250701141609.152652-1-damien@zamaudio.com>
|
|
|
|
The VGA boards may not like AVX-whatnot-optimized 512B accesses. E.g.
qemu does not support it and raises an invalid opcode trap.
|
|
COLOR_PAIR takes a color pair, it does not produce one.
|
|
that pass through to /dev/usbdisk.
|
|
* libpager/demuxer.c(pager_start_workers): set current and max RLIMIT_AS
to RLIM_INFINITY when the current user has access to the privileged host
port.
Message-ID: <20250616225815.844-2-dnietoc@gmail.com>
|
|
Fall back to bios defaults for requests for irq 9.
Ideally we could check the PIIX3 bridge device exists on
pci, but that would require pci access before pci-arbiter
exists. This is a convenient workaround for now.
Message-ID: <20250622073557.188295-1-damien@zamaudio.com>
|
|
|
|
|
|
|
|
This was offsetting all values on the parameters stack
|
|
Previously, ‘accept’ would return an O_NONBLOCK socket if the listening
socket was O_NONBLOCK at the time the connection was made. With this
change, ‘accept’ always returns a socket where O_NONBLOCK is cleared.
|
|
|
|
Use 64bit mapped time values in maptime_read when the kernel and the
mapped_time_value structure in header file time_value.h support it.
Otherwise step back to use the 32bit time.
Message-ID: <20250503132808.15359-1-zhmingluo@163.com>
|
|
54c0b9b9dbf7 ("ext2fs: Trap trying to access bogus data areas") added
checks on the allocated block number, but did not take care of the
out-of-space condition, which callers of ext2_new_block and
ext2_alloc_block know to handle.
|
|
This fixes making diskfs_catch_exception recursive, catching the last
fault exception, and fixes callers.
|
|
tmpfs loses files when they are unlinked but still mapped.
|
|
Message-ID: <20250402092354.293338-1-zhmingluo@163.com>
|
|
So that if we get a lazily-cleaned inode, we do not get disturbed by the
values, notably i_file_acl and i_dir_acl were not cleaned, and
i_block_group not checked.
b0ff48880bb40 ("Formerly ialloc.c.~6~") introduced only setting
dn_set_ctime when cleanup was missing, but we always want to set the
ctime for a new inode anyway.
|
