All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: netdev <netdev@vger.kernel.org>,
	serue@linux.vnet.ibm.com, David Miller <davem@davemloft.net>,
	matthltc@us.ibm.com, Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [2.6.30-git21] Network Namespace test failure
Date: Thu, 25 Jun 2009 11:08:30 +0530	[thread overview]
Message-ID: <4A430D56.5080406@in.ibm.com> (raw)
In-Reply-To: <20090625033847.GA27181@us.ibm.com>

Serge E. Hallyn wrote:
> Indeed the following patch fixes it on my end.  Sachin can you give
> this one a shot?
>
> thanks,
> -serge
>
> From 7193023ad09dbc4b57909c0204c19ed93472cd9e Mon Sep 17 00:00:00 2001
> From: root <root@elm3b203.beaverton.ibm.com>
> Date: Wed, 24 Jun 2009 20:26:17 -0700
> Subject: [PATCH 1/1] veth: don't free priv->status until dev->destructor
>
> Since commit ae0e8e82205c903978a79ebf5e31c670b61fa5b4, priv->status
> has been freed at veth_close().  But that causes a NULL deref at
> veth_xmit.  This patch moves priv->status free back to the device
> destructor.
>
> Signed-off-by: Serge Hallyn <serue@us.ibm.com>
> ---
Yes this fixed the problem for me.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------


  parent reply	other threads:[~2009-06-25  5:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 13:50 [2.6.30-git21] Network Namespace test failure Sachin Sant
2009-06-24 14:00 ` Serge E. Hallyn
2009-06-24 14:32   ` Sachin Sant
2009-06-25  3:14     ` Serge E. Hallyn
2009-06-25  3:38       ` Serge E. Hallyn
2009-06-25  3:46         ` Serge E. Hallyn
2009-06-25  5:38         ` Sachin Sant [this message]
2009-06-25  9:49         ` David Miller

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=4A430D56.5080406@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=davem@davemloft.net \
    --cc=matthltc@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=serue@linux.vnet.ibm.com \
    --cc=serue@us.ibm.com \
    --cc=shemminger@vyatta.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 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.