netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedorysychenko <nuclearcat@nuclearcat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	krkumar2@in.ibm.com, netdev@vger.kernel.org
Subject: Re: NULL pointer dereference panic in stable (2.6.33.2), amd64
Date: Thu, 29 Apr 2010 13:50:08 +0300	[thread overview]
Message-ID: <201004291350.08620.nuclearcat@nuclearcat.com> (raw)
In-Reply-To: <1271327830.16881.2370.camel@edumazet-laptop>

On Thursday 15 April 2010 13:37:10 Eric Dumazet wrote:
> Le jeudi 15 avril 2010 à 12:11 +0300, Denys Fedorysychenko a écrit :
> > Btw i have application using tun.
> 
> Could you add following sanity test to catch the error ?
> 
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index fa8b476..b67274a 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -988,6 +988,7 @@ static inline
>  struct netdev_queue *netdev_get_tx_queue(const struct net_device *dev,
>  					 unsigned int index)
>  {
> +	WARN_ON(index >= dev->num_tx_queues);
>  	return &dev->_tx[index];
>  }
> 
Very sorry for being late, just i found way to stabilize kernel for me and to 
solve my personal life issues. It took 2 weeks...
I will try this patch, but i'm sure i dont have multiqueue card there.

I had shaper on eth0.33 and eth0 so i disable all offloading except 
checksumming there. Recently i found  that on some interfaces (where is no 
shaper) gso left on. And yes, probably some traffic was queued, then route 
changed, and maybe it went from gso off interface to gso on... 
It can be just pure luck, that i dont have crashes anymore, but maybe trick is 
in gso...

  reply	other threads:[~2010-04-30 16:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 20:38 NULL pointer dereference panic in stable (2.6.33.2), amd64 Denys Fedorysychenko
2010-04-11 22:35 ` Eric Dumazet
2010-04-11 23:04   ` Denys Fedorysychenko
2010-04-11 23:11     ` Eric Dumazet
2010-04-11 23:36       ` Denys Fedorysychenko
2010-04-12  3:38   ` Krishna Kumar2
2010-04-12  6:01     ` Eric Dumazet
2010-04-12  7:18       ` Eric Dumazet
2010-04-12  7:36         ` David Miller
2010-04-15  6:52         ` David Miller
2010-04-15  8:02           ` Eric Dumazet
2010-04-15  8:26             ` David Miller
2010-04-15  8:51               ` Eric Dumazet
2010-04-15  9:06                 ` David Miller
2010-04-15  9:11                   ` Denys Fedorysychenko
2010-04-15 10:37                     ` Eric Dumazet
2010-04-29 10:50                       ` Denys Fedorysychenko [this message]
2010-04-15 20:30                   ` Eric Dumazet
2010-04-15 20:46                     ` Eric Dumazet
2010-04-15 21:33                       ` David Miller
2010-04-16 22:18                         ` [PATCH net-next-2.6] net: Introduce skb_orphan_try() Eric Dumazet
2010-04-18  9:46                           ` David Miller
2010-04-21  6:08                             ` Eric Dumazet
2010-04-22  5:56                               ` David Miller
2010-04-22  7:10                                 ` Eric Dumazet
2010-04-22  7:16                                   ` David Miller
2010-04-22  7:24                                     ` Eric Dumazet
2010-04-22  7:26                                       ` David Miller
2010-04-22  7:33                                         ` Eric Dumazet
2010-04-22  7:41                                           ` David Miller
2010-04-22  7:47                                             ` Eric Dumazet
2010-04-22  7:54                                               ` David Miller
2010-04-22  7:59                                                 ` Eric Dumazet
2010-04-12  7:54       ` NULL pointer dereference panic in stable (2.6.33.2), amd64 Krishna Kumar2
2010-04-12  9:31         ` Eric Dumazet
2010-04-12 16:11           ` Denys Fedorysychenko
2010-04-12 20:09             ` Eric Dumazet

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=201004291350.08620.nuclearcat@nuclearcat.com \
    --to=nuclearcat@nuclearcat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).