From: Andi Kleen <ak@suse.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@redhat.com>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: Inotify patch missed arch/x86_64/ia32/sys_ia32.c
Date: Fri, 15 Jul 2005 14:15:16 +0200 [thread overview]
Message-ID: <20050715141516.6c107c34@basil.nowhere.org> (raw)
In-Reply-To: <1121426860.1909.52.camel@sisko.sctweedie.blueyonder.co.uk>
On Fri, 15 Jul 2005 12:27:40 +0100
"Stephen C. Tweedie" <sct@redhat.com> wrote:
> Hi,
>
> The inotify patch just added a line
>
> + fsnotify_open(f->f_dentry);
>
> to sys_open, but it missed the x86_64 compatibility sys32_open()
> equivalent in arch/x86_64/ia32/sys_ia32.c.
... and probably missing in the other compat layers too.
> Andi, perhaps it's time to factor out the guts of sys_open from the flag
> munging to keep as much of that code as common as possible, and avoid
> this sort of maintenance problem in the future?
No problem from my side if someone does a patch, but on the other hand if
sys_open needs changes then likely all filp_open callers need too, and one would
better hope the patcher knows how to operate "grep -r" then. So it might
not buy much.
-Andi
prev parent reply other threads:[~2005-07-15 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 11:27 Stephen C. Tweedie
2005-07-15 12:15 ` Andi Kleen [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=20050715141516.6c107c34@basil.nowhere.org \
--to=ak@suse.de \
--cc=dwmw2@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®