This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Hurd".
The branch, master has been updated via 529b93b8f6cc94830325cfde1b237f0ca04af38e (commit) via 2c39bb58dfbcc018d2f2104d60733e6cf6be4adc (commit) via f7ba77a585b1ada60ca08e0033b50eaca2138961 (commit) via d74aaad213577fe22fa171093a0f1d1820503cb6 (commit) from 21f8f17a959097f02ebbfb5a11692ba7c17cd6e2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 529b93b8f6cc94830325cfde1b237f0ca04af38e Author: Michael Kelly <m...@weatherwax.co.uk> Date: Sun Jul 20 14:19:11 2025 +0200 nfs: fix the handling of replies to MKNOD and SYMLINK 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. commit 2c39bb58dfbcc018d2f2104d60733e6cf6be4adc Author: Michael Kelly <m...@weatherwax.co.uk> Date: Sun Jul 20 14:17:28 2025 +0200 nfs: generalise process_create_reply() 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() commit f7ba77a585b1ada60ca08e0033b50eaca2138961 Author: Michael Kelly <m...@weatherwax.co.uk> Date: Sun Jul 20 14:15:58 2025 +0200 nfs: generalises the code for making a LOOKUP rpc call 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. commit d74aaad213577fe22fa171093a0f1d1820503cb6 Author: Michael Kelly <m...@weatherwax.co.uk> Date: Sun Jul 20 14:11:05 2025 +0200 nfs: generalise calling SETATTR ----------------------------------------------------------------------- Summary of changes: nfs/nfs.c | 32 +++++++- nfs/ops.c | 274 ++++++++++++++++++++++++++++++-------------------------------- 2 files changed, 163 insertions(+), 143 deletions(-) hooks/post-receive -- Hurd