public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cong Wang <amwang@redhat.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: Thu, 11 Oct 2012 17:20:43 +0200	[thread overview]
Message-ID: <1349968843.21172.9508.camel@edumazet-glaptop> (raw)
In-Reply-To: <1349967908.21172.9459.camel@edumazet-glaptop>

On Thu, 2012-10-11 at 17:05 +0200, Eric Dumazet wrote:
> On Thu, 2012-10-11 at 16:38 +0800, Cong Wang wrote:
> > On Mon, 2012-10-08 at 17:15 +0800, Cong Wang wrote:
> > > Hi, all,
> > > 
> > > We got the following kernel crash on RHEL6 and I confirmed upstream has
> > > the same problem (I didn't save this kernel log though):
> > 
> > Ok, I got the backtrace of the latest kernel, see below. Seems
> > qfq_slot_scan() in qfq_dequeue() returns something bad, 'cl' becomes
> > '0x10'.
> 
> not exactly, cl is -0x50
> 

> > 
> 
> 
> static struct qfq_class *qfq_slot_head(struct qfq_group *grp)
> {
>         return hlist_entry(grp->slots[grp->front].first,
>                            struct qfq_class, next);
> }
> 
> 
> problem is : grp->slots[grp->front].first is NULL here,
> 
> so we return RAX = -offsetof(struct qfq_class, next)
> 
> (ie -0x50 : ffffffffffffffb0)
> 
> 
> So one bit is set in full_slots while the corresponding slots[] is
> empty.
> 
> I wonder if qfq_slot_remove() is correct ?


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)

  reply	other threads:[~2012-10-11 15:20 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 [this message]
2012-10-12  1:25       ` 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=1349968843.21172.9508.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --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