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 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2839EC54EE9 for ; Wed, 7 Sep 2022 20:11:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1662581513; 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=8ly5XBxPVwDQwIXyEDD/8XeKYOiaKZ3GGgHI7dKureQ=; b=MysX0xU3IAmLMG0EbJikHgko2uYEf4oHPU3jpsJQMuxuBdP5ZwrrQn9Q9NFBouy/MHIRiK EjJT4k4OVJ5FSuZ2CFZp3GGvOqp7gT5yAO5ZEP3/Z4ubngxE/YsLvXUwTSAACN+698Q3iu S2YTf272MeagxlIwMbqm/7CyWDAfheg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-651-SFILmCQ0MG-dmUexa1IUZA-1; Wed, 07 Sep 2022 16:11:51 -0400 X-MC-Unique: SFILmCQ0MG-dmUexa1IUZA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5F983803301; Wed, 7 Sep 2022 20:11:49 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 236094010E4D; Wed, 7 Sep 2022 20:11:47 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id E6CB41946A44; Wed, 7 Sep 2022 20:11:46 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 217CB1946A40 for ; Wed, 7 Sep 2022 20:11:46 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 0A1D04010D2A; Wed, 7 Sep 2022 20:11:46 +0000 (UTC) Received: from x2.localnet (unknown [10.22.33.231]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9941840C141D; Wed, 7 Sep 2022 20:11:45 +0000 (UTC) From: Steve Grubb To: Paul Moore , Richard Guy Briggs Subject: Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Date: Wed, 07 Sep 2022 16:11:45 -0400 Message-ID: <4753948.GXAFRqVoOG@x2> Organization: Red Hat In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jan Kara , Amir Goldstein , LKML , Linux-Audit Mailing List , linux-fsdevel@vger.kernel.org, Eric Paris Errors-To: linux-audit-bounces@redhat.com Sender: "Linux-audit" X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wednesday, September 7, 2022 2:43:54 PM EDT Richard Guy Briggs wrote: > > > Ultimately I guess I'll leave it upto audit subsystem what it wants to > > > have in its struct fanotify_response_info_audit_rule because for > > > fanotify subsystem, it is just an opaque blob it is passing. > > > > In that case, let's stick with leveraging the type/len fields in the > > fanotify_response_info_header struct, that should give us all the > > flexibility we need. > > > > Richard and Steve, it sounds like Steve is already aware of additional > > information that he wants to send via the > > fanotify_response_info_audit_rule struct, please include that in the > > next revision of this patchset. I don't want to get this merged and > > then soon after have to hack in additional info. > > Steve, please define the type and name of this additional field. Maybe extra_data, app_data, or extra_info. Something generic that can be reused by any application. Default to 0 if not present. Thanks, -Steve -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit