Re: [PATCH hurd 0/6] Add file record locking support

2015-01-19 Thread Samuel Thibault
Hello, Thanks for reviving this, it'll definitely be useful! Svante Signell, le Thu 08 Jan 2015 12:28:05 +0100, a écrit : > 1) l_pid of struct flock is not set. According to the manpage (and > posix) the PID of the process blocking the lock should be reported. Can > maybe be solved by a shared me

Re: [PATCH hurd 0/6] Add file record locking support

2015-01-19 Thread Samuel Thibault
Svante Signell, le Thu 08 Jan 2015 12:28:05 +0100, a écrit : > 3/6: libfshelp_rlock.patch: implement fshelp_rlock_* functions It seems this one didn't make its way to the list. Samuel

Re: [PATCH hurd 1/6] Add file record locking support

2015-01-19 Thread Samuel Thibault
Svante Signell, le Thu 08 Jan 2015 12:28:24 +0100, a écrit : > hurd: add new RPC: file_record_lock It seems good. > hurd/ChangeLog > 2014-08-21 Svante Signell > > * fs.defs: Added description. > * hurd_types.defs: Make struct flock_t seven integers long since > l_start and

Re: [PATCH hurd 0/6] Add file record locking support

2015-01-19 Thread Samuel Thibault
Svante Signell, le Fri 09 Jan 2015 10:54:32 +0100, a écrit : > e.g. Debian Hurd patches are not even admitted to be used to make a new > release of Debian glibc until the Debian maintainer decides :( Now > during the freeze nothing happens with glibc, and e.g. the symbol file > update lingers in -p

Re: [PATCH glibc] Add file record locking support

2015-01-19 Thread Samuel Thibault
Hello, Svante Signell, le Thu 08 Jan 2015 19:54:12 +0100, a écrit : > You made me confused, so all changes were not made. I think the malloc > version was better for symmetry reasons. Changed anyway. Which symmetry? You mean fl->foo vs fl.foo? It is not worth spending a malloc call for this. > +

Re: System getting stuck by GCC invocation

2015-01-19 Thread Thomas Schwinge
Hi! On Thu, 25 Sep 2014 08:13:57 +0200, I wrote: > Here is a test case that gets a Hurd system "stuck". (But I don't know > yet what "stuck" exactly means.) Unfortunately, the test case is a > biggie: GCC. The steps to reproduce it, reduced as much as I could: > [...] Just upgrading that syste