netdev - Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1KKZxj-0000vD-00@gondolin.me.apana.org.au>
Date:	Sun, 20 Jul 2008 22:32:35 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	davem@...emloft.net (David Miller)
Cc:	kaber@...sh.net, hadi@...erus.ca, netdev@...r.kernel.org,
	johannes@...solutions.net, linux-wireless@...r.kernel.org
Subject: Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU.

David Miller <davem@...emloft.net> wrote:
> 
> Are we really really sure it's OK to let users do this?  :)

Well security questions aside, I have seen this used on routers
to ensure certain traffic (e.g., VOIP) get preferential treatment
when it comes to transmission.

Of course some of these routers setup custom qdiscs so they wouldn't
be affected, but there may be ones out there relying on the default
pfifo.

Now I understand that having a pfifo is an anathema to multi-queue TX
by definition.  However, even if we couldn't preserve the full
semantics by default, if we could at least preserve the ordering
within each queue it would still be a plus.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html