Hi!
A patch, committed within the last two weeks, broke the named pipe filesystem driver. The result is the message:
service/sctrl.c:305 Pipe read failed
The error code is ERROR_BROKEN_PIPE. This bug keeps user-mode services from starting up. I assume the bug is caused by one on the patches to ntoskrnls IO code because npfs has not been touched for a few more weeks.
Please fix this bug as soon as possible as it keeps me from working on PnP and RPC!
Regards, Eric
Possible it is a problem of the many changes from ntoskrnl\io\file.c. Compiling ros on ros is also broken.
- Hartmut
Eric Kohl wrote:
Hi!
A patch, committed within the last two weeks, broke the named pipe filesystem driver. The result is the message:
service/sctrl.c:305 Pipe read failedThe error code is ERROR_BROKEN_PIPE. This bug keeps user-mode services from starting up. I assume the bug is caused by one on the patches to ntoskrnls IO code because npfs has not been touched for a few more weeks.
Please fix this bug as soon as possible as it keeps me from working on PnP and RPC!
Regards, Eric _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Hartmut Birr wrote:
Possible it is a problem of the many changes from ntoskrnl\io\file.c. Compiling ros on ros is also broken.
- Hartmut
Eric Kohl wrote:
Hi!
A patch, committed within the last two weeks, broke the named pipe filesystem driver. The result is the message:
service/sctrl.c:305 Pipe read failed
The error code is ERROR_BROKEN_PIPE. This bug keeps user-mode services from starting up. I assume the bug is caused by one on the patches to ntoskrnls IO code because npfs has not been touched for a few more weeks.
Please fix this bug as soon as possible as it keeps me from working on PnP and RPC!
Regards, Eric _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Hi guys,
Sorry to disappoint you, I didn't cause this regression :(!
The bug is between 15048 and 15059. Most probably caused by 15048.
Best regards, Alex Ionescu
Eric Kohl wrote:
Hi!
A patch, committed within the last two weeks, broke the named pipe filesystem driver. The result is the message:
service/sctrl.c:305 Pipe read failedThe error code is ERROR_BROKEN_PIPE. This bug keeps user-mode services from starting up. I assume the bug is caused by one on the patches to ntoskrnls IO code because npfs has not been touched for a few more weeks.
Well actually the bug is most probably caused by a bug in the NPFS driver.
Please fix this bug as soon as possible as it keeps me from working on PnP and RPC!
I'll take a look at the NPFS driver and/or I/O code.
Regards, Eric
Best regards, Alex Ionescu