Bug in FIFO implementation in 2.3.x?

• Next message: Mike Galbraith: "2.3.45 aty128fb.c typo"
• Previous message: Simon Garner: "VM: killing process"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Hi, all. I've been noticing odd behaviour with named pipes under
recent 2.3.x kernels (at least since 2.3.36 and possibly before).

If you open a FIFO with O_RDONLY and then call read(2), and then
another process writes to the FIFO, the read(2) call doesn't return. A
subsequent writer process does wake up the reader, however.

Has anybody else noticed this behaviour?

                                Regards,

                                        Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Mike Galbraith: "2.3.45 aty128fb.c typo"
• Previous message: Simon Garner: "VM: killing process"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:14 EST