Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] BUG_ON vs WARN_ON
Date: Fri, 7 Oct 2016 14:27:32 +0100	[thread overview]
Message-ID: <e23f1aca-84fc-4a9c-16b5-dab1e284cb00@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <F6651CB5-9759-4CD6-A83C-89E372EE3030@gmail.com>



On 05/10/16 19:53, Jonathan Morton wrote:
>>> I wonder what it was that caused yesterday's issues?  I really
>>> must try again when I've more time to get proper access.
>>
>> I’m having trouble reproducing it here.  I know one of my boxes
>> froze the very first time I loaded it, but it’s been running fine
>> ever since.  Another machine is currently refusing to insert the
>> module, claiming a wrong exec format.  It’s all a bit bizarre.
>>
>> I do have a few more avenues of enquiry to explore, though.
>
> Aha - I managed to capture a kernel panic, which appears to trace to
> the lookup in the accelerator array.  It’s a read-only access, so it
> only panics if it hits unpaged memory, rather than corrupting
> anything.  Of course, if it reads outside the array, it’ll increment
> the deficit by a random value, but that usually won’t prevent traffic
> flowing.
>
> The lookup is indexed on the host refcnt, which I’m using as the
> count of flows attached to that host.  It seems likely that it isn’t
> being maintained correctly in all cases, so it can wrap around past
> zero very soon after being attached, without needing much traffic.
>
> I’ll try to fix that, and put a sanity check in as well to be
> certain.

It's now ok...so far :-)


  reply	other threads:[~2016-10-07 13:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 15:24 Kevin Darbyshire-Bryant
2016-10-05 15:42 ` Jonathan Morton
2016-10-05 15:45   ` Kevin Darbyshire-Bryant
2016-10-05 15:53     ` Jonathan Morton
2016-10-05 18:53       ` Jonathan Morton
2016-10-07 13:27         ` Kevin Darbyshire-Bryant [this message]
2016-10-07 13:35           ` Jonathan Morton
2016-10-07 13:43             ` Kevin Darbyshire-Bryant
2016-10-05 15:53     ` Dave Taht
2016-10-05 15:55       ` Kevin Darbyshire-Bryant
2016-10-05 15:57         ` Jonathan Morton
2016-10-05 16:38           ` Dave Taht
2016-10-06  3:59             ` Kevin Darbyshire-Bryant
2016-10-06  4:19               ` Dave Taht
2016-10-06  8:12                 ` Jonathan Morton

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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=e23f1aca-84fc-4a9c-16b5-dab1e284cb00@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox