From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5537CC433DB for ; Tue, 19 Jan 2021 21:53:21 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E26A322E01 for ; Tue, 19 Jan 2021 21:53:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E26A322E01 Authentication-Results: mail.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-audit-bounces@redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1611093198; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=ycfgJi5mFxAe7Z76gNOANV/gEJUavSFB+r89JeuWXK8=; b=BSaEzzaC05zWj84fqPZztG//mRV/QdLRCUI1kFOBfIvAZhjhC/0HlUJ5jO2IhEtetQeJJO +nu60r5ZnghtdgNnTL0mDziTfOSjWYmx5GEeIZbNLXzikck8Ob+DRK1MuMoxEXI9YLq6RR +J2+8UM5YMi5L2QI3ofg45dMo2c5jB0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-5-KdVoKsZ0OIyA1vAB2dBE8Q-1; Tue, 19 Jan 2021 16:53:16 -0500 X-MC-Unique: KdVoKsZ0OIyA1vAB2dBE8Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 067B0806663; Tue, 19 Jan 2021 21:53:13 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C966B2CF2C; Tue, 19 Jan 2021 21:53:11 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 3E7114BB7B; Tue, 19 Jan 2021 21:52:54 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 10JLpEXg005094 for ; Tue, 19 Jan 2021 16:51:14 -0500 Received: by smtp.corp.redhat.com (Postfix) id DE82369320; Tue, 19 Jan 2021 21:51:14 +0000 (UTC) Received: from x2.localnet (ovpn-116-90.rdu2.redhat.com [10.10.116.90]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9CBC2629C0; Tue, 19 Jan 2021 21:51:08 +0000 (UTC) From: Steve Grubb To: burn@swtf.dyndns.org, Paul Moore Subject: Re: Occasional delayed output of events Date: Tue, 19 Jan 2021 16:51:08 -0500 Message-ID: <805552026.0ifERbkFSE@x2> Organization: Red Hat In-Reply-To: References: <30c5dbc14368a1919717e2f39d2d4c29463c3108.camel@iinet.net.au> <9fd0d1b4585214eb3ed8db6da066b571563f19bc.camel@iinet.net.au> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-loop: linux-audit@redhat.com Cc: Richard Guy Briggs , Linux Audit X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=linux-audit-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tuesday, January 19, 2021 3:26:04 PM EST Paul Moore wrote: > On Tue, Jan 19, 2021 at 2:38 PM Burn Alting wrote: > > All systems use chrony (current NTP daemon). One is a VM (on top of KVM) > > and the other a bare metal deployment. Does the above explain my second > > data set (in the issue) from a bare metal Centos 8 host? Perhaps Lenny's > > comments bare investigation. Either way, I will offer a patch to the > > user space code to, based on a configuration value, manage correctly > > such activity. > ... > > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609921000.636:1787850): > > msg=audit(1609921000.636:1787850): > > msg=audit(1609921000.636:1787850): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609921008.456:1787851): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609921010.837:1787852): > > msg=audit(1609921010.837:1787852): > > msg=audit(1609921010.837:1787852): > > > msg=audit(1609921010.837:1787852): > Looking at the extracted snippet above where event 1787849 is out of > > order we see the following timestamps: > > msg=audit(1609920994.483:1787848): > > msg=audit(1609920994.484:1787849): > > msg=audit(1609921000.636:1787850): > > msg=audit(1609921008.456:1787851): > > > msg=audit(1609921010.837:1787852): > > ... which looks correct in as much that the time doesn't appear to go > backwards between events. As I said before, I'm not sure how Steve's > userspace works so the time may be a red herring. It only handles one record at a time. No chance to mix things up. The github issue says that 30-stig.rules is being used. If the system time changed with chrony, I would expect syscall events with adjtimex. But the only ones given are execve. -Steve > Barring some weird condition where auditd disconnects and quickly > reconnects to the kernel, and/or dies and is replaced quickly, I'm not > seeing anything obvious in the kernel which would cause this. I'm not > saying there isn't anything there, just that it isn't obvious to me at > the moment :) -- Linux-audit mailing list Linux-audit@redhat.com https://www.redhat.com/mailman/listinfo/linux-audit