From: Cong Wang <xiyou.wangcong@gmail.com>
To: Kelly Anderson <kelly@xilka.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Daniel Borkmann <dborkman@redhat.com>
Subject: Re: 3.14 tc oops
Date: Mon, 19 May 2014 12:14:26 -0700 [thread overview]
Message-ID: <CAM_iQpVseFM9aHhOd-SRFUPtsxjdaAv2cpJ-BwwLotirB9rH_A@mail.gmail.com> (raw)
In-Reply-To: <2501516.A9ihW45TvK@comer>
On Fri, May 16, 2014 at 8:28 PM, Kelly Anderson <kelly@xilka.com> wrote:
> On Friday, May 16, 2014 17:18:52 Cong Wang wrote:
>> On Mon, Apr 7, 2014 at 1:00 AM, Kelly Anderson <kelly@xilka.com> wrote:
>> > Cong,
>> >
>> > The patch did not fix the problem.
>> >
>> > For your convenience, I've attached tc filter show for eth0 and eth1, as
>> > well as a mangled version of my tcng input file.
>>
>> Sorry that I totally forgot this thread....
>>
>> I just tested a new patch (attached), it works for me, please verify it.
>>
>> Thanks for the report anyway.
>
> Great, the new patch seems to work fine with 3.14.4. If you haven't done it
> yet, you should probably get that patch pulled into 3.14 stable.
>
OK. I will send a formal patch and I believe David will queue it for
3.14 stable.
Thanks!
prev parent reply other threads:[~2014-05-19 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1592838.91HrDxMk9i@comer>
[not found] ` <CAM_iQpVgEtDqbK6-JoMn8-1D_cOsRTGPozvbmxbCBKi1+ss-rQ@mail.gmail.com>
[not found] ` <CAM_iQpU+A+1FxFNkibvbkM=vkWVw7QmHJzE_AODVTgzUEjdeDg@mail.gmail.com>
2014-04-07 9:08 ` 3.14 tc oops Daniel Borkmann
2014-04-07 10:16 ` Kelly Anderson
2014-05-16 6:41 ` Kelly Anderson
2014-05-16 8:45 ` Daniel Borkmann
[not found] ` <3222104.QGqslXqjVx@comer>
2014-05-17 0:18 ` Cong Wang
2014-05-17 0:24 ` Cong Wang
2014-05-17 3:28 ` Kelly Anderson
2014-05-19 19:14 ` Cong Wang [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=CAM_iQpVseFM9aHhOd-SRFUPtsxjdaAv2cpJ-BwwLotirB9rH_A@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=dborkman@redhat.com \
--cc=kelly@xilka.com \
--cc=netdev@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).