You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to the fact that one command (e.g. PS) uses PCBUF to get information from the kernel, tries, to write it to STDOUT, so it locks PCBUF during this time, while the shell still tries to open the down-pipe process, which is also using PCBUF to open the file and FORK.
The text was updated successfully, but these errors were encountered:
the shell keeps locking PCBUF as long as it is needed to build the complete pipe chain. This is similar to what init and filesystems do today, init locks PCBUF with PSEM and the filesystem releases once it has registered itself with VSEM. But forked processes now "inherit" the semaphore, and release it - should FORK provide some block that too?
PS needs to copy away the data and immediately release PCBUF
This is related to the fact that one command (e.g. PS) uses PCBUF to get information from the kernel, tries, to write it to STDOUT, so it locks PCBUF during this time, while the shell still tries to open the down-pipe process, which is also using PCBUF to open the file and FORK.
The text was updated successfully, but these errors were encountered: