From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: dhowells@redhat.com, yasutake.koichi@jp.panasonic.com,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: arch/ && tracehook_report_syscall_xxx()
Date: Mon, 27 Apr 2009 20:43:55 +0200 [thread overview]
Message-ID: <20090427184355.GA3281@redhat.com> (raw)
In-Reply-To: <20090427182919.B923DFC3BF@magilla.sf.frob.com>
On 04/27, Roland McGrath wrote:
>
> > We have a lot of code like arch/alpha/kernel/ptrace.c:syscall_trace()
> > in arch/ and I can't see how to convert them to use tracehooks.
> >
> > The first problem, we don't know which hook should be called, there is
> > no entry/exit argument.
>
> These arch maintainers just need to update their code. Christoph has
> started poking arch folks individually about getting up to speed.
Ah, good.
> IMHO, it is better anyway to use separate entry/exit calls. For that
> change, it is often easy to see how to do it correctly in the assembly code
> without really knowing the arch at all. (There are separate assembly paths
> leading to the calls for entry vs exit cases already, just change the
> symbol names. Adding an argument would require a bit of a clue about
> assembly on the arch.)
>
> > Still, I think it is better to change this code right now, and call
> > ptrace_report_syscall() directly.
>
> I disagree. Let the arch code get with the modern style.
> It is just a minute's hack for the arch maintainer.
Sure, if maintainers can help then we don't need the temporary/incomplete
changes.
Oleg.
next prev parent reply other threads:[~2009-04-27 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 18:04 arch/ && tracehook_report_syscall_xxx() Oleg Nesterov
2009-04-27 18:29 ` Roland McGrath
2009-04-27 18:32 ` Christoph Hellwig
2009-04-29 19:08 ` Fwd: " Oleg Nesterov
2009-04-29 19:17 ` Roland McGrath
2009-04-29 19:30 ` Ingo Molnar
2009-04-29 19:44 ` Christoph Hellwig
2009-04-29 19:53 ` Kyle McMartin
2009-04-27 18:43 ` Oleg Nesterov [this message]
2009-04-27 19:24 ` David Howells
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=20090427184355.GA3281@redhat.com \
--to=oleg@redhat.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=yasutake.koichi@jp.panasonic.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