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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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 65375C4320E for ; Sun, 29 Aug 2021 15:18:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4998B606A5 for ; Sun, 29 Aug 2021 15:18:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235587AbhH2PTh (ORCPT ); Sun, 29 Aug 2021 11:19:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235577AbhH2PTc (ORCPT ); Sun, 29 Aug 2021 11:19:32 -0400 Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B108C06175F for ; Sun, 29 Aug 2021 08:18:39 -0700 (PDT) Received: by mail-ej1-x62c.google.com with SMTP id x11so25548414ejv.0 for ; Sun, 29 Aug 2021 08:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WMCQKvetI0XkPpqOn9T5HvUMfbn/ZoV4rfgKei7DRbQ=; b=AUUV3UubwIyhdd3QwL/BBxhZ19xpizfCaKyOw0a60FAYj9f66viJmJP7tYy41TL9Wo eNf6jSSenKzez1einuBFP0+fY9nxF6hdr1wO8rBa3ENpUIALSpb4xoQIe/FnGz9OdKr4 akd3h/x4wweRLZcDu6qCobE/A7Z+xWpOUJyaSVSIMFFdmJFI1BFVv9+MTwOs3ranzCkd oGxztcxgF7GefWZbnqsGU98ezJNZs0M34yqlyXDBLekLrFowEkt6Te8nTfcICh1kqHvv hxVzVNp/aWF2NVcn274Ko4GkP2ceS0SC5ZOsxYWUhGAioPzZG9dDe5rsYQsNxZdwDVK5 euJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMCQKvetI0XkPpqOn9T5HvUMfbn/ZoV4rfgKei7DRbQ=; b=r+7nsekF1i06xz2ZrJHxxZ3NsnAJR7/0uX4z3O/BuKwYQQT87K2EFP5xhAEMeAi1qy a7kERE6y7QjwcjbvIUjp85PPS33eUj3C7WN3z7xbJkg4m+nIiL/yG/dcAMzyT0H/vUek 1QjccGsDdWahUSDHcGOebGO6Ep7wyJmxJkZFeMerfeMpq9qWRU5s6dtbGGesZJZjNYvI pI93M0jfsANNjoWtmEA01IGVRpfRdGNoPX1S2yD5h3LVLG5MPjuIvqsffCGIMGoyOIPP WU/dJAId4gEPNbugyZ8LgBwxVOjxwzpGXhyVvfWj0MLqKfGcivaJ2u3XGTD2Qt81e+JV JA6g== X-Gm-Message-State: AOAM532w5+RelHUdmF3D3LBR7PrLbtlLPUC8lkw11sMNVnKEDxl+NpSM V46b0OwmhZimvxS9po33TvICuXqBYmM/KjPYILOe X-Google-Smtp-Source: ABdhPJzddDAP4GwVgg5xjP+pa+Pe/nyxAGXU1kyChZOijuG2A5i+rzFXA53gOJ+xW6ZKS9R2sDtfMTdkLKe1+YuoHoI= X-Received: by 2002:a17:906:8597:: with SMTP id v23mr13342286ejx.178.1630250318016; Sun, 29 Aug 2021 08:18:38 -0700 (PDT) MIME-Version: 1.0 References: <162871480969.63873.9434591871437326374.stgit@olly> <20210824205724.GB490529@madcap2.tricolour.ca> <20210826011639.GE490529@madcap2.tricolour.ca> <20210826163230.GF490529@madcap2.tricolour.ca> <20210827133559.GG490529@madcap2.tricolour.ca> <20210828150356.GH490529@madcap2.tricolour.ca> In-Reply-To: <20210828150356.GH490529@madcap2.tricolour.ca> From: Paul Moore Date: Sun, 29 Aug 2021 11:18:26 -0400 Message-ID: Subject: Re: [RFC PATCH v2 0/9] Add LSM access controls and auditing to io_uring To: Richard Guy Briggs Cc: linux-security-module@vger.kernel.org, selinux@vger.kernel.org, linux-audit@redhat.com, io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org, Kumar Kartikeya Dwivedi , Jens Axboe , Pavel Begunkov Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Sat, Aug 28, 2021 at 11:04 AM Richard Guy Briggs wrote: > I did set a syscall filter for > -a exit,always -F arch=b64 -S io_uring_enter,io_uring_setup,io_uring_register -F key=iouringsyscall > and that yielded some records with a couple of orphans that surprised me > a bit. Without looking too closely at the log you sent, you can expect URING records without an associated SYSCALL record when the uring op is being processed in the io-wq or sqpoll context. In the io-wq case the processing is happening after the thread finished the syscall but before the execution context returns to userspace and in the case of sqpoll the processing is handled by a separate kernel thread with no association to a process thread. -- paul moore www.paul-moore.com