From: Daniel Borkmann <daniel@iogearbox.net>
To: Vijay Subramanian <subramanian.vijay@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, tgraf <tgraf@suug.ch>
Subject: Re: Kernel crash while using tc script
Date: Tue, 19 May 2015 23:43:14 +0200 [thread overview]
Message-ID: <555BAE72.40609@iogearbox.net> (raw)
In-Reply-To: <CAGK4HS_cCQPJwXVoCuZAa2zHtPnXO+ar5Wpg_azyxc5Efv4Mwg@mail.gmail.com>
On 05/19/2015 10:11 PM, Vijay Subramanian wrote:
> Hi,
>
> It seems latest net-next kernel crashes while unloading modules.
> Please see simple script below to reproduce the crash.
>
> ===============================
>
> #!/bin/bash
>
> while true; do
>
> # modules will be loaded automatically
>
> tc qdisc add dev eth1 root handle 1: prio
>
> tc filter add dev eth1 parent 1: u32 match u32 0 0 flowid 1
>
>
> tc qdisc del dev eth1 root
>
> rmmod cls_u32
>
> rmmod sch_prio
>
>
> done
>
> =========================
>
> It seems there is some refcounting or locking issue issue. I am unable
> to easily post the dump but sometimes it points to crashes in various
> functions in prio_class_ops (sch_prio.c), such as prio_walk(),
> prio_dump_class etc. Probably, sch_prio call back functions are
> invoked when they should not be.
>
> I bisected this down to following commit:
>
> commit 78fd1d0ab072d4d9b5f0b7c14a1516665170b565
> Author: Thomas Graf <tgraf@suug.ch>
> Date: Tue Oct 21 22:05:38 2014 +0200
> netlink: Re-add locking to netlink_lookup() and seq walker
>
> If there are suggestions for me to try or you need more info, let me know.
Hmm, seems rather like the synchronize_net() removal in netlink_release()
must have uncovered a bug elsewhere.
next prev parent reply other threads:[~2015-05-19 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 20:11 Kernel crash while using tc script Vijay Subramanian
2015-05-19 21:43 ` Daniel Borkmann [this message]
2015-05-20 11:53 ` Daniel Borkmann
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=555BAE72.40609@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=subramanian.vijay@gmail.com \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.