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 A9534C43217 for ; Thu, 10 Mar 2022 22:11:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344294AbiCJWMX (ORCPT ); Thu, 10 Mar 2022 17:12:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37312 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244380AbiCJWMW (ORCPT ); Thu, 10 Mar 2022 17:12:22 -0500 Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD330187B9F for ; Thu, 10 Mar 2022 14:11:18 -0800 (PST) Received: by mail-ej1-x631.google.com with SMTP id qx21so15110136ejb.13 for ; Thu, 10 Mar 2022 14:11:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9km0i8SFuccdCOVZYquGLNsFmsoS5afCtujPM89debo=; b=DkO/8stlw+jpHvI8npwNphLXTcJGdwo5HGKNzsLEQgRJKoqLNqUtQ14rO8YztWtv6H bAxp1qhPNeH3fynL0mw7GJsoth6uZUwOJRQT3vdvrEI2RpF54ufTb0yXO3++rTXBespQ x5lpjmtoM0L6NN0u9NAmn1YkWynYbmAVkFmqK9RxmA3NcICSIgE9yAEScpXJQ4VdYV+H qGhCj6APjWltlRC5qBmw4vuoMHC3nKYsIbGWFHWJaXvc4I/QXkVgLDu0Y46f5aCQWnEh nBP1d+G1PMaC87QCOjKfloK3Lw9CLGuuIdMcOaJnRc9h+7uDqcwjICH2qyHuewLribm8 lAZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9km0i8SFuccdCOVZYquGLNsFmsoS5afCtujPM89debo=; b=tmV0ZT4u2FEDEoW9cgVRkDXOnotgfAGp/vYBQ79TbCqLjqvzL+rzPQsVxDr9dSMiul +7b9YGsReTLKP+b4TcIIB3T9+mfFiRLX/ui+mISgo8UoTEmOSz8hoZ+lKkdTkClT0S1y 8k+1CN2+PMbaxt5aIyvFTBpoHgVUaqsCtqM56293f0vSYJL4aDL2XDiRRRV4ZsMTMdEb 2tagqARg78Xn/GoGIKjVUSks/O7FT5RHf73ZFUW4I2gzGRcHknls3Ey216KqE+4hdLU8 cRjaiL4XbGjO9ja66g5Dc93i0VYt9LyRXZASAK4TN0KzmpxI1ITk3gdy/suop05lrRha w2cw== X-Gm-Message-State: AOAM5310KbGkjm8nJXgQ0miVTVM/4nEIDeCZ9rdz64i7bMNA1pY17HDs e5hTmxMVAlcYbMXA0peb3ul8kYkIxMcE+ZkrEptq X-Google-Smtp-Source: ABdhPJzuqe7pKCSsXOm2hSO3J0hQynYE7R+uH9xz7Xj/FjdVN2m1z54F4ZugUJ/pEbmhBHGUILXKrslgjHDns1/T+QA= X-Received: by 2002:a17:907:216f:b0:6ce:d85f:35cf with SMTP id rl15-20020a170907216f00b006ced85f35cfmr6109610ejb.517.1646950277373; Thu, 10 Mar 2022 14:11:17 -0800 (PST) MIME-Version: 1.0 References: <20211117015806.2192263-1-dvander@google.com> In-Reply-To: From: Paul Moore Date: Thu, 10 Mar 2022 17:11:05 -0500 Message-ID: Subject: Re: [PATCH v19 0/4] overlayfs override_creds=off & nested get xattr fix To: Vivek Goyal , Amir Goldstein , Miklos Szeredi , David Anderson Cc: Mark Salyzyn , Jonathan Corbet , "Eric W . Biederman" , Randy Dunlap , Stephen Smalley , John Stultz , linux-doc@vger.kernel.org, linux-kernel , linux-fsdevel , overlayfs , LSM List , kernel-team , selinux@vger.kernel.org, paulmoore@microsoft.com, luca.boccassi@microsoft.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: On Wed, Mar 9, 2022 at 4:13 PM Paul Moore wrote: > On Tue, Mar 1, 2022 at 12:05 AM David Anderson wrote= : > > On Mon, Feb 28, 2022 at 5:09 PM Paul Moore wrote: ... > >> This patchset may not have been The Answer, but surely there is > >> something we can do to support this use-case. > > > > Yup exactly, and we still need patches 3 & 4 to deal with this. My curr= ent plan is to try and rework our sepolicy (we have some ideas on how it co= uld be made compatible with how overlayfs works). If that doesn't pan out w= e'll revisit these patches and think harder about how to deal with the cohe= rency issues. > > Can you elaborate a bit more on the coherency issues? Is this the dir > cache issue that is alluded to in the patchset? Anything else that > has come up on review? > > Before I start looking at the dir cache in any detail, did you have > any thoughts on how to resolve the problems that have arisen? David, Vivek, Amir, Miklos, or anyone for that matter, can you please go into more detail on the cache issues? I *think* I may have found a potential solution for an issue that could arise when the credential override is not in place, but I'm not certain it's the only issue :) There is motivation on our part to try and get the "override_creds=3Doff" portion of the patchset working and suitable for upstreaming, but I need some help in making sure I understand all the objections/problems. --=20 paul-moore.com