mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc5-mm2 problem ?
Date: Mon, 05 Jun 2006 17:02:58 -0700	[thread overview]
Message-ID: <1149552178.26170.31.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <20060605114132.2f777060.akpm@osdl.org>

On Mon, 2006-06-05 at 11:41 -0700, Andrew Morton wrote:
> On Mon, 05 Jun 2006 09:37:40 -0700
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> 
> > Have you seen this on 2.6.17-rc5-mm2 before ? Could be due to my
> > patchset (fileop cleanups), but doesn't seem like it ..
> > 
> > Thanks,
> > Badari
> > 
> > Unable to handle kernel NULL pointer dereference at 0000000000000008
> > RIP:
> >  [<ffffffff80448d5f>] skb_dequeue+0x2c/0x50
> 
> It could be the LLC bug.  That thing caused untold amounts of grief.
> 
> --- devel/net/llc/llc_input.c~git-net-llc-fix	2006-06-02 11:55:38.000000000 -0700
> +++ devel-akpm/net/llc/llc_input.c	2006-06-02 11:55:38.000000000 -0700
> @@ -176,7 +176,6 @@ int llc_rcv(struct sk_buff *skb, struct 
>   		struct sk_buff *cskb = skb_clone(skb, GFP_ATOMIC);
>   		if (cskb)
>   			rcv(cskb, dev, pt, orig_dev);
> -		rcv(skb, dev, pt, orig_dev);
>  	}
>  	dest = llc_pdu_type(skb);
>  	if (unlikely(!dest || !llc_type_handlers[dest - 1]))
> _

Thanks. 2.6.17-rc5-mm3 is behaving much better, haven't seen these
issues on -mm3 with my patchset. I don't want to be the reason for
breaking -mm tree with fileop changes (I already used up my free
credits) ;)

Thanks,
Badari


      reply	other threads:[~2006-06-06  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 16:37 Badari Pulavarty
2006-06-05 18:41 ` Andrew Morton
2006-06-06  0:02   ` Badari Pulavarty [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=1149552178.26170.31.camel@dyn9047017100.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®