linux-kernel - Re: arch/ && tracehook_report_syscall

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090427184355.GA3281@redhat.com>
Date:	Mon, 27 Apr 2009 20:43:55 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	dhowells@...hat.com, yasutake.koichi@...panasonic.com,
	linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: arch/ && tracehook_report_syscall_xxx()

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/