From: Alejandro Colomar <alx.manpages@gmail.com>
To: Patrick Reader <_@pxeger.com>, linux-man@vger.kernel.org
Subject: Re: [patch] unshare.2: Add note about potential capabilities confusion
Date: Tue, 6 Sep 2022 14:03:55 +0200 [thread overview]
Message-ID: <4c3df615-ce8c-35ae-7a0e-d69e563ec00c@gmail.com> (raw)
In-Reply-To: <0102018312aa4b17-59210806-b085-41ce-b346-2d30f99effe7-000000@eu-west-1.amazonses.com>
[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]
Hi Patrick,
On 9/6/22 13:58, Patrick Reader wrote:
> On 06/09/2022 12:50, Alejandro Colomar wrote:
>> Would you mind fixing those small issues and send an v2?
>
> Voilà!
>
> From a63c099d31c8fd27af6428c4d9191df698b2c0e7 Mon Sep 17 00:00:00 2001
> From: Patrick Reader <_@pxeger.com>
> Date: Tue, 6 Sep 2022 12:56:12 +0100
> Subject: [PATCH 2/2] fix formatting
I was going to apply your patches, when I got a warning from git-am(1):
warning: Patch sent with format=flowed; space at the end of lines might
be lost.
Applying: unshare.2: Add note about potential capabilities confusion
error: corrupt patch at line 10
I guess you copied the patches into your mailer, and it screwed it. If
you could re-send your patches with git-send-email(1) or some other tool
that can send them pristine, that would be great. Otherwise, I can try
to apply your changes manually.
Cheers,
Alex
>
> ---
> man/man2/unshare.2 | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/man/man2/unshare.2 b/man/man2/unshare.2
> index 851129022..79a960728 100644
> --- a/man/man2/unshare.2
> +++ b/man/man2/unshare.2
> @@ -464,9 +464,10 @@ Such functionality may be added in the future, if
> required.
> .PP
> Creating all kinds of namespace, except user namespaces, requires the
> .B CAP_SYS_ADMIN
> -capability. However, since creating a user namespace automatically
> confers a
> -full set of capabilities, creating both a user namespace and any other
> type
> -of namespace in the same
> +capability.
> +However, since creating a user namespace automatically confers a full
> set of
> +capabilities,
> +creating both a user namespace and any other type of namespace in the same
> .BR unshare ()
> call does not require the
> .B CAP_SYS_ADMIN
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-06 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 9:01 [patch] unshare.2: Add note about potential capabilities confusion Patrick Reader
2022-09-06 11:50 ` Alejandro Colomar
2022-09-06 11:58 ` Patrick Reader
2022-09-06 12:03 ` Alejandro Colomar [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=4c3df615-ce8c-35ae-7a0e-d69e563ec00c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=_@pxeger.com \
--cc=linux-man@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).