Linux Overlay Filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
	 Miklos Szeredi <miklos@szeredi.hu>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-unionfs@vger.kernel.org
Subject: Re: [GIT PULL] overlayfs updates for 6.13
Date: Sat, 23 Nov 2024 19:47:24 +0100	[thread overview]
Message-ID: <20241123-wortreich-eistee-542b69311fba@brauner> (raw)
In-Reply-To: <20241123-bauhof-tischbein-579ff1db831a@brauner>

On Sat, Nov 23, 2024 at 01:06:14PM +0100, Christian Brauner wrote:
> On Fri, Nov 22, 2024 at 09:21:58PM -0800, Linus Torvalds wrote:
> > On Fri, 22 Nov 2024 at 01:57, Amir Goldstein <amir73il@gmail.com> wrote:
> > >
> > > - Introduction and use of revert/override_creds_light() helpers, that were
> > >   suggested by Christian as a mitigation to cache line bouncing and false
> > >   sharing of fields in overlayfs creator_cred long lived struct cred copy.
> > 
> > So I don't actively hate this, but I do wonder if this shouldn't have
> > been done differently.
> > 
> > In particular, I suspect *most* users of override_creds() actually
> > wants this "light" version, because they all already hold a ref to the
> > cred that they want to use as the override.
> > 
> > We did it that safe way with the extra refcount not because most
> > people would need it, but it was expected to not be a big deal.
> > 
> > Now you found that it *is* a big deal, and instead of just fixing the
> > old interface, you create a whole new interface and the mental burden
> > of having to know the difference between the two.
> 
> > So may I ask that you look at perhaps just converting the (not very
> > many) users of the non-light cred override to the "light" version?
> 
> I think that could be a good idea in general.
> 
> But I have to say I'm feeling a bit defensive after having read your
> message even though I usually try not to. :) 

It was just pointed out to me that this was written like I'm not reading
you messages - which is obviously not the case. What I means it that I
usually try to not be defensive when valid criticism is brought up. :)

  parent reply	other threads:[~2024-11-23 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22  9:57 [GIT PULL] overlayfs updates for 6.13 Amir Goldstein
2024-11-23  5:21 ` Linus Torvalds
2024-11-23  5:22   ` Linus Torvalds
2024-11-23  6:09   ` Linus Torvalds
2024-11-23  6:14     ` Al Viro
2024-11-23 17:18       ` Linus Torvalds
2024-11-23 12:06   ` Christian Brauner
2024-11-23 17:29     ` Linus Torvalds
2024-11-23 18:47     ` Christian Brauner [this message]
2024-11-23  5:57 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241123-wortreich-eistee-542b69311fba@brauner \
    --to=brauner@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox