All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"eparis@redhat.com" <eparis@redhat.com>,
	"rgb@redhat.com" <rgb@redhat.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-audit@redhat.com" <linux-audit@redhat.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 1/3] arm64: Add __NR_* definitions for compat syscalls
Date: Fri, 4 Jul 2014 11:57:00 +0100	[thread overview]
Message-ID: <20140704105700.GD16404@arm.com> (raw)
In-Reply-To: <5418828.mxvNk2rT0e@wuerfel>

On Fri, Jul 04, 2014 at 11:06:07AM +0100, Arnd Bergmann wrote:
> On Friday 04 July 2014 16:28:29 AKASHI Takahiro wrote:
> > From: Catalin Marinas <catalin.marinas@arm.com>
> > 
> > This patch adds __NR_* definitions to asm/unistd32.h, moves the
> > __NR_compat_* definitions to asm/unistd.h and removes all the explicit
> > unistd32.h includes apart from the one building the compat syscall
> > table. The aim is to have the compat __NR_* definitions available but
> > without colliding with the native syscall definitions.
> > 
> > And adds more syscall definitions for 3.16.
> 
> Can you explain in more detail why you want to add those macros? I've
> looked at all three patches in the series but can't find any code using
> them.
> 
> I would expect that we don't need to define those macros at all for
> compat mode, since they are meant primarily for user space (glibc)
> compilation, which gets them from arch/arm/include/asm/unistd.h.

That's coming from commit 4b58841149dc (audit: Add generic compat
syscall support). The compat_audit.c code reuses some of the existing
asm-generic/audit_*.h headers which depend on __NR_* definitions (rather
than __NR_COMPAT_*). Akashi's suggestion was to include a unistd32.h,
hence this patch.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 1/3] arm64: Add __NR_* definitions for compat syscalls
Date: Fri, 4 Jul 2014 11:57:00 +0100	[thread overview]
Message-ID: <20140704105700.GD16404@arm.com> (raw)
In-Reply-To: <5418828.mxvNk2rT0e@wuerfel>

On Fri, Jul 04, 2014 at 11:06:07AM +0100, Arnd Bergmann wrote:
> On Friday 04 July 2014 16:28:29 AKASHI Takahiro wrote:
> > From: Catalin Marinas <catalin.marinas@arm.com>
> > 
> > This patch adds __NR_* definitions to asm/unistd32.h, moves the
> > __NR_compat_* definitions to asm/unistd.h and removes all the explicit
> > unistd32.h includes apart from the one building the compat syscall
> > table. The aim is to have the compat __NR_* definitions available but
> > without colliding with the native syscall definitions.
> > 
> > And adds more syscall definitions for 3.16.
> 
> Can you explain in more detail why you want to add those macros? I've
> looked at all three patches in the series but can't find any code using
> them.
> 
> I would expect that we don't need to define those macros at all for
> compat mode, since they are meant primarily for user space (glibc)
> compilation, which gets them from arch/arm/include/asm/unistd.h.

That's coming from commit 4b58841149dc (audit: Add generic compat
syscall support). The compat_audit.c code reuses some of the existing
asm-generic/audit_*.h headers which depend on __NR_* definitions (rather
than __NR_COMPAT_*). Akashi's suggestion was to include a unistd32.h,
hence this patch.

-- 
Catalin

  reply	other threads:[~2014-07-04 10:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  7:28 [PATCH v10 0/3] arm64: Add audit support AKASHI Takahiro
2014-07-04  7:28 ` AKASHI Takahiro
2014-07-04  7:28 ` [PATCH v10 1/3] arm64: Add __NR_* definitions for compat syscalls AKASHI Takahiro
2014-07-04  7:28   ` AKASHI Takahiro
2014-07-04 10:06   ` Arnd Bergmann
2014-07-04 10:06     ` Arnd Bergmann
2014-07-04 10:57     ` Catalin Marinas [this message]
2014-07-04 10:57       ` Catalin Marinas
2014-07-04 11:05     ` AKASHI Takahiro
2014-07-04 11:05       ` AKASHI Takahiro
2014-07-04 11:17       ` Arnd Bergmann
2014-07-04 11:17         ` Arnd Bergmann
2015-01-28 21:31   ` Timur Tabi
2015-01-28 21:31     ` Timur Tabi
2015-01-28 21:31     ` Timur Tabi
2015-01-28 21:35     ` Arnd Bergmann
2015-01-28 21:35       ` Arnd Bergmann
2015-01-28 21:35       ` Arnd Bergmann
2015-01-29  9:57     ` Will Deacon
2015-01-29  9:57       ` Will Deacon
2014-07-04  7:28 ` [PATCH v10 2/3] arm64: Add audit support AKASHI Takahiro
2014-07-04  7:28   ` AKASHI Takahiro
2014-07-04  7:28 ` [PATCH v10 3/3] arm64: audit: Add audit hook in syscall_trace_enter/exit() AKASHI Takahiro
2014-07-04  7:28   ` AKASHI Takahiro
2014-07-10 10:08 ` [PATCH v10 0/3] arm64: Add audit support Catalin Marinas
2014-07-10 10:08   ` Catalin Marinas

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=20140704105700.GD16404@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=arnd@arndb.de \
    --cc=eparis@redhat.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgb@redhat.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.