From: Cong Wang <amwang@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: stephen hemminger <shemminger@vyatta.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Thomas Graf <tgraf@redhat.com>,
rizzo@iet.unipi.it
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in qfq_dequeue()
Date: Fri, 12 Oct 2012 09:25:04 +0800 [thread overview]
Message-ID: <1350005104.31369.0.camel@cr0> (raw)
In-Reply-To: <1349968843.21172.9508.camel@edumazet-glaptop>
On Thu, 2012-10-11 at 17:20 +0200, Eric Dumazet wrote:
>
> I just realize its a 2.6.32 redhat kernel, while QFQ is a 3.0 addition.
>
> Can you reproduce the bug on current kernel (3.6 or git tree)
>
Sure, the gdb backtrace is from the latest -net kernel.
prev parent reply other threads:[~2012-10-12 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 9:15 BUG: unable to handle kernel NULL pointer dereference in qfq_dequeue() Cong Wang
2012-10-11 8:38 ` Cong Wang
2012-10-11 15:05 ` Eric Dumazet
2012-10-11 15:20 ` Eric Dumazet
2012-10-12 1:25 ` 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=1350005104.31369.0.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rizzo@iet.unipi.it \
--cc=shemminger@vyatta.com \
--cc=tgraf@redhat.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).