From: Robert Love <rml@novell.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify: add x86-64 syscall numbers
Date: Fri, 15 Jul 2005 16:09:53 -0400 [thread overview]
Message-ID: <1121458193.830.27.camel@betsy> (raw)
In-Reply-To: <p73wtnrbzzr.fsf@bragg.suse.de>
On Fri, 2005-07-15 at 22:01 +0200, Andi Kleen wrote:
> It won't work anyways because you forgot to patch the compat
> sys32_open.
Well, "won't work" is a bit harsh, its just one hook. But that was
next.
I usually leave per-arch stuff to the arch folks.
Robert Love
Add fsnotify_open() hook to sys32_open() on x86-64.
Signed-off-by: Robert Love <rml@novell.com>
arch/x86_64/ia32/sys_ia32.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletion(-)
diff -urN linux-2.6.13-rc3/arch/x86_64/ia32/sys_ia32.c linux/arch/x86_64/ia32/sys_ia32.c
--- linux-2.6.13-rc3/arch/x86_64/ia32/sys_ia32.c 2005-07-15 16:08:27.000000000 -0400
+++ linux/arch/x86_64/ia32/sys_ia32.c 2005-07-15 16:07:21.000000000 -0400
@@ -61,6 +61,7 @@
#include <linux/ptrace.h>
#include <linux/highuid.h>
#include <linux/vmalloc.h>
+#include <linux/fsnotify.>
#include <asm/mman.h>
#include <asm/types.h>
#include <asm/uaccess.h>
@@ -984,8 +985,10 @@
if (IS_ERR(f)) {
put_unused_fd(fd);
fd = error;
- } else
+ } else {
+ fsnotify_open(f->f_dentry);
fd_install(fd, f);
+ }
}
putname(tmp);
}
next prev parent reply other threads:[~2005-07-15 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1121457125.830.22.camel@betsy.suse.lists.linux.kernel>
2005-07-15 20:01 ` [patch] inotify: add x86-64 syscall numbers Andi Kleen
2005-07-15 20:09 ` Robert Love [this message]
2005-07-15 19:52 Robert Love
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=1121458193.830.27.camel@betsy \
--to=rml@novell.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.