From: Veaceslav Falico <vfalico@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: thomas@glanzmann.de, netdev@vger.kernel.org, fubar@us.ibm.com,
andy@greyhouse.net, nikolay@redhat.com, robbat2@gentoo.org
Subject: Re: [BUG] v3.12-rc5-139-gbdeeab6 assertion failed at drivers/net/bonding/bond_main.c (3398)
Date: Thu, 7 Nov 2013 21:18:42 +0100 [thread overview]
Message-ID: <20131107201842.GC14694@redhat.com> (raw)
In-Reply-To: <20131107.151212.489598950578675166.davem@davemloft.net>
On Thu, Nov 07, 2013 at 03:12:12PM -0500, David Miller wrote:
>From: Veaceslav Falico <vfalico@redhat.com>
>Date: Thu, 7 Nov 2013 15:24:18 +0100
>
>> Sorry for bringing this up - completely my fault. There are further
>> reports
>> of this bug in mainline. I've read the
>> ./Documentation/networking/netdev-FAQ.txt but haven't seen a way to
>> get a
>> fix that got in net-next to the (correct) net tree.
>>
>> Is there any way to do it?
>>
>> Sorry again for the mess :-(.
>
>Since we're in the merge window the tree going to Linus next would
>be net-next, and the fix is there.
>
>Once it hits Linus's tree I can queue it up for -stable.
Awesome, please do, thank you.
And sorry again for the noise.
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-11-07 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 20:27 [BUG] v3.12-rc5-139-gbdeeab6 assertion failed at drivers/net/bonding/bond_main.c (3398) Thomas Glanzmann
2013-10-19 20:52 ` Veaceslav Falico
2013-10-19 22:44 ` David Miller
2013-11-07 14:24 ` Veaceslav Falico
2013-11-07 20:12 ` David Miller
2013-11-07 20:18 ` Veaceslav Falico [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131107201842.GC14694@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=robbat2@gentoo.org \
--cc=thomas@glanzmann.de \
/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;
as well as URLs for NNTP newsgroup(s).