[Bug 1542] pipe_control_t is not deallocated if fifo_open is attempted with O_WRONLY | O_NONBLOCK

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=1542

--- Comment #6 from Chris Johns <chrisj at rtems.org> 2010-06-23 18:42:26 CDT ---
Could you please explain this case in more detail ?

I see in fifo_open a call to pipe_new and this allocates a new pipe and creates
the barriers. This new pipe never leaves the context of the fifo_open so I
cannot see how other threads could have run and blocked on the barrier. I
suspect I am not understanding something about pipes.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.