mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org,
	Zou Pengcheng <pczou@redflag-linux.com>,
	Trivial Kernel Patches <trivial@rustcorp.com.au>
Subject: Re: [PATCH] dnotify fix for readv/writev (Linux 2.4.20)
Date: Mon, 2 Dec 2002 16:31:11 +1100	[thread overview]
Message-ID: <20021202163111.560d218d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <200212020922.43820.pczou@redflag-linux.com>

Hi Linus,

On Mon, 2 Dec 2002 09:22:43 +0800 Zou Pengcheng <pczou@redflag-linux.com> wrote:
>
> this is a patch to fix the dnotify bug of readv/writev. 
> 
> Orignally DN_MODIFY is issued on readv while DN_ACCESS is issued on writev, 
> which is obviously wrong. This patch fixes such problem.
> 
> cheers,
>   -- Pengcheng Zou

This is the equivalent patch for 2.5.50+.

Please apply.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff -ruN 2.5.50-BK/fs/read_write.c 2.5.50-BK-dnotify/fs/read_write.c
--- 2.5.50-BK/fs/read_write.c	2002-12-02 16:25:50.000000000 +1100
+++ 2.5.50-BK-dnotify/fs/read_write.c	2002-12-02 16:28:39.000000000 +1100
@@ -447,7 +447,7 @@
 		kfree(iov);
 	if ((ret + (type == READ)) > 0)
 		dnotify_parent(file->f_dentry,
-				(type == READ) ? DN_MODIFY : DN_ACCESS);
+				(type == READ) ? DN_ACCESS : DN_MODIFY);
 	return ret;
 }
 

      reply	other threads:[~2002-12-02  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  1:22 Zou Pengcheng
2002-12-02  5:31 ` Stephen Rothwell [this message]

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=20021202163111.560d218d.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pczou@redflag-linux.com \
    --cc=torvalds@transmeta.com \
    --cc=trivial@rustcorp.com.au \
    /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®