From: Jarek Poplawski <jarkao2@gmail.com>
To: Mathieu SEGAUD <mathieu.segaud@regala.cx>
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au, kernel@gentoo.org
Subject: Re: Lockup with tun/tap/bridge interface deregistration.
Date: Thu, 11 Dec 2008 10:24:21 +0000 [thread overview]
Message-ID: <20081211102421.GB4129@ff.dom.local> (raw)
In-Reply-To: <87fxkwhyyq.fsf@barad-dur.regala.cx>
On 10-12-2008 15:44, Mathieu SEGAUD wrote:
> Hi,
>
> we are experiencing some "virtual" network interfaces problem, especially
> with tun/tap devices and with bridges, which occasionally get stuck and
> won't deregister and hang the destroying process for very long time.
...
> [<c0266b41>] netdev_run_todo+0xf7/0x19d
> [<f8a7f3c5>] br_del_bridge+0x48/0x4c [bridge]
> [<f8a7ff61>] br_ioctl_deviceless_stub+0x190/0x19f [bridge]
> [<c018a66c>] inotify_d_instantiate+0x12/0x3a
> [<c02e5c1b>] _spin_unlock+0xc/0x1f
> [<f8a7fdd1>] br_ioctl_deviceless_stub+0x0/0x19f [bridge]
> [<c025bf6e>] sock_ioctl+0x11f/0x1d9
> [<c025be4f>] sock_ioctl+0x0/0x1d9
> [<c0170cdc>] vfs_ioctl+0x1c/0x5f
> [<c0170f47>] do_vfs_ioctl+0x228/0x23b
> [<c025d76f>] sys_socketcall+0x51/0x19d
> [<c0170f86>] sys_ioctl+0x2c/0x42
> [<c01038a9>] sysenter_do_call+0x12/0x25
> [<c02e0000>] print_cpu_info+0x7e/0x92
>
> (This one was obtained with kernel version 2.6.27.4)
>
Could you try e.g. 2.6.27.7 or something with this patch?:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commit;h=58ec3b4db9eb5a28e3aec5f407a54e28f7039c19
Jarek P.
next prev parent reply other threads:[~2008-12-11 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 14:44 Lockup with tun/tap/bridge interface deregistration Mathieu SEGAUD
2008-12-11 10:24 ` Jarek Poplawski [this message]
2008-12-11 10:43 ` Jarek Poplawski
2008-12-11 10:49 ` Herbert Xu
2008-12-11 11:02 ` Jarek Poplawski
2008-12-11 13:27 ` Mathieu SEGAUD
2008-12-17 12:23 ` Jarek Poplawski
2008-12-17 12:34 ` Herbert Xu
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=20081211102421.GB4129@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@gentoo.org \
--cc=mathieu.segaud@regala.cx \
--cc=netdev@vger.kernel.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).