Jamie Lokier <jamie@xxxxxxxxxxxxx> writes: > Eric W. Biederman wrote: >> >> revoked_file_ops return 0 from reads (aka EOF). Tell poll the file is >> >> always ready for I/O and return -EIO from all other operations. >> > >> > I think read should return -EIO too. If a program is reading from a >> > /proc file (say), and the thing it's reading suddenly disappears, EOF >> > gives the false impression that it's read to the end of formatted data >> > from that file and it can process the data as if it's complete, which >> > is wrong. >> >> Good point EIO is the current read return value for a removed proc file. >> >> For closed pipes, and hung up ttys the read return value is 0, and from >> my reading that is what bsd returns after a sys_revoke. > > A few suggestions below. Feel free to ignore them on account of the > basic revoking functionality being more important :-) I think I will. This seems to be the part of the code that is easily approachable and it is going to be easy to have different opinions on, and there is no one right answer. For now I'm just going to pick my best understanding of what BSD did. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
