From: Paul Moore <paul@paul-moore.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Andrew G. Morgan" <morgan@kernel.org>,
Gaosheng Cui <cuigaosheng1@huawei.com>,
akpm@linux-foundation.org, ezk@cs.sunysb.edu,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
Date: Sat, 5 Nov 2022 01:33:05 -0400 [thread overview]
Message-ID: <CAHC9VhS4-e-OphfCyaSmRDRA0_3t+ZjtdOStNeddJ5xRaD1E7g@mail.gmail.com> (raw)
In-Reply-To: <20221103132434.GA30946@mail.hallyn.com>
On Thu, Nov 3, 2022 at 9:24 AM Serge E. Hallyn <serge@hallyn.com> wrote:
> Ok, thanks.
>
> I wouldn't mind putting up a capability tree if number of patches were
> going to start ramping up, but historically that has not been worth it.
Don't ever let me stop you from setting up a capability tree, but
yeah, I understand why it probably wouldn't be very useful. As long
as you keep doing the reviews, ACKs, etc. I don't mind carrying the
capability patches in the LSM tree; merging stuff is usually the easy
part of the job.
--
paul-moore.com
next prev parent reply other threads:[~2022-11-05 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:25 [PATCH] capabilities: fix undefined behavior in bit shift for CAP_TO_MASK Gaosheng Cui
2022-10-31 14:18 ` Andrew G. Morgan
2022-11-01 4:30 ` Serge E. Hallyn
2022-11-03 11:57 ` Paul Moore
2022-11-03 13:24 ` Serge E. Hallyn
2022-11-05 5:33 ` Paul Moore [this message]
2022-11-05 5:30 ` 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=CAHC9VhS4-e-OphfCyaSmRDRA0_3t+ZjtdOStNeddJ5xRaD1E7g@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=akpm@linux-foundation.org \
--cc=cuigaosheng1@huawei.com \
--cc=ezk@cs.sunysb.edu \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=serge@hallyn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.