From: CGEL <cgel.zte@gmail.com>
To: Davidlohr Bueso <dbueso@suse.de>
Cc: keescook@chromium.org, christian.brauner@ubuntu.com,
ktkhai@virtuozzo.com, jamorris@linux.microsoft.com,
varad.gautam@suse.com, legion@kernel.org,
linux-kernel@vger.kernel.org,
Ran Xiaokai <ran.xiaokai@zte.com.cn>
Subject: Re: [PATCH] ipc: add set_ownership() and permissions() callbacks for posix mqueue sysctl
Date: Tue, 3 Aug 2021 03:34:45 -0700 [thread overview]
Message-ID: <20210803103445.GB607784@www> (raw)
In-Reply-To: <4b67a8df7823cc14ffb69657c82562b2@suse.de>
O Fri, Jul 30, 2021 at 08:09:32AM -0700, Davidlohr Bueso wrote:
> On 2021-07-28 20:06, cgel.zte@gmail.com wrote:
> > This patch adds a ctl_table_set per ipc namespace, and also the
> > set_ownership() and permissions() callbacks for the new ctl_table_root
> > for ipc mqueue syscgtls.
> ^^ sysctls
>
> This makes sense to me, just some nits below.
>
> Acked-by: Davidlohr Bueso <dbueso@suse.de>
>
> >
> > Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> > ---
> ...
> > +static int set_permissions(struct ctl_table_header *head,
> > + struct ctl_table *table)
> > +{
>
> Please use curly braces for the else.
>
> > + return (mode << 6) | (mode << 3) | mode;
> > +}
> > +
> > +static void set_ownership(struct ctl_table_header *head,
> > + struct ctl_table *table,
> > + kuid_t *uid, kgid_t *gid)
> > +{
> > + struct ipc_namespace *ipc_ns =
> > + container_of(head->set, struct ipc_namespace, mq_set);
> > + struct user_namespace *user_ns = ipc_ns->user_ns;
> > + kuid_t ns_root_uid;
> > + kgid_t ns_root_gid;
> > +
> > + ns_root_uid = make_kuid(user_ns, 0);
> > + if (uid_valid(ns_root_uid))
> > + *uid = ns_root_uid;
> > +
> > + ns_root_gid = make_kgid(user_ns, 0);
> > + if (gid_valid(ns_root_gid))
> > + *gid = ns_root_gid;
> > +}
>
> Could set_permissions() and set_ownership() be factored such that we can
> avoid duplicated code between ipc and net ns? Something like:
>
> void set_permissions(struct ctl_table_header *head, struct ctl_table *table)
> {
> struct ipc_namespace *ipc_ns = container_of(head->set, struct
> ipc_namespace, mq_set);
> set_permissions_common(ipc_ns->user_ns);
> }
>
> Thanks,
> Davidlohr
Hi Davidlohr
Thanks for your comments.
I will sent a v2 patch together with Christian's comments.
prev parent reply other threads:[~2021-08-03 10:34 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
2022-04-06 7:59 ` cgel.zte
2021-07-30 15:09 ` [PATCH] " Davidlohr Bueso
2021-08-03 10:34 ` CGEL [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=20210803103445.GB607784@www \
--to=cgel.zte@gmail.com \
--cc=christian.brauner@ubuntu.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).