From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
hu1.chen@intel.com, miklos@szeredi.hu, malini.bhandaru@intel.com,
tim.c.chen@intel.com, mikko.ylinen@intel.com,
lizhen.you@intel.com, linux-unionfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC] HACK: overlayfs: Optimize overlay/restore creds
Date: Mon, 18 Dec 2023 16:17:48 +0100 [thread overview]
Message-ID: <20231218-einnehmen-hufen-822b38b4c94e@brauner> (raw)
In-Reply-To: <CAHk-=whzaCCucr9odvFWcWr72nraRgejD90Nwb2tP8SBE2LTQw@mail.gmail.com>
> I just removed the CONFIG_DEBUG_CREDENTIALS code, because the fix for
I noticed this yesterday. Thanks for getting rid of this stuff. I never
understood who was supposed to use this for what.
prev parent reply other threads:[~2023-12-18 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 7:45 ovl: ovl_fs::creator_cred::usage scalability issues Chen Hu
2023-10-18 11:59 ` Amir Goldstein
2023-12-14 22:02 ` [RFC] HACK: overlayfs: Optimize overlay/restore creds Vinicius Costa Gomes
2023-12-15 10:30 ` Amir Goldstein
2023-12-15 20:00 ` Vinicius Costa Gomes
2023-12-16 10:16 ` Amir Goldstein
2023-12-16 11:38 ` Amir Goldstein
2023-12-18 16:30 ` Christian Brauner
2023-12-18 21:57 ` Vinicius Costa Gomes
2023-12-19 7:15 ` Amir Goldstein
2023-12-19 13:35 ` Christian Brauner
2023-12-19 14:33 ` Vinicius Costa Gomes
2024-01-23 15:39 ` Christian Brauner
2024-01-23 16:37 ` Vinicius Costa Gomes
2023-12-16 18:26 ` Linus Torvalds
2023-12-18 15:17 ` Christian Brauner [this message]
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=20231218-einnehmen-hufen-822b38b4c94e@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=dhowells@redhat.com \
--cc=hu1.chen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=lizhen.you@intel.com \
--cc=malini.bhandaru@intel.com \
--cc=mikko.ylinen@intel.com \
--cc=miklos@szeredi.hu \
--cc=tim.c.chen@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vinicius.gomes@intel.com \
/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
all inboxes | Powered by JetHome®