[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5858051-57fa-dc3f-158a-6afe7fc04ca4@synopsys.com>
Date: Fri, 9 Nov 2018 11:13:33 -0800
From: Vineet Gupta <vineet.gupta1@...opsys.com>
To: Andy Lutomirski <luto@...capital.net>
CC: "Dmitry V. Levin" <ldv@...linux.org>,
Andy Lutomirski <luto@...nel.org>,
Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...hat.com>,
"Elvira Khabirova" <lineprinter@...linux.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"linux-audit@...hat.com" <linux-audit@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 06/13] arc: define syscall_get_arch()
On 11/9/18 11:03 AM, Andy Lutomirski wrote:
>> Does ptrace (or user of this API) need a unique value per arch. Otherwise instead
>> of adding the boilerplate code to all arches, they could simply define AUDIT_ARCH
>> and common code could return it. Also the EM_xxx are not there in
>> include/uapi/linux/elf.h to begin with since libc elf.h already defines them.
>>
> A lot of architectures allow multiple audit_arches at runtime due to compat support and similar features, so it really does want to be a function. The goal of this patch set is to get it supported everywhere.
>
I was wondering if we could have a common syscall_get_arch() simply returning an
per-arch AUDIT_ARCH. But seems like the function itself needs to be per arch
anyways due to the nuances above.
Powered by blists - more mailing lists