All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: linux-audit@redhat.com, "Jarsulic,
	Michael [CRI]" <mjarsulic@bsd.uchicago.edu>
Subject: Re: Question regarding ntpd
Date: Tue, 11 Oct 2016 12:07:02 -0400	[thread overview]
Message-ID: <2633790.HIaGmAgEAo@x2> (raw)
In-Reply-To: <57FC0CA7.4000404@tlinx.org>

On Monday, October 10, 2016 2:48:23 PM EDT L. A. Walsh wrote:
> Steve Grubb wrote:
> > But ntpd overwhelms logs but chronyd might be marginally better. See bz
> > https://bugzilla.redhat.com/show_bug.cgi?id=918127
> 
> ---
> I took a gander at said bugzilla num, and found a minor surprise in that
> there
> Miroslav Lichvar said:
> 
>    "You can use ntpd from the ntp package instead of chrony, it
>     shouldn't call adjtimex as often as chronyd does."
> ---
> 
> I.e. the exact opposite of your (Steve)'s statement.  Wondered if that was
> a misread or newer information...<*idle curiosity*>.
> 
> Either way sounds like it would be "nice" to differentiate a "read" from
> a "write" in this syscall if it is to be useful.

I agree. But the problem with this syscall is that the operation is part of a 
data structure that is passed by address to the kernel. There currently is no 
good way to filter its uses because the audit subsystem can only look at the 
actual argument passed. I think there may be an issue opened for this on 
github.

-Steve

  reply	other threads:[~2016-10-11 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 22:05 Question regarding ntpd Sullivan, Daniel [CRI]
2016-09-27 23:16 ` Steve Grubb
2016-09-28  0:06   ` John Jasen
2016-09-28  1:21     ` Sullivan, Daniel [CRI]
2016-09-28  0:21   ` Ryan Sawhill
2016-09-28  1:45     ` Sullivan, Daniel [CRI]
2016-09-28  1:17   ` Sullivan, Daniel [CRI]
2016-10-10 21:48   ` L. A. Walsh
2016-10-11 16:07     ` Steve Grubb [this message]
2016-10-11 20:49       ` Paul Moore
2016-10-11 21:37         ` L. A. Walsh
2016-10-13 12:25           ` Paul Moore
2016-10-11 16:33     ` Ryan Sawhill

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=2633790.HIaGmAgEAo@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=lkml@tlinx.org \
    --cc=mjarsulic@bsd.uchicago.edu \
    /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.