From: David Laight <David.Laight@ACULAB.COM>
To: 'Cong Wang' <xiyou.wangcong@gmail.com>,
Changbin Du <changbin.du@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kici nski <kuba@kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: RE: [PATCH] net: fix oops in socket ioctl cmd SIOCGSKNS when NET_NS is disabled
Date: Mon, 31 May 2021 08:30:58 +0000 [thread overview]
Message-ID: <55effe20acc54ea4a96ea86015d99a5b@AcuMS.aculab.com> (raw)
In-Reply-To: <CAM_iQpWwApLVg39rUkyXxnhsiP0SZf=0ft6vsq=VxFtJ2SumAQ@mail.gmail.com>
From: Cong Wang
> Sent: 29 May 2021 20:15
>
> On Fri, May 28, 2021 at 11:08 PM Changbin Du <changbin.du@gmail.com> wrote:
> > diff --git a/net/socket.c b/net/socket.c
> > index 27e3e7d53f8e..644b46112d35 100644
> > --- a/net/socket.c
> > +++ b/net/socket.c
> > @@ -1149,11 +1149,15 @@ static long sock_ioctl(struct file *file, unsigned cmd, unsigned long arg)
> > mutex_unlock(&vlan_ioctl_mutex);
> > break;
> > case SIOCGSKNS:
> > +#ifdef CONFIG_NET_NS
> > err = -EPERM;
> > if (!ns_capable(net->user_ns, CAP_NET_ADMIN))
> > break;
> >
> > err = open_related_ns(&net->ns, get_net_ns);
> > +#else
> > + err = -ENOTSUPP;
> > +#endif
>
> I wonder if it is easier if we just reject ns->ops==NULL case
> in open_related_ns(). For 1) we can save an ugly #ifdef here;
> 2) drivers/net/tun.c has the same bugs.
If CONFIG_NET_NS is unset then why not make both ns_capable()
and open_related_ns() unconditionally return -ENOTSUPP?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-05-31 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 6:05 [PATCH] net: fix oops in socket ioctl cmd SIOCGSKNS when NET_NS is disabled Changbin Du
2021-05-29 18:27 ` Jakub Kicinski
2021-05-31 15:28 ` Changbin Du
2021-05-29 19:14 ` Cong Wang
2021-05-31 8:30 ` David Laight [this message]
2021-05-31 15:31 ` Changbin Du
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=55effe20acc54ea4a96ea86015d99a5b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=changbin.du@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).