All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
	selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org
Subject: Re: [PATCH] net: don't unnecessarily load kernel modules in dev_ioctl()
Date: Thu, 08 Mar 2018 12:34:40 -0500 (EST)	[thread overview]
Message-ID: <20180308.123440.2224695014753871221.davem@davemloft.net> (raw)
In-Reply-To: <20180306155920.7b6379ac@xeon-e3>

From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
Date: Tue, 6 Mar 2018 15:59:20 -0800

> Actually dev_load by ethernet name is really a legacy thing that
> should just die,
> 
> It was kept around so that some very tunnel configuration using special names.
> 
> 	# ifconfig sit0
> 
> which probably several web pages still tell users to do...
> We have much better control now with ip commands so that this is just
> baggage.

As you say, some people use this stuff, so we really can't break
it at this point.

WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: pmoore@redhat.com, netdev@vger.kernel.org,
	viro@zeniv.linux.org.uk, dac.override@gmail.com,
	selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] net: don't unnecessarily load kernel modules in dev_ioctl()
Date: Thu, 08 Mar 2018 12:34:40 -0500 (EST)	[thread overview]
Message-ID: <20180308.123440.2224695014753871221.davem@davemloft.net> (raw)
In-Reply-To: <20180306155920.7b6379ac@xeon-e3>

From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 6 Mar 2018 15:59:20 -0800

> Actually dev_load by ethernet name is really a legacy thing that
> should just die,
> 
> It was kept around so that some very tunnel configuration using special names.
> 
> 	# ifconfig sit0
> 
> which probably several web pages still tell users to do...
> We have much better control now with ip commands so that this is just
> baggage.

As you say, some people use this stuff, so we really can't break
it at this point.

WARNING: multiple messages have this Message-ID (diff)
From: davem@davemloft.net (David Miller)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] net: don't unnecessarily load kernel modules in dev_ioctl()
Date: Thu, 08 Mar 2018 12:34:40 -0500 (EST)	[thread overview]
Message-ID: <20180308.123440.2224695014753871221.davem@davemloft.net> (raw)
In-Reply-To: <20180306155920.7b6379ac@xeon-e3>

From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 6 Mar 2018 15:59:20 -0800

> Actually dev_load by ethernet name is really a legacy thing that
> should just die,
> 
> It was kept around so that some very tunnel configuration using special names.
> 
> 	# ifconfig sit0
> 
> which probably several web pages still tell users to do...
> We have much better control now with ip commands so that this is just
> baggage.

As you say, some people use this stuff, so we really can't break
it at this point.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-03-08 17:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 22:27 [PATCH] net: don't unnecessarily load kernel modules in dev_ioctl() Paul Moore
2018-03-06 22:27 ` Paul Moore
2018-03-06 22:27 ` Paul Moore
2018-03-06 22:32 ` Paul Moore
2018-03-06 22:32   ` Paul Moore
2018-03-06 22:32   ` Paul Moore
     [not found]   ` <CAHC9VhR4FzwsAEO9O9Pnpkm2jOBajwZUkn_i0FqOMR_4ycag2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-03-07 20:13     ` David Miller
2018-03-07 20:13       ` David Miller
2018-03-07 20:13       ` David Miller
2018-03-06 23:59 ` Stephen Hemminger
2018-03-06 23:59   ` Stephen Hemminger
2018-03-06 23:59   ` Stephen Hemminger
2018-03-07 13:46   ` Paul Moore
2018-03-07 13:46     ` Paul Moore
2018-03-07 13:46     ` Paul Moore
2018-03-08 17:34   ` David Miller [this message]
2018-03-08 17:34     ` David Miller
2018-03-08 17:34     ` David Miller
     [not found]     ` <20180308.123440.2224695014753871221.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-03-08 18:05       ` Eric Dumazet
2018-03-08 18:05         ` Eric Dumazet
2018-03-08 18:05         ` Eric Dumazet
     [not found]         ` <c2d378b6-80b3-d9e1-7087-95f143875067-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-08 18:11           ` David Miller
2018-03-08 18:11             ` David Miller
2018-03-08 18:11             ` David Miller
     [not found]             ` <20180308.131115.611191617522587758.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-03-08 20:53               ` Eric Dumazet
2018-03-08 20:53                 ` Eric Dumazet
2018-03-08 20:53                 ` Eric Dumazet

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=20180308.123440.2224695014753871221.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org \
    --cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.