Re: named pipe writes on readonly filesystems

On Tue, 13 Mar 2001, Ingo Oeser wrote: > 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

Re: named pipe writes on readonly filesystems

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 woul

Re: named pipe writes on readonly filesystems

On Mon, 12 Mar 2001, Chris Mason wrote: > Hello everyone, > > 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()...

named pipe writes on readonly filesystems

Hello everyone, 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. reiserfs prints a warning whenever someone tries to write an inode on a readonly FS, so we've been getting a fe