From: Christian Brauner <christian.brauner@ubuntu.com>
To: CGEL <cgel.zte@gmail.com>
Cc: dbueso@suse.de, jamorris@linux.microsoft.com,
keescook@chromium.org, ktkhai@virtuozzo.com, legion@kernel.org,
linux-kernel@vger.kernel.org, ran.xiaokai@zte.com.cn,
varad.gautam@suse.com
Subject: Re: [PATCH V2] ipc: add set_ownership() and permissions() callbacks for posix mqueue sysctl
Date: Wed, 1 Dec 2021 13:53:14 +0100 [thread overview]
Message-ID: <20211201125314.mhx7z4nhg2ei2eof@wittgenstein> (raw)
In-Reply-To: <61a720eb.1c69fb81.80210.02b6@mx.google.com>
On Wed, Dec 01, 2021 at 07:14:50AM +0000, CGEL wrote:
> On Mon, Oct 04, 2021 at 12:53:13PM +0200, Christian Brauner wrote:
> > On Thu, Sep 16, 2021 at 01:49:31AM +0000, CGEL wrote:
> > > esOn Mon, Sep 13, 2021 at 04:40:47PM +0200, Christian Brauner wrote:
> > > > On Fri, Aug 27, 2021 at 03:12:06AM -0700, CGEL wrote:
> > > > > From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> > > > >
> > > > > When a non-root user process creates a user namespace and ipc namespace
> > > > > with command "unshare -Ur -i", and map the root user inside
> > > > > the user namesapce to the global owner of user namespace.
> > > > > The newly created user namespace OWNS the ipc namespace,
> > > > > So the root user inside the user namespace should have full access
> > > > > rights to the ipc namespace resources and should be writable to
> > > > > the ipc mqueue sysctls.
> > > > >
> > > > > v2:
> > > > > - update commit msg.
> > > > > - fix the coding style issue.
> > > > > Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> > > > > ---
> > > >
> > > > David,
> > > >
> > > > are you happy with this too? If so I'd pick this up.
> > > >
> > >
> > > Hi Christian,
> > >
> > > Is there a xx-next branch for this kind patch?
> > > We will try to fixes other issues like this, so we could tag the follow-up
> > > patches with the branch name.
> >
> > Hm, sorry that message slipped through the pre-mid-and post-conference
> > cracks. I'll added the patches now for testing. See:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=kernel.fixes
> >
> > Christian
>
> Hi Christian,
>
> How the the testing goes on?
I'll plan to send this for the next merge window.
Thanks!
Christian
next prev parent reply other threads:[~2021-12-01 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 3:06 [PATCH] ipc: add set_ownership() and permissions() callbacks for posix mqueue sysctl cgel.zte
2021-07-29 14:53 ` Christian Brauner
2021-08-03 10:31 ` CGEL
2021-08-03 14:01 ` Christian Brauner
2021-08-11 15:51 ` CGEL
2021-08-23 3:29 ` [PATCH] tests: add mqueue sysctl tests for user namespace Ran Xiaokai
2021-08-23 15:26 ` Davidlohr Bueso
2021-08-24 12:05 ` Christian Brauner
2021-08-27 9:50 ` [PATCH V2] " CGEL
2021-08-27 10:12 ` [PATCH V2] ipc: add set_ownership() and permissions() callbacks for posix mqueue sysctl CGEL
2021-09-13 14:40 ` Christian Brauner
2021-09-13 19:42 ` Davidlohr Bueso
2021-09-16 1:49 ` CGEL
2021-10-04 10:53 ` Christian Brauner
2021-12-01 7:14 ` CGEL
2021-12-01 12:53 ` Christian Brauner [this message]
2022-04-06 7:59 ` cgel.zte
2021-07-30 15:09 ` [PATCH] " Davidlohr Bueso
2021-08-03 10:34 ` CGEL
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=20211201125314.mhx7z4nhg2ei2eof@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=cgel.zte@gmail.com \
--cc=dbueso@suse.de \
--cc=jamorris@linux.microsoft.com \
--cc=keescook@chromium.org \
--cc=ktkhai@virtuozzo.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=varad.gautam@suse.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;
as well as URLs for NNTP newsgroup(s).