stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: phil@nwl.cc
Cc: mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
	jhs@mojatatu.com, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [net PATCH] IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
Date: Thu, 18 Feb 2016 14:57:35 -0500 (EST)	[thread overview]
Message-ID: <20160218.145735.320352771512551627.davem@davemloft.net> (raw)
In-Reply-To: <1455719863-25730-1-git-send-email-phil@nwl.cc>

From: Phil Sutter <phil@nwl.cc>
Date: Wed, 17 Feb 2016 15:37:43 +0100

> My implementation around IFF_NO_QUEUE driver flag assumed that leaving
> tx_queue_len untouched (specifically: not setting it to zero) by drivers
> would make it possible to assign a regular qdisc to them without having
> to worry about setting tx_queue_len to a useful value. This was only
> partially true: I overlooked that some drivers don't call ether_setup()
> and therefore not initialize tx_queue_len to the default value of 1000.
> Consequently, removing the workarounds in place for that case in qdisc
> implementations which cared about it (namely, pfifo, bfifo, gred, htb,
> plug and sfb) leads to problems with these specific interface types and
> qdiscs.
> 
> Luckily, there's already a sanitization point for drivers setting
> tx_queue_len to zero, which can be reused to assign the fallback value
> most qdisc implementations used, which is 1.
> 
> Fixes: 348e3435cbefa ("net: sched: drop all special handling of tx_queue_len == 0")
> Tested-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Signed-off-by: Phil Sutter <phil@nwl.cc>

Applied and queued up for -stable, thanks.

      reply	other threads:[~2016-02-18 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  0:56 [PATCH] Revert "net: sched: drop all special handling of tx_queue_len == 0" Mathieu Desnoyers
2016-02-17 12:47 ` Phil Sutter
2016-02-17 13:57   ` Mathieu Desnoyers
2016-02-17 13:58     ` Phil Sutter
2016-02-17 14:37     ` [net PATCH] IFF_NO_QUEUE: Fix for drivers not calling ether_setup() Phil Sutter
2016-02-18 19:57       ` David Miller [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=20160218.145735.320352771512551627.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).