netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Kelly Anderson <kelly@xilka.com>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: 3.14 tc oops
Date: Mon, 07 Apr 2014 11:08:47 +0200	[thread overview]
Message-ID: <53426B1F.9050405@redhat.com> (raw)
In-Reply-To: <CAM_iQpU+A+1FxFNkibvbkM=vkWVw7QmHJzE_AODVTgzUEjdeDg@mail.gmail.com>

[Kelly, please also cc netdev]

On 04/07/2014 07:56 AM, Cong Wang wrote:
> On Thu, Apr 3, 2014 at 9:24 AM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
>> On Wed, Apr 2, 2014 at 7:24 AM, Kelly Anderson <kelly@xilka.com> wrote:
>>> Hi,
>>>
>>> I hit a kernel oops when starting traffic control on my armv7 router, I don't
>>> think the architecture is related, the same tc code worked perfectly with
>>> earlier kernel versions, i.e. 3.13.x.
>>>
>>> I also attached an object dump with line numbers to make identifying the
>>> problem a bit easier.
>>>
>>> Please cc me to keep me in the loop, I can test patches.
>>
>>
>> Thanks for the report! Looks like it is caused by one of my patches,
>> I will look into this shortly.
>>
>
> Which tc filter are you using on that htb qdisc? (tc filter show dev ....)
>
> I suspect it's tcindex filter, if so please try the following patch:
>
> diff --git a/net/sched/cls_tcindex.c b/net/sched/cls_tcindex.c
> index eed8404..14618cc 100644
> --- a/net/sched/cls_tcindex.c
> +++ b/net/sched/cls_tcindex.c
> @@ -298,8 +298,10 @@ tcindex_set_parms(struct net *net, struct
> tcf_proto *tp, unsigned long base,
>          tcf_exts_change(tp, &cr.exts, &e);
>
>          tcf_tree_lock(tp);
> -       if (old_r && old_r != r)
> +       if (old_r && old_r != r) {
>                  memset(old_r, 0, sizeof(*old_r));
> +               tcf_exts_init(&old_r->exts, TCA_TCINDEX_ACT,
> TCA_TCINDEX_POLICE);
> +       }
>
>          memcpy(p, &cp, sizeof(cp));
>          memcpy(r, &cr, sizeof(cr));
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

       reply	other threads:[~2014-04-07  9:08 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     ` Daniel Borkmann [this message]
2014-04-07 10:16     ` 3.14 tc oops 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

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=53426B1F.9050405@redhat.com \
    --to=dborkman@redhat.com \
    --cc=kelly@xilka.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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).