Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp6989876rwl; Mon, 9 Jan 2023 16:16:27 -0800 (PST) X-Google-Smtp-Source: AMrXdXvZuO/HuuDptxYWoc9EsHTw3mICIY/M7Nc+BKk9cZ5vJLeusgpc2DotL9P+ycg5jGNkdOyk X-Received: by 2002:a17:906:2509:b0:7c0:f2c5:ac3f with SMTP id i9-20020a170906250900b007c0f2c5ac3fmr54040859ejb.58.1673309786767; Mon, 09 Jan 2023 16:16:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673309786; cv=none; d=google.com; s=arc-20160816; b=EdLU+504gT1mvFPD0zkfXidudcJW7ecF7rc3No4+Md5CmUQiFnmeOy9zRX76TffF+i ZX6jRseP0GKu6NQjGG+v7XjCvSffXijkOzc4eQjWGpBGZBhLuWXxwMP0+Pxg1eLA29VW 8MD5XznPd8u3Fsrx98piYt4vwYg9eIOWTPo+hf6vqPzmEfo8mhj0ahDE2fDmg8Lqj1Sh 2l4zvnxVqYtUVA0CJBSOJdZlRuAFnpjYHsfFq7/lv3ZiWkB+6e1ttkDWznQQ4y6KyHbm BHryB3h+cCXgJDt6eEhlkqIV8tpnVavhGK1xJkn+Zja+U4mYsNlT0ml5aKgq1aMngbHa Hgiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:organization:message-id:date:subject:cc:to :from:dkim-signature; bh=iapCfz1rFKFdP7CVLCAke8ViE4mAB2lsuFKVxrGNfa4=; b=VzQ0Qr+keNDiX5Xe2uiqUOEjUE0rleMQA8hJK627MUDl0cb1qAdViSPuEtX5F2Y6s8 5PE6mYBfEPPrVigpD1tGD6eNv14xn/oRtVGHvTa0YGQf+smUuBRgtoQkJzC61r8syn4/ D+ZZcs46raP/EzHGZGcKYleONVlfBwlW+ulZ3jMAvG7RifgOCcArXW0cAWPL5N3Ufu0q lFxzMs0LeJrSlLC5qahC+i3E94bSn1ws9T/rx29LEXLSpvoVI7Be5km3Xdopspmim+Qn im8V1PYcSYQiK69ONAuwoU47QLu1+5mwD9StHlJSOagoWO0pvt8hD7o1WbZGdB0KIDZZ 0PZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=iIEwLC4b; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sa4-20020a1709076d0400b0078fcfc5d24esi11267454ejc.618.2023.01.09.16.16.13; Mon, 09 Jan 2023 16:16:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=iIEwLC4b; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237843AbjAJAHs (ORCPT + 53 others); Mon, 9 Jan 2023 19:07:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52416 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237525AbjAJAHe (ORCPT ); Mon, 9 Jan 2023 19:07:34 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7362B488 for ; Mon, 9 Jan 2023 16:06:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673309205; h=from:from: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; bh=iapCfz1rFKFdP7CVLCAke8ViE4mAB2lsuFKVxrGNfa4=; b=iIEwLC4bNzdoBTIdfM4oNUfQqUsgDDi9MNrKC1FNgO4Wx2aNIAnul7sEN3b8TSMnlDoAxy pz7KJ4wth23dNK7/VtYxdchE9EI9Q39IFRXqX+7xBs11bm35FMlsPYFgjzr1rMUNqDWjIX PntsfUzgpcwF2nr6Rl/VXAu8LMj7H2U= 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-96-FsPNlyx_MfSTfNmTKXRULg-1; Mon, 09 Jan 2023 19:06:44 -0500 X-MC-Unique: FsPNlyx_MfSTfNmTKXRULg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 499108027FE; Tue, 10 Jan 2023 00:06:44 +0000 (UTC) Received: from x2.localnet (unknown [10.22.32.102]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3F453140EBF5; Tue, 10 Jan 2023 00:06:43 +0000 (UTC) From: Steve Grubb To: Linux-Audit Mailing List , LKML , linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, Richard Guy Briggs Cc: Paul Moore , Eric Paris , Richard Guy Briggs , Jan Kara , Amir Goldstein Subject: Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response Date: Mon, 09 Jan 2023 19:06:42 -0500 Message-ID: <3211441.aeNJFYEL58@x2> Organization: Red Hat In-Reply-To: <79fcf72ea442eeede53ed5e6de567f8df8ef7d83.1670606054.git.rgb@redhat.com> References: <79fcf72ea442eeede53ed5e6de567f8df8ef7d83.1670606054.git.rgb@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Sorry to take so long. Holidays and kernel build problems. However, I have built a kernel with these patches. I only have 2 comments. When I use an application that expected the old API, meaning it simply does: response.fd = metadata->fd; response.response = reply; close(metadata->fd); write(fd, &response, sizeof(struct fanotify_response)); I get access denials. Every time. If the program is using the new API and sets FAN_INFO, then it works as expected. I'll do some more testing but I think there is something wrong in the compatibility path. On Monday, December 12, 2022 9:06:11 AM EST Richard Guy Briggs wrote: > This patch passes the full response so that the audit function can use all > of it. The audit function was updated to log the additional information in > the AUDIT_FANOTIFY record. What I'm seeing is: type=FANOTIFY msg=audit(01/09/2023 18:43:16.306:366) : resp=deny fan_type=1 fan_info=313300000000000000000000 subj_trust=0 obj_trust=0 Where fan_info was supposed to be 13 decimal. More below... > Currently the only type of fanotify info that is defined is an audit > rule number, but convert it to hex encoding to future-proof the field. > Hex encoding suggested by Paul Moore . > > Sample records: > type=FANOTIFY msg=audit(1600385147.372:590): resp=2 fan_type=1 > fan_info=3137 subj_trust=3 obj_trust=5 type=FANOTIFY > msg=audit(1659730979.839:284): resp=1 fan_type=0 fan_info=3F subj_trust=2 > obj_trust=2 > > Suggested-by: Steve Grubb > Link: https://lore.kernel.org/r/3075502.aeNJFYEL58@x2 > Signed-off-by: Richard Guy Briggs > --- > fs/notify/fanotify/fanotify.c | 3 ++- > include/linux/audit.h | 9 +++++---- > kernel/auditsc.c | 25 ++++++++++++++++++++++--- > 3 files changed, 29 insertions(+), 8 deletions(-) > > diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c > index 24ec1d66d5a8..29bdd99b29fa 100644 > --- a/fs/notify/fanotify/fanotify.c > +++ b/fs/notify/fanotify/fanotify.c > @@ -273,7 +273,8 @@ static int fanotify_get_response(struct fsnotify_group > *group, > > /* Check if the response should be audited */ > if (event->response & FAN_AUDIT) > - audit_fanotify(event->response & ~FAN_AUDIT); > + audit_fanotify(event->response & ~FAN_AUDIT, > + &event->audit_rule); > > pr_debug("%s: group=%p event=%p about to return ret=%d\n", __func__, > group, event, ret); > diff --git a/include/linux/audit.h b/include/linux/audit.h > index d6b7d0c7ce43..31086a72e32a 100644 > --- a/include/linux/audit.h > +++ b/include/linux/audit.h > @@ -14,6 +14,7 @@ > #include > #include > #include > +#include > > #define AUDIT_INO_UNSET ((unsigned long)-1) > #define AUDIT_DEV_UNSET ((dev_t)-1) > @@ -416,7 +417,7 @@ extern void __audit_log_capset(const struct cred *new, > const struct cred *old); extern void __audit_mmap_fd(int fd, int flags); > extern void __audit_openat2_how(struct open_how *how); > extern void __audit_log_kern_module(char *name); > -extern void __audit_fanotify(u32 response); > +extern void __audit_fanotify(u32 response, struct > fanotify_response_info_audit_rule *friar); extern void > __audit_tk_injoffset(struct timespec64 offset); > extern void __audit_ntp_log(const struct audit_ntp_data *ad); > extern void __audit_log_nfcfg(const char *name, u8 af, unsigned int > nentries, @@ -523,10 +524,10 @@ static inline void > audit_log_kern_module(char *name) __audit_log_kern_module(name); > } > > -static inline void audit_fanotify(u32 response) > +static inline void audit_fanotify(u32 response, struct > fanotify_response_info_audit_rule *friar) { > if (!audit_dummy_context()) > - __audit_fanotify(response); > + __audit_fanotify(response, friar); > } > > static inline void audit_tk_injoffset(struct timespec64 offset) > @@ -679,7 +680,7 @@ static inline void audit_log_kern_module(char *name) > { > } > > -static inline void audit_fanotify(u32 response) > +static inline void audit_fanotify(u32 response, struct > fanotify_response_info_audit_rule *friar) { } > > static inline void audit_tk_injoffset(struct timespec64 offset) > diff --git a/kernel/auditsc.c b/kernel/auditsc.c > index d1fb821de104..8d523066d81f 100644 > --- a/kernel/auditsc.c > +++ b/kernel/auditsc.c > @@ -64,6 +64,7 @@ > #include > #include > #include // struct open_how > +#include > > #include "audit.h" > > @@ -2877,10 +2878,28 @@ void __audit_log_kern_module(char *name) > context->type = AUDIT_KERN_MODULE; > } > > -void __audit_fanotify(u32 response) > +void __audit_fanotify(u32 response, struct > fanotify_response_info_audit_rule *friar) { > - audit_log(audit_context(), GFP_KERNEL, > - AUDIT_FANOTIFY, "resp=%u", response); > + struct audit_context *ctx = audit_context(); > + struct audit_buffer *ab; > + char numbuf[12]; > + > + if (friar->hdr.type == FAN_RESPONSE_INFO_NONE) { > + audit_log(audit_context(), GFP_KERNEL, AUDIT_FANOTIFY, > + "resp=%u fan_type=%u fan_info=3F subj_trust=2 obj_trust=2", > + response, FAN_RESPONSE_INFO_NONE); > + return; > + } > + ab = audit_log_start(ctx, GFP_KERNEL, AUDIT_FANOTIFY); > + if (ab) { > + audit_log_format(ab, "resp=%u fan_type=%u fan_info=", > + response, friar->hdr.type); > + snprintf(numbuf, sizeof(numbuf), "%u", friar->rule_number); > + audit_log_n_hex(ab, numbuf, sizeof(numbuf)); I don't think it needs to be converted to ascii and then hexencoded. As Paul said, probably %X is all we need here. -Steve > + audit_log_format(ab, " subj_trust=%u obj_trust=%u", > + friar->subj_trust, friar->obj_trust); > + audit_log_end(ab); > + } > } > > void __audit_tk_injoffset(struct timespec64 offset)