From: Richard Guy Briggs <rgb@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Moore <paul@paul-moore.com>, Eric Paris <eparis@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Steve Grubb <sgrubb@redhat.com>,
linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] audit: use ktime_get_coarse_ts64() for time access
Date: Fri, 22 Jun 2018 16:24:36 -0400 [thread overview]
Message-ID: <20180622202436.tlowdotb2xo4pc6l@madcap2.tricolour.ca> (raw)
In-Reply-To: <20180618145954.785509-1-arnd@arndb.de>
On 2018-06-18 16:58, Arnd Bergmann wrote:
> The API got renamed for consistency with the other time accessors,
> this changes the audit caller as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
This looks reasonable to me.
Not that I think it matters, but any reason it was swapped in a
different code location other than aesthetics? Time and serial are
usually used together in our code.
Reviewed-by: Richard Guy Briggs <rgb@redhat.com>
> ---
> kernel/audit.c | 2 +-
> kernel/auditsc.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/audit.c b/kernel/audit.c
> index e7478cb58079..3e34b9f03cfe 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -1724,7 +1724,7 @@ static inline void audit_get_stamp(struct audit_context *ctx,
> struct timespec64 *t, unsigned int *serial)
> {
> if (!ctx || !auditsc_get_stamp(ctx, t, serial)) {
> - *t = current_kernel_time64();
> + ktime_get_coarse_ts64(t);
> *serial = audit_serial();
> }
> }
> diff --git a/kernel/auditsc.c b/kernel/auditsc.c
> index ceb1c4596c51..dbbf02f513a8 100644
> --- a/kernel/auditsc.c
> +++ b/kernel/auditsc.c
> @@ -1540,10 +1540,10 @@ void __audit_syscall_entry(int major, unsigned long a1, unsigned long a2,
> context->argv[2] = a3;
> context->argv[3] = a4;
> context->serial = 0;
> - context->ctime = current_kernel_time64();
> context->in_syscall = 1;
> context->current_state = state;
> context->ppid = 0;
> + ktime_get_coarse_ts64(&context->ctime);
> }
>
> /**
> --
> 2.9.0
>
- RGB
--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635
next prev parent reply other threads:[~2018-06-22 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 14:58 [PATCH] audit: use ktime_get_coarse_ts64() for time access Arnd Bergmann
2018-06-22 20:24 ` Richard Guy Briggs [this message]
2018-07-03 14:15 ` Paul Moore
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=20180622202436.tlowdotb2xo4pc6l@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=arnd@arndb.de \
--cc=eparis@redhat.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul@paul-moore.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