From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: bugme-daemon@bugzilla.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Bugme-new] [Bug 9543] New: RTNL: assertion failed at net/ipv6/addrconf.c (2164)/RTNL: assertion failed at net/ipv4/devinet.c (1055)
Date: Tue, 11 Dec 2007 12:30:27 -0800 [thread overview]
Message-ID: <20071211123027.cd4faa19.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712111603250.21312@bizon.gios.gov.pl>
On Tue, 11 Dec 2007 16:04:27 +0100 (CET) Krzysztof Oledzki <olel@ans.pl> wrote:
> >> [<783bfa72>] rt_run_flush+0x43/0x8b
> >> [<783bfa93>] rt_run_flush+0x64/0x8b
> >> [<7813ac54>] notifier_call_chain+0x2a/0x52
> >> [<7813ac9e>] raw_notifier_call_chain+0x17/0x1a
> >> [<783a3471>] netdev_state_change+0x18/0x29
> >> [<783ac6a9>] __linkwatch_run_queue+0x150/0x17e
> >> [<783ac6f4>] linkwatch_event+0x1d/0x22
> >> [<78133cdf>] run_workqueue+0xdb/0x1b6
> >> [<78133c8b>] run_workqueue+0x87/0x1b6
> >> [<783ac6d7>] linkwatch_event+0x0/0x22
> >> [<781346ff>] worker_thread+0x0/0x85
> >> [<78134778>] worker_thread+0x79/0x85
> >> [<781371ad>] autoremove_wake_function+0x0/0x35
> >> [<781370f6>] kthread+0x38/0x5e
> >> [<781370be>] kthread+0x0/0x5e
> >> [<78104baf>] kernel_thread_helper+0x7/0x10
> >> =======================
> >> RTNL: assertion failed at net/ipv6/addrconf.c (1610)
> >
> >
> > Hopefully this is due to the bug you reported in bug #9542.
> >
> > Does this patch fix both issues?
>
> Unfortunately not. I just updated bugzilla.
argh. Please conduct these discussions via emailed reply-to-all, not via
the bugzilla web interface.
I think my patch _did_ fix http://bugzilla.kernel.org/show_bug.cgi?id=9542
But then you hit a new bonding locking bug.
Rafael, please track 9542 and 9543 as post-2.6.23 regressions, thanks.
next prev parent reply other threads:[~2007-12-11 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9543-10286@http.bugzilla.kernel.org/>
2007-12-11 11:46 ` [Bugme-new] [Bug 9543] New: RTNL: assertion failed at net/ipv6/addrconf.c (2164)/RTNL: assertion failed at net/ipv4/devinet.c (1055) Andrew Morton
2007-12-11 15:04 ` Krzysztof Oledzki
2007-12-11 20:30 ` Andrew Morton [this message]
2007-12-12 13:31 ` Herbert Xu
2007-12-12 17:46 ` Jay Vosburgh
2007-12-12 19:07 ` Andy Gospodarek
2007-12-14 16:14 ` Krzysztof Oledzki
2007-12-14 18:26 ` Andy Gospodarek
2007-12-14 18:57 ` Krzysztof Oledzki
2007-12-14 22:03 ` Andy Gospodarek
2007-12-14 22:11 ` Krzysztof Oledzki
2007-12-14 22:27 ` Andy Gospodarek
2007-12-18 19:52 ` Krzysztof Oledzki
2007-12-14 22:47 ` Andy Gospodarek
2007-12-15 4:10 ` Herbert Xu
2007-12-15 15:09 ` Andy Gospodarek
2007-12-16 2:27 ` Herbert Xu
2007-12-16 3:17 ` Andy Gospodarek
2007-12-16 3:23 ` Herbert Xu
2007-12-18 19:53 ` Krzysztof Oledzki
2007-12-19 14:42 ` Andy Gospodarek
2008-01-07 17:57 ` Krzysztof Oledzki
2008-01-07 20:26 ` Andy Gospodarek
2008-01-07 20:40 ` Jay Vosburgh
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=20071211123027.cd4faa19.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=olel@ans.pl \
--cc=rjw@sisk.pl \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).