On Fri, 4 Nov 2016 11:59:13 +0100
Phil Sutter <p...@nwl.cc> wrote:
> On Fri, Nov 04, 2016 at 11:10:42AM +0100, Jesper Dangaard Brouer wrote:
> >
> > On Fri, 4 Nov 2016 10:35:26 +0100 Phil Sutter <p...@nwl.cc> wrote:
> >
> > > Hi,
> > >
> > > On Thu, Nov 03, 2016 at 02:56:11PM +0100, Jesper Dangaard Brouer wrote:
> > > [...]
> > > > diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
> > > > index 206dc24add3a..f337f1bdd1d4 100644
> > > > --- a/net/sched/sch_api.c
> > > > +++ b/net/sched/sch_api.c
> > > > @@ -960,6 +960,17 @@ static struct Qdisc *qdisc_create(struct
> > > > net_device *dev,
> > > >
> > > > sch->handle = handle;
> > > >
> > > > + /* This exist to keep backward compatible with a userspace
> > > > + * loophole, what allowed userspace to get IFF_NO_QUEUE
> > > > + * facility on older kernels by setting tx_queue_len=0 (prior
> > > > + * to qdisc init), and then forgot to reinit tx_queue_len
> > > > + * before again attaching a qdisc.
> > > > + */
> > > > + if ((dev->priv_flags & IFF_NO_QUEUE) && (dev->tx_queue_len ==
> > > > 0)) {
> > > > + dev->tx_queue_len = DEFAULT_TX_QUEUE_LEN;
> > > > + netdev_info(dev, "Caught tx_queue_len zero
> > > > misconfig\n");
> > > > + }
> > >
> > > I wonder why this is limited to IFF_NO_QUEUE devices. Do you think there
> > > is a valid use case for physical ones?
> >
> > Hmmm, I cannot come up with a useful use-case for physical devices, but
> > I cannot see why we should save users that had used the loophole on
> > physical devices, as that is clearly a faulty config to begin with.
> > See net_crit_ratelimited warning here:
> > [1] https://github.com/torvalds/linux/blob/v4.9-rc3/net/core/dev.c#L3403
>
> I really feel like nit-picking again,
Perhaps a follow up patch is better? This patch does solve a real
issue.
> but what differs in between
> loophole users of virtual devices (whose broken scripts stopped working)
> and loophole users of physical devices (whose broken scripts stopped
> working as well)?
There is a difference. We basically closed the loophole config, but
fixed that qdisc can be attached to virtual (IFF_NO_QUEUE) devices,
without needing to adjusting tx_queue_len.
Thus, running a loophole-script have no-effect, but for IFF_NO_QUEUE
devices (veth specifically) it looks like it had the desired effect,
thus Docker will/can keep doing that, to work with older kernels, and
on newer kernels it just doesn't have any effect.
The remaining problem is that a "loophole-script" leaves the interface
in a broken state with tx_queue_len==0. Which this patch address.
So, why only catch misconfig for IFF_NO_QUEUE devices? Because a
loophole-script on veth brought it into a valid config, thus valid
use-case, while one a physical into a invalid config (hence the
critical warn[1]).
You could (in a followup patch, please) argue that it is a lot simpler,
just to always catch the misconfig of having tx_queue_len==0 when
attaching a qdisc.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
