From: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Lukasz Pawelczyk <havner@gmail.com>
Subject: Re: [PATCH v2] netfilter: xt_owner: Add supplementary groups option
Date: Wed, 08 May 2019 17:56:37 +0200 [thread overview]
Message-ID: <cf34c829002177e89806e9f7260559aefb3c2ac7.camel@samsung.com> (raw)
In-Reply-To: <6a6e9754-4f2b-3433-6df0-bbb9d9915582@gmail.com>
On Wed, 2019-05-08 at 08:41 -0700, Eric Dumazet wrote:
>
> On 5/8/19 11:25 AM, Lukasz Pawelczyk wrote:
> > On Wed, 2019-05-08 at 07:58 -0700, Eric Dumazet wrote:
> > > On 5/8/19 10:12 AM, Lukasz Pawelczyk wrote:
> > > > The XT_SUPPL_GROUPS flag causes GIDs specified with
> > > > XT_OWNER_GID to
> > > > be also checked in the supplementary groups of a process.
> > > >
> > > > Signed-off-by: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
> > > > ---
> > > > include/uapi/linux/netfilter/xt_owner.h | 1 +
> > > > net/netfilter/xt_owner.c | 23
> > > > ++++++++++++++++++++-
> > > > --
> > > > 2 files changed, 21 insertions(+), 3 deletions(-)
> > > >
> > > > diff --git a/include/uapi/linux/netfilter/xt_owner.h
> > > > b/include/uapi/linux/netfilter/xt_owner.h
> > > > index fa3ad84957d5..d646f0dc3466 100644
> > > > --- a/include/uapi/linux/netfilter/xt_owner.h
> > > > +++ b/include/uapi/linux/netfilter/xt_owner.h
> > > > @@ -8,6 +8,7 @@ enum {
> > > > XT_OWNER_UID = 1 << 0,
> > > > XT_OWNER_GID = 1 << 1,
> > > > XT_OWNER_SOCKET = 1 << 2,
> > > > + XT_SUPPL_GROUPS = 1 << 3,
> > > > };
> > > >
> > > > struct xt_owner_match_info {
> > > > diff --git a/net/netfilter/xt_owner.c
> > > > b/net/netfilter/xt_owner.c
> > > > index 46686fb73784..283a1fb5cc52 100644
> > > > --- a/net/netfilter/xt_owner.c
> > > > +++ b/net/netfilter/xt_owner.c
> > > > @@ -91,11 +91,28 @@ owner_mt(const struct sk_buff *skb, struct
> > > > xt_action_param *par)
> > > > }
> > > >
> > > > if (info->match & XT_OWNER_GID) {
> > > > + unsigned int i, match = false;
> > > > kgid_t gid_min = make_kgid(net->user_ns, info-
> > > > > gid_min);
> > > > kgid_t gid_max = make_kgid(net->user_ns, info-
> > > > > gid_max);
> > > > - if ((gid_gte(filp->f_cred->fsgid, gid_min) &&
> > > > - gid_lte(filp->f_cred->fsgid, gid_max)) ^
> > > > - !(info->invert & XT_OWNER_GID))
> > > > + struct group_info *gi = filp->f_cred-
> > > > >group_info;
> > > > +
> > > > + if (gid_gte(filp->f_cred->fsgid, gid_min) &&
> > > > + gid_lte(filp->f_cred->fsgid, gid_max))
> > > > + match = true;
> > > > +
> > > > + if (!match && (info->match & XT_SUPPL_GROUPS)
> > > > && gi) {
> > > > + for (i = 0; i < gi->ngroups; ++i) {
> > > > + kgid_t group = gi->gid[i];
> > > > +
> > > > + if (gid_gte(group, gid_min) &&
> > > > + gid_lte(group, gid_max)) {
> > > > + match = true;
> > > > + break;
> > > > + }
> > > > + }
> > > > + }
> > > > +
> > > > + if (match ^ !(info->invert & XT_OWNER_GID))
> > > > return false;
> > > > }
> > > >
> > > >
> > >
> > > How can this be safe on SMP ?
> > >
> >
> > From what I see after the group_info rework some time ago this
> > struct
> > is never modified. It's replaced. Would
> > get_group_info/put_group_info
> > around the code be enough?
>
> What prevents the data to be freed right after you fetch filp-
> >f_cred->group_info ?
I think the get_group_info() I mentioned above would. group_info seems
to always be freed by put_group_info().
--
Lukasz Pawelczyk
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2019-05-08 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190508141219eucas1p1e5a899714747b497499976113ea9681f@eucas1p1.samsung.com>
2019-05-08 14:12 ` [PATCH v2] netfilter: xt_owner: Add supplementary groups option Lukasz Pawelczyk
2019-05-08 14:58 ` Eric Dumazet
2019-05-08 15:25 ` Lukasz Pawelczyk
2019-05-08 15:41 ` Eric Dumazet
2019-05-08 15:56 ` Lukasz Pawelczyk [this message]
2019-05-08 16:53 ` Eric Dumazet
2019-05-09 10:47 ` Lukasz Pawelczyk
2019-05-09 11:29 ` Jan Engelhardt
2019-05-09 11:57 ` Eric Dumazet
2019-05-09 12:01 ` Lukasz Pawelczyk
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=cf34c829002177e89806e9f7260559aefb3c2ac7.camel@samsung.com \
--to=l.pawelczyk@samsung.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=havner@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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