netdev - [PATCH net-next 0/7] clear old options when old qdisc's replaced

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-next>] [day] [month] [year] [list]

Message-ID: <1392366970-11592-1-git-send-email-yangyingliang@huawei.com>
Date:	Fri, 14 Feb 2014 16:36:03 +0800
From:	Yang Yingliang <yangyingliang@...wei.com>
To:	<netdev@...r.kernel.org>
CC:	<davem@...emloft.net>, <stephen@...workplumber.org>
Subject: [PATCH net-next 0/7] clear old options when old qdisc's replaced

I've added a netem qdisc with rate option, then I replace this qdisc
without rate option but with latency option. The rate option is still
there.

E.g.
  # tc qdisc add dev eth4 handle 1: root netem rate 10mbit
  # tc qdisc show
    qdisc netem 1: dev eth4 root refcnt 2 limit 1000 rate 10Mbit

  # tc qdisc replace dev eth4 handle 1: root netem latency 10ms
  # tc qdisc show
    qdisc netem 1: dev eth4 root refcnt 2 limit 1000 delay 10.0ms rate 10Mbit

The old options need be cleared after the qdisc is replaced.

Yang Yingliang (7):
  sch_netem: clear old clgstate when old qdisc's replaced
  sch_netem: clear old dist table when old qdisc's replaced
  sch_netem: clear old reorder when old qdisc's replaced
  sch_netem: clear old correlation when old qdisc's replaced
  sch_netem: clear old corrupt when old qdisc's replaced
  sch_netem: clear old rate when old qdisc's replaced
  sch_netem: clear old ecn when old qdisc's replaced

 net/sched/sch_netem.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

-- 
1.8.0


--
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