From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: named pipe writes on readonly filesystems
Date: Tue, 13 Mar 2001 10:22:24 +0100 [thread overview]
Message-ID: <20010313102224.A17224@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <517520000.984449174@tiny> <Pine.GSO.4.21.0103122113480.28460-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0103122113480.28460-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Mon, Mar 12, 2001 at 09:15:33PM -0500
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.
Regards
Ingo Oeser
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-03-13 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 2:06 Chris Mason
2001-03-13 2:15 ` Alexander Viro
2001-03-13 9:22 ` Ingo Oeser [this message]
2001-03-13 9:26 ` Alexander Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010313102224.A17224@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®