> On Mon, Mar 12, 2001 at 09:15:33PM -0500, Alexander Viro wrote:
> > On Mon, 12 Mar 2001, Chris Mason wrote:
> > > Since fs/pipe.c:pipe_write() calls mark_inode_dirty, and it is legal to
> > > write to a named pipe on a readonly filesystem, we can end up writing an
> > > inode on a readonly FS.
> >
> > I would check that in pipe_write()...
>
> So atime and mtime of a named pipe are meaningless in general?
> That would make sense, since you cannot access the data anymore,
> once they are through the pipe.
Huh? They are meaningless if fs is read-only. Can't change inode in
such situation... For normal filesystems it's "how long ago somebody
did <type of access> with this FIFO".
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/