From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] lockup with multiple cake instances on 3.16.7
Date: Fri, 1 Feb 2019 00:23:29 +0100 [thread overview]
Message-ID: <7052193E-AB03-4FF7-9155-4CE62A43D22F@heistp.net> (raw)
In-Reply-To: <87ef8sifh0.fsf@toke.dk>
> On Feb 1, 2019, at 12:18 AM, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> (crossed streams; but yeah, basically the same conclusion)
Ok, crossed-crossed streams references it is… :)
>> Do you think this is a correct patch?
>
> Well, the "correct patch" would be to get upstream fixed :)
>
> But yeah, I don't think it would hurt to carry this as a workaround
> patch until that happens...
>
> I guess you could try running it for a while and see if anything else
> blows up? You seem to have quite a knack for getting it to fail... ;)
That sounds reasonable, let me see if I can break it in some different cases.
My guess is, past qdiscs didn’t manage to fill the tailroom space and cause this problem, but I’m not sure…
next prev parent reply other threads:[~2019-01-31 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 8:58 Pete Heist
2019-01-30 22:59 ` Toke Høiland-Jørgensen
2019-01-31 7:15 ` Pete Heist
2019-01-31 14:53 ` Toke Høiland-Jørgensen
2019-01-31 20:25 ` Pete Heist
2019-01-31 23:09 ` Toke Høiland-Jørgensen
2019-01-31 23:18 ` Pete Heist
2019-01-31 23:10 ` Pete Heist
2019-01-31 23:18 ` Toke Høiland-Jørgensen
2019-01-31 23:23 ` Pete Heist [this message]
2019-01-31 23:31 ` Toke Høiland-Jørgensen
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=7052193E-AB03-4FF7-9155-4CE62A43D22F@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--cc=toke@redhat.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