From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] audit: Modify a set of system calls in audit class definitions
Date: Fri, 17 Jan 2014 12:28:40 +0000 [thread overview]
Message-ID: <20140117122840.GG16003@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1389945903-4326-1-git-send-email-takahiro.akashi@linaro.org>
On Fri, Jan 17, 2014 at 08:05:03AM +0000, AKASHI Takahiro wrote:
> Each asm-generic/audit_xx.h defines a set of system calls for respective
> audit permssion class (read, write, change attribute or exec).
permission
> This patch changes two entries:
>
> 1) fchown in audit_change_attr.h
> Make fchown included by its own because in asm-generic/unistd.h, for example,
> fchown always exists while chown is optional. This change is necessary at
> least for arm64.
>
> 2) truncate64 in audit_write.h
> Add missing truncate64/ftruncate64 as well as truncate/ftruncate
>
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2014-01-17 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 8:05 [PATCH] audit: Modify a set of system calls in audit class definitions AKASHI Takahiro
2014-01-17 12:28 ` Will Deacon [this message]
2014-01-17 19:42 ` Richard Guy Briggs
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=20140117122840.GG16003@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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