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: Computer Science

2024-10-17 Thread matthew patton via Cygwin
On Wednesday, October 16, 2024 at 11:07:50 PM EDT, Mike Yearwood via Cygwin wrote: > The education of and practice of software is glaringly lax and we have the > collective power to fix it. ahem, Microsoft would like to enter the chat... Apparently "unlimited" funds doesn't help either. I'm go

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