From: David Miller <davem@davemloft.net>
To: jarkao2@gmail.com
Cc: netdev@vger.kernel.org, shemminger@vyatta.com, kaber@trash.net,
franchoze@yandex.ru
Subject: Re: [PATCH 1/2] pkt_sched: Fix sch_sfq vs tc_modify_qdisc oops
Date: Wed, 11 Aug 2010 01:37:50 -0700 (PDT) [thread overview]
Message-ID: <20100811.013750.193698154.davem@davemloft.net> (raw)
In-Reply-To: <20100811083101.GA10126@ff.dom.local>
From: Jarek Poplawski <jarkao2@gmail.com>
Date: Wed, 11 Aug 2010 08:31:02 +0000
> After more investigation I've found sch_sfq is still vulnerable
> because off its missing class handlers. Here is an oops as
> proof of the concept, and a patch below. This patch should be
> considered for stable (without following 2/2 patch).
Thanks Jarek, both applied to net-2.6 and the first queued up
for -stable.
prev parent reply other threads:[~2010-08-11 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 8:31 [PATCH 1/2] pkt_sched: Fix sch_sfq vs tc_modify_qdisc oops Jarek Poplawski
2010-08-11 8:37 ` 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=20100811.013750.193698154.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=franchoze@yandex.ru \
--cc=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).