[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <52A6BAC6.4090407@samsung.com>
Date: Tue, 10 Dec 2013 07:55:02 +0100
From: Andrzej Pietrasiewicz <andrzej.p@...sung.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Felipe Balbi <balbi@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Michal Nazarewicz <mina86@...a86.com>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org
Subject: Re: [PATCH] net: sk == 0xffffffff fix - not for commit
W dniu 09.12.2013 16:31, Eric Dumazet pisze:
> On Mon, 2013-12-09 at 12:47 +0100, Andrzej Pietrasiewicz wrote:
>> NOT FOR COMMITTING TO MAINLINE.
>>
>> With g_ether loaded the sk occasionally becomes 0xffffffff.
>> It happens usually after transferring few hundreds of kilobytes to few
>> tens of megabytes. If sk is 0xffffffff then dereferencing it causes
>> kernel panic.
>>
>> This is a *workaround*. I don't know enough net code to understand the core
>> of the problem. However, with this patch applied the problems are gone,
>> or at least pushed farther away.
>
> Is it happening on SMP or UP ?
UP build, S5PC110
>
> Crash should happen earlier in __inet_lookup_established()
>
>
>
AP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists