From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <nbd@openwrt.org>
Received: from nbd.name (unknown [IPv6:2a01:4f8:131:30e2::2])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 9D28721F11C
	for <cerowrt-devel@lists.bufferbloat.net>;
	Sun, 13 Jan 2013 13:39:19 -0800 (PST)
Message-ID: <50F32981.9080404@openwrt.org>
Date: Sun, 13 Jan 2013 22:39:13 +0100
From: Felix Fietkau <nbd@openwrt.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Eric Dumazet <edumazet@google.com>
References: <CAA93jw5zUfm=5jhd3y=Z6jjZ-+1nEcE=f7OuKojBJT+PsUuPuw@mail.gmail.com>
	<CANn89i+W19eiH1o5MJjAe2nk-4=STCxQUhbM3XCu3=7FriZepQ@mail.gmail.com>
	<CAA93jw5pLRgM3EmHgHjzMUTYBcbDXzQd_DFJ4OLY5aA2ets8GA@mail.gmail.com>
	<CAMZR1YBs0w1r9T1S7A-Uin34tGMrY3y7oh0WqiZZ-SaXTeQMNA@mail.gmail.com>
	<CAA93jw5H=+fEvSqszB3oWQcfDhX8kFxeW5Ekm7gkCuU2hvDGnQ@mail.gmail.com>
	<CAPshTChm9Q6mZu+HiGmyP_=GQVS+LWb-r0ZyJ5v=pxZPK6_yQA@mail.gmail.com>
	<CAD6NSj5QtQ+fC2W3O_RxXKin8r=+6o+yYtmCVAinKeGPHsx6=Q@mail.gmail.com>
	<CAK6E8=cNGx379gbJGK_y76HSsEBUuz7kVUW3XYgq34630M1Ekg@mail.gmail.com>
	<CAD6NSj4xQF+jnoaMG+1BcUX57zSWMetJZEghS+r_9MHT+hk=9g@mail.gmail.com>
	<CAD6NSj6Q0vrpnPh24H8AwjzyEa55EiKt640CBptCaBMpkgwC_w@mail.gmail.com>
	<CAD6NSj6vMqU4zQzNgJVKm9=YwSmUi-KfgCiFdCzScc20PR+mJw@mail.gmail.com>
	<CANn89iKc8xju2hEzP11=+WjBwqxcD5j3jo3Ftavr=6jcn9KNGg@mail.gmail.com>
In-Reply-To: <CANn89iKc8xju2hEzP11=+WjBwqxcD5j3jo3Ftavr=6jcn9KNGg@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Jerry Chu <hkchu@google.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	Yuchung Cheng <ycheng@google.com>
Subject: Re: [Cerowrt-devel] TFO crashes cerowrt 3.7.1-1
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 21:39:19 -0000

On 2013-01-13 7:03 PM, Eric Dumazet wrote:
> I suspect a bug in the spin_is_locked() implementation on your arch, as
> he socket lock should be held at this point.
I don't think this is an arch implementation bug, this probably happens
on all !SMP systems. See this bit from include/linux/spinlock_up.h:

#define arch_spin_is_locked(lock)   ((void)(lock), 0)

- Felix