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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A74D5C54EAA for ; Fri, 27 Jan 2023 23:09:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232797AbjA0XJH (ORCPT ); Fri, 27 Jan 2023 18:09:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56462 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232757AbjA0XJC (ORCPT ); Fri, 27 Jan 2023 18:09:02 -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 270A47D9B8 for ; Fri, 27 Jan 2023 15:08:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674860889; 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=iP5M+Rvk3GF5mM9HY3iEHMgp/cYCRLdT0QBjJv/tYEY=; b=GlHYzp0sDHjoq7L84aSfr9K1QwsOcxqNtzxaYxIum/gm5AVFQu3s7BtWeLKBzoVnaeR0/1 x1oZSM8yf8Z2kV8lDs5eJfMHyfIwmWcKLVeqUg3sZFPRr+eg4TgW85YaqhQ907cPmUGRIu XlYonjvDCqjGGD66Dvy9j/1VfozPexA= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-664-dlooKtsfMfankTnBLYHdbQ-1; Fri, 27 Jan 2023 18:08:08 -0500 X-MC-Unique: dlooKtsfMfankTnBLYHdbQ-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 644D51C05AD5; Fri, 27 Jan 2023 23:08:07 +0000 (UTC) Received: from madcap2.tricolour.ca (ovpn-0-3.rdu2.redhat.com [10.22.0.3]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D3902400F8F1; Fri, 27 Jan 2023 23:08:05 +0000 (UTC) Date: Fri, 27 Jan 2023 18:08:03 -0500 From: Richard Guy Briggs To: Jens Axboe Cc: Paul Moore , Linux-Audit Mailing List , LKML , io-uring@vger.kernel.org, Eric Paris , Steve Grubb , Stefan Roesch , Christian Brauner , Pavel Begunkov Subject: Re: [PATCH v1 1/2] io_uring,audit: audit IORING_OP_FADVISE but not IORING_OP_MADVISE Message-ID: References: <68eb0c2dd50bca1af91203669f7f1f8312331f38.1674682056.git.rgb@redhat.com> <6d3f76ae-9f86-a96e-d540-cfd45475e288@kernel.dk> <68b599bb-2329-3125-1859-cf529fbeea00@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <68b599bb-2329-3125-1859-cf529fbeea00@kernel.dk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023-01-27 16:03, Jens Axboe wrote: > On 1/27/23 4:02 PM, Richard Guy Briggs wrote: > > On 2023-01-27 15:45, Jens Axboe wrote: > >> On 1/27/23 3:35?PM, Paul Moore wrote: > >>> On Fri, Jan 27, 2023 at 12:24 PM Richard Guy Briggs wrote: > >>>> > >>>> Since FADVISE can truncate files and MADVISE operates on memory, reverse > >>>> the audit_skip tags. > >>>> > >>>> Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support to io_uring") > >>>> Signed-off-by: Richard Guy Briggs > >>>> --- > >>>> io_uring/opdef.c | 2 +- > >>>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>>> > >>>> diff --git a/io_uring/opdef.c b/io_uring/opdef.c > >>>> index 3aa0d65c50e3..a2bf53b4a38a 100644 > >>>> --- a/io_uring/opdef.c > >>>> +++ b/io_uring/opdef.c > >>>> @@ -306,12 +306,12 @@ const struct io_op_def io_op_defs[] = { > >>>> }, > >>>> [IORING_OP_FADVISE] = { > >>>> .needs_file = 1, > >>>> - .audit_skip = 1, > >>>> .name = "FADVISE", > >>>> .prep = io_fadvise_prep, > >>>> .issue = io_fadvise, > >>>> }, > >>> > >>> I've never used posix_fadvise() or the associated fadvise64*() > >>> syscalls, but from quickly reading the manpages and the > >>> generic_fadvise() function in the kernel I'm missing where the fadvise > >>> family of functions could be used to truncate a file, can you show me > >>> where this happens? The closest I can see is the manipulation of the > >>> page cache, but that shouldn't actually modify the file ... right? > >> > >> Yeah, honestly not sure where that came from. Maybe it's being mixed up > >> with fallocate? All fadvise (or madvise, for that matter) does is > >> provide hints on the caching or access pattern. On second thought, both > >> of these should be able to set audit_skip as far as I can tell. > > > > That was one suspicion I had. If this is the case, I'd agree both could > > be skipped. > > I'd be surprised if Steve didn't mix them up. Once he responds, can you > send a v2 with the correction? Gladly. > Jens Axboe - RGB -- Richard Guy Briggs Sr. S/W Engineer, Kernel Security, Base Operating Systems Remote, Ottawa, Red Hat Canada IRC: rgb, SunRaycer Voice: +1.647.777.2635, Internal: (81) 32635