From: David Woodhouse <dwmw2@infradead.org>
To: Eric Paris <eparis@redhat.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Richard Guy Briggs <rgb@redhat.com>,
Manuel Lauss <manuel.lauss@gmail.com>,
linux-audit@redhat.com, Steve Grubb <sgrubb@redhat.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [RESEND PATCH 1/2] MIPS syscall auditing patches
Date: Thu, 03 Apr 2014 15:36:52 +0100 [thread overview]
Message-ID: <1396535812.3615.139.camel@i7.infradead.org> (raw)
In-Reply-To: <1396533511.24733.28.camel@flatline.rdu.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Thu, 2014-04-03 at 09:58 -0400, Eric Paris wrote:
> Same for the 64BIT flag. Do what makes sense to identify the arch and
> don't worry to much about it. (sounds to me like MIPS has 3 arches)
Since the syscall numbers are disjoint for the three MIPS "arches", you
could surely consider it to be just one?
I've kind of missed the point of why that's an improvement though. There
was something about the size of the syscall table, and having 3 (or 6)
copies of it...?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]
next prev parent reply other threads:[~2014-04-03 14:36 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 [this message]
2014-04-03 15:13 ` Richard Guy Briggs
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=1396535812.3615.139.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.org \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.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