From: Richard Guy Briggs <rgb@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
linux-audit@redhat.com, Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [RESEND PATCH 1/2] MIPS syscall auditing patches
Date: Thu, 3 Apr 2014 11:13:36 -0400 [thread overview]
Message-ID: <20140403151336.GA24821@madcap2.tricolour.ca> (raw)
In-Reply-To: <1396532936.3615.124.camel@i7.infradead.org>
On 14/04/03, David Woodhouse wrote:
> On Thu, 2014-04-03 at 11:32 +0200, Ralf Baechle wrote:
> The __AUDIT_ARCH_64BIT flag does allow you to distinguish between 32-bit
> and 64-bit system calls on architectures where you can't tell them apart
> by syscall number alone (e.g. S390?). But even that isn't really needed
> on MIPS because the syscall number tells you *everything* you need to
> know, doesn't it?
That hadn't even occured to me. So, why not use O32, N32 and 64 flags
and just take mod 1000 of the syscall number and use a 64-bit mask? Or
drop the 3 arch flags and just identify the arch from the syscall number
range alone?
> David Woodhouse Open Source Technology Centre
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-04-03 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:13 [RESEND PATCH 0/2] MIPS syscall auditing patches Manuel Lauss
2014-04-02 10:13 ` [RESEND PATCH 1/2] " Manuel Lauss
2014-04-02 15:56 ` Richard Guy Briggs
2014-04-03 9:32 ` Ralf Baechle
2014-04-03 13:12 ` Steve Grubb
2014-04-03 13:48 ` David Woodhouse
2014-04-03 13:58 ` Eric Paris
2014-04-03 14:36 ` David Woodhouse
2014-04-03 15:13 ` Richard Guy Briggs [this message]
2014-04-03 14:04 ` Eric Paris
2014-04-02 10:13 ` [RESEND PATCH 2/2] " Manuel Lauss
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=20140403151336.GA24821@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.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