[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] 2(3) hurd+glibc: Support for file record locking
From: |
Samuel Thibault |
Subject: |
Re: [PATCH] 2(3) hurd+glibc: Support for file record locking |
Date: |
Sun, 27 Oct 2019 21:06:07 +0100 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Svante Signell, le jeu. 12 sept. 2019 10:23:55 +0200, a ecrit:
> @@ -358,6 +357,18 @@ routine file_reparent (
> skip; /* Was: file_get_children. */
> skip; /* Was: file_get_source. */
>
> +
> +/* Do fcntl type locking on FILE. CMD is from the set F_GETLK64,
> + F_SETLK64, F_SETLKW64. FLOCK64 is passed by the user and is as
> + defined by <fcntl.h>. RENDEZVOUS is MACH_PORT_NULL for per opened
> + file locking and !MACH_PORT_NULL for per process file locking */
> +routine file_record_lock (
> + file: file_t;
> + RPT
> + cmd: int;
> + inout flock64: flock_t;
> + rendezvous: mach_port_send_t);
> +
> /* Overlay a task with a file. Necessary initialization, including
> authentication changes associated with set[ug]id execution must be
> handled by the filesystem. Filesystems normally implement this by
I'm only realizing this, now that I see that rebooting with the patches
applied on hurd fails completely: never insert an RPC between existing
ones! That renumbers everything, we do not want that at any rate. I'll
fix that along committing.
Samuel
- Re: [PATCH] 2(3) hurd+glibc: Support for file record locking,
Samuel Thibault <=