From: Paul Moore <paul@paul-moore.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
viro@zeniv.linux.org.uk, serge@hallyn.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 2/2] vfs: avoid duplicating creds in faccessat if possible
Date: Wed, 25 Jan 2023 12:11:00 -0500 [thread overview]
Message-ID: <CAHC9VhTOeGXqqsbfuWXoe+od4YvfCoPPCwyionRGOj2ZaTH4mg@mail.gmail.com> (raw)
In-Reply-To: <CAGudoHHkeF-ozA-A+7ZcJP-Su02PwE4rfQ79VgD0zw8zS84YwA@mail.gmail.com>
On Wed, Jan 25, 2023 at 11:17 AM Mateusz Guzik <mjguzik@gmail.com> wrote:
> So I posted v3 with the comment, you are CC'ed.
>
> I'm not going to further argue about the patch. If you want to write
> your own variant that's fine with me, feel free to take my bench results
> and denote they come from a similar version.
Once again, I see the back-and-forth as more of a discussion, not
really an argument in the combative sense, but everyone reads their
email differently I guess.
The comment is an improvement, thanks for that, now it's just a matter
of hearing from the VFS folks.
--
paul-moore.com
next prev parent reply other threads:[~2023-01-25 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 21:21 [PATCH v2 1/2] capability: add cap_isidentical Mateusz Guzik
2023-01-16 21:21 ` [PATCH v2 2/2] vfs: avoid duplicating creds in faccessat if possible Mateusz Guzik
2023-01-20 20:45 ` Paul Moore
2023-01-21 0:50 ` Mateusz Guzik
2023-01-21 1:18 ` Mateusz Guzik
2023-01-23 21:29 ` Paul Moore
2023-01-24 10:16 ` Mateusz Guzik
2023-01-24 17:00 ` Paul Moore
2023-01-24 17:14 ` Linus Torvalds
2023-01-24 18:42 ` Mateusz Guzik
2023-01-24 20:37 ` Linus Torvalds
2023-01-24 21:33 ` Paul Moore
2023-01-25 15:00 ` Mateusz Guzik
2023-01-25 16:17 ` Mateusz Guzik
2023-01-25 17:11 ` Paul Moore [this message]
2023-01-25 17:07 ` Paul Moore
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=CAHC9VhTOeGXqqsbfuWXoe+od4YvfCoPPCwyionRGOj2ZaTH4mg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=serge@hallyn.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).