public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: hch@infradead.org, robn@verdi.et.tudelft.nl,
	root@chaos.analogic.com, linux-kernel@vger.kernel.org,
	marcelo@conectiva.com.br, sct@redhat.com
Subject: Re: 2.4 bug: fifo-write causes diskwrites to read-only fs !
Date: Fri, 30 May 2003 09:36:06 -0700	[thread overview]
Message-ID: <20030530093606.657a9ca2.akpm@digeo.com> (raw)
In-Reply-To: <1054307933.3749.313.camel@sisko.scot.redhat.com>

"Stephen C. Tweedie" <sct@redhat.com> wrote:
>
> It's pure cut-and-paste from the update_atime immediately above it.  But
> sure, we can clean them both up while we're at it if you want.

2.5 seems to have gained a handy library function.

diff -puN fs/pipe.c~pipe-rofs-fix fs/pipe.c
--- 25/fs/pipe.c~pipe-rofs-fix	2003-05-30 09:33:29.000000000 -0700
+++ 25-akpm/fs/pipe.c	2003-05-30 09:34:08.000000000 -0700
@@ -208,10 +208,8 @@ pipe_write(struct file *filp, const char
 		wake_up_interruptible(PIPE_WAIT(*inode));
 		kill_fasync(PIPE_FASYNC_READERS(*inode), SIGIO, POLL_IN);
 	}
-	if (ret > 0) {
-		inode->i_ctime = inode->i_mtime = CURRENT_TIME;
-		mark_inode_dirty(inode);
-	}
+	if (ret > 0)
+		inode_update_time(inode, 1);	/* mtime and ctime */
 	return ret;
 }
 

_


  reply	other threads:[~2003-05-30 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 17:58 2.4 bug: fifo-write causes diskwrites to read-only fs ! Rob van Nieuwkerk
2003-05-28 18:52 ` Rob van Nieuwkerk
2003-05-28 19:17   ` Richard B. Johnson
2003-05-28 19:34     ` Rob van Nieuwkerk
2003-05-28 20:22       ` Richard B. Johnson
2003-05-28 20:52         ` Rob van Nieuwkerk
2003-05-30 13:21           ` Stephen C. Tweedie
2003-05-30 14:58             ` Christoph Hellwig
2003-05-30 15:18               ` Stephen C. Tweedie
2003-05-30 16:36                 ` Andrew Morton [this message]
2003-05-28 19:22 ` Nuno Silva
2003-05-28 19:37   ` Rob van Nieuwkerk

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=20030530093606.657a9ca2.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=robn@verdi.et.tudelft.nl \
    --cc=root@chaos.analogic.com \
    --cc=sct@redhat.com \
    /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