Re: cygwin 3.5.4-1: lockf() aborts on overlap and does not fail on overflow

2024-10-17 Thread Takashi Yano via Cygwin
On Thu, 17 Oct 2024 18:37:57 +0200 Christian Franke wrote: > Takashi Yano via Cygwin wrote: > > On Mon, 14 Oct 2024 15:36:02 +0200 > > Christian Franke wrote: > >> Two possibly independent bugs found by 'stress-ng --lockf ...': > >> > >> 1) lockf() may abort the process with api_fatal() if the new

Re: cygwin 3.5.4-1: lockf() aborts on overlap and does not fail on overflow

2024-10-17 Thread Christian Franke via Cygwin
Takashi Yano via Cygwin wrote: On Mon, 14 Oct 2024 15:36:02 +0200 Christian Franke wrote: Two possibly independent bugs found by 'stress-ng --lockf ...': 1) lockf() may abort the process with api_fatal() if the new range partly overlaps with two ranges previously locked by the same process. 2)

Re: cygwin 3.5.4-1: lockf() aborts on overlap and does not fail on overflow

2024-10-17 Thread Takashi Yano via Cygwin
On Mon, 14 Oct 2024 15:36:02 +0200 Christian Franke wrote: > Two possibly independent bugs found by 'stress-ng --lockf ...': > > 1) lockf() may abort the process with api_fatal() if the new range > partly overlaps with two ranges previously locked by the same process. > > 2) lockf() prints a war

cygwin 3.5.4-1: lockf() aborts on overlap and does not fail on overflow

2024-10-14 Thread Christian Franke via Cygwin
Two possibly independent bugs found by 'stress-ng --lockf ...': 1) lockf() may abort the process with api_fatal() if the new range partly overlaps with two ranges previously locked by the same process. 2) lockf() prints a warning on too many locks and returns success. It should not print a wa