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=-4.6 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 6EF8FC41604 for ; Tue, 6 Oct 2020 20:20:47 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.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 BF1392083B for ; Tue, 6 Oct 2020 20:20:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="CghEk6cm" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BF1392083B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=linux-audit-bounces@redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1602015645; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to: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=T+rt0NxTzKDylZJnQmEQmbOY3GwWqiJfJxJVgZUy63A=; b=CghEk6cmb2QCJDZPhkNv42UAuM61vxCiThefIobLwt+dmF9EEYdAPgiDPFAhjF0yFZfW0H +g8l1pfm4liRdUfq6M2F0UBnjlaOu+z+vG1S0rnKD8obKkhN30a93csU61KcG4DMS+41Wi hnELxPwW8Dc3V1aXGvbRezmLsixSlRQ= 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-240-6rASq-b4NSCJuu6xyhWxCA-1; Tue, 06 Oct 2020 16:20:43 -0400 X-MC-Unique: 6rASq-b4NSCJuu6xyhWxCA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9C9E618BE160; Tue, 6 Oct 2020 20:20:39 +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 DAB9D5D9CD; Tue, 6 Oct 2020 20:20:38 +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 37FA779FF3; Tue, 6 Oct 2020 20:20:38 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 096KKab2023906 for ; Tue, 6 Oct 2020 16:20:36 -0400 Received: by smtp.corp.redhat.com (Postfix) id D9C5037DD; Tue, 6 Oct 2020 20:20:36 +0000 (UTC) Received: from x2.localnet (ovpn-116-174.rdu2.redhat.com [10.10.116.174]) by smtp.corp.redhat.com (Postfix) with ESMTP id 94EC760E1C; Tue, 6 Oct 2020 20:20:33 +0000 (UTC) From: Steve Grubb To: linux-audit@redhat.com Subject: Re: Identifying thread/process termination Date: Tue, 06 Oct 2020 16:20:32 -0400 Message-ID: <5549003.MhkbZ0Pkbq@x2> Organization: Red Hat In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-loop: linux-audit@redhat.com 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.14 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 Hello, On Monday, October 5, 2020 3:07:12 PM EDT Natan Yellin wrote: > I've been tracking all process terminations using a rule for the exit and > exit_group syscalls. However, by looking at the audit events for exit it is > impossible to differentiate between the death of different threads in the > same thread group. Is there an alternative way to track this? I don't think the audit system was ever designed to distinguish between threads. But there is a general need to determine the exit of a process rather than a thread. Paul, Richard, Do you have any thoughts? -Steve > For my use case, I would like to know when either processes or individual > threads execute and terminate. (I'm fine tracking at either granularity.) > Right now I can track the creation properly using fork/clone/etc but for > termination I receive multiple exit events with identical information that > doesn't let me know which thread died. -- Linux-audit mailing list Linux-audit@redhat.com https://www.redhat.com/mailman/listinfo/linux-audit