All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Eric B Munson <emunson@mgebm.net>,
	David Miller <davem@davemloft.net>,
	dave@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	gregkh@suse.de, ksrinivasan@novell.com,
	NetDev <netdev@vger.kernel.org>
Subject: Re: 2.6.39-rc2 boot crash
Date: Tue, 12 Apr 2011 17:39:51 +0200	[thread overview]
Message-ID: <4DA47247.20700@trash.net> (raw)
In-Reply-To: <4DA44A73.3060801@trash.net>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On 12.04.2011 14:49, Patrick McHardy wrote:
> On 12.04.2011 00:06, Evgeniy Polyakov wrote:
>> Hi.
>>
>> On Mon, Apr 11, 2011 at 05:07:47PM -0400, Eric B Munson (emunson@mgebm.net) wrote:
>>>> I can't figure this out, the only thing that should have changed is the
>>>> time the initial PROC_CN_MCAST_LISTEN message is received. Apparently
>>>> at that point connector is not fully initialized yet. Please post your
>>>> config and the full boot log. Thanks.
>>>>
>>>
>>> I am still seeing this on Linus' tree, is there anything more I can do to help
>>> track the problem?
> 
> Sorry, I had a hardware failure, I'm back working on this now.
> 
>> Patrick, do you need my assist on this bug?
> 
> Thanks, but I can meanwhile reproduce the problem, so I think I
> should have a fix soon.

I think this patch should fix the problem. Eric, could you please
give it a try?




[-- Attachment #2: cn.diff --]
[-- Type: text/x-patch, Size: 838 bytes --]

commit ad676e0dbbe8658ce46e192f449689bf3011bdf5
Author: Patrick McHardy <kaber@trash.net>
Date:   Tue Apr 12 17:37:04 2011 +0200

    connector: fix skb double free in cn_rx_skb()
    
    When a skb is delivered to a registered callback, cn_call_callback()
    incorrectly returns -ENODEV after freeing the skb, causing cn_rx_skb()
    to free the skb a second time.
    
    Reported-by: Eric B Munson <emunson@mgebm.net>
    Signed-off-by: Patrick McHardy <kaber@trash.net>

diff --git a/drivers/connector/connector.c b/drivers/connector/connector.c
index d770058..219d88a 100644
--- a/drivers/connector/connector.c
+++ b/drivers/connector/connector.c
@@ -142,6 +142,7 @@ static int cn_call_callback(struct sk_buff *skb)
 		cbq->callback(msg, nsp);
 		kfree_skb(skb);
 		cn_queue_release_callback(cbq);
+		err = 0;
 	}
 
 	return err;

  reply	other threads:[~2011-04-12 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 18:47 2.6.39-rc2 boot crash Eric B Munson
2011-04-06 18:52 ` Dave Hansen
2011-04-06 21:20   ` Eric B Munson
2011-04-06 21:21     ` David Miller
2011-04-06 22:05       ` Eric B Munson
2011-04-07 11:06         ` Patrick McHardy
2011-04-07 11:06           ` Patrick McHardy
2011-04-07 14:17           ` Eric B Munson
2011-04-11 21:07           ` Eric B Munson
2011-04-11 22:06             ` Evgeniy Polyakov
2011-04-12 12:49               ` Patrick McHardy
2011-04-12 15:39                 ` Patrick McHardy [this message]
2011-04-12 15:59                   ` Eric B Munson
2011-04-12 21:39                   ` 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=4DA47247.20700@trash.net \
    --to=kaber@trash.net \
    --cc=dave@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=emunson@mgebm.net \
    --cc=gregkh@suse.de \
    --cc=ksrinivasan@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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.