Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Yuchung Cheng <ycheng@google.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Jerry Chu <hkchu@google.com>, Eric Dumazet <edumazet@google.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] TFO crashes cerowrt 3.7.1-1
Date: Sun, 13 Jan 2013 16:38:38 -0800	[thread overview]
Message-ID: <CAK6E8=faYUi9Z9XfYtQY9h1PDt7ddfFFC-J4PYae4OXcVT6bxA@mail.gmail.com> (raw)
In-Reply-To: <50F32981.9080404@openwrt.org>

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

Thanks for making these efforts to debug this. Ketan: can we try replace
the one BUG_ON with two WARN_ON  to confirm the exact faulty condition? I
wish I can do that myself but I don't have a box at hand.

Yuchung

On Sun, Jan 13, 2013 at 1:39 PM, Felix Fietkau <nbd@openwrt.org> wrote:

> 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
>
>

[-- Attachment #2: Type: text/html, Size: 1081 bytes --]

  reply	other threads:[~2013-01-14  0:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 17:04 Dave Taht
2013-01-04 17:27 ` Eric Dumazet
2013-01-04 17:33   ` Dave Taht
2013-01-04 20:42     ` Maciej Soltysiak
2013-01-04 20:43       ` Maciej Soltysiak
2013-01-04 20:57         ` Jerry Chu
2013-01-04 21:21           ` Dave Taht
2013-01-04 21:36             ` Jerry Chu
2013-01-04 21:44               ` Dave Taht
2013-01-04 21:01         ` dpreed
2013-01-04 22:49           ` Robert Bradley
2013-01-04 21:11       ` Dave Taht
2013-01-04 21:19         ` Jerry Chu
2013-01-05  1:59           ` Ketan Kulkarni
2013-01-05  2:20             ` Yuchung Cheng
2013-01-05  3:02               ` Ketan Kulkarni
2013-01-05  3:16                 ` Eric Dumazet
2013-01-05  3:35                 ` Dave Taht
2013-01-05  4:05                   ` Dave Taht
2013-01-05 19:13                 ` Ketan Kulkarni
2013-01-13 17:01                   ` Ketan Kulkarni
2013-01-13 18:03                     ` Eric Dumazet
2013-01-13 21:39                       ` Felix Fietkau
2013-01-14  0:38                         ` Yuchung Cheng [this message]
2013-01-14  3:05                         ` Eric Dumazet
2013-01-14  4:07                           ` Eric Dumazet
2013-01-14  4:43                             ` Ketan Kulkarni
2013-01-14  6:14                               ` Dave Taht
2013-01-14 19:50                                 ` Dave Taht
2013-01-14  8:18                           ` Jerry Chu
2013-01-14 16:32                             ` Eric Dumazet
2013-01-04 22:25       ` Robert Bradley
2013-01-14  6:11       ` Dave Taht
2013-01-14 16:37         ` Ketan Kulkarni
2013-01-16 22:19         ` Maciej Soltysiak
2013-01-17  0:58           ` Dave Taht
2013-01-17  3:44           ` Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK6E8=faYUi9Z9XfYtQY9h1PDt7ddfFFC-J4PYae4OXcVT6bxA@mail.gmail.com' \
    --to=ycheng@google.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=edumazet@google.com \
    --cc=hkchu@google.com \
    --cc=nbd@openwrt.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