Re: badness in kernel/softirq.c
From: Andrew Morton
Date: Sat Mar 20 2004 - 16:56:24 EST
Brad Laue <brad@xxxxxxxxxx> wrote:
>
> Badness in local_bh_enable at kernel/softirq.c:126
> Call Trace:
> [<c0121d46>] local_bh_enable+0x86/0x90
> [<d087ac3b>] ppp_sync_push+0x5b/0x170 [ppp_synctty]
> [<d087a63d>] ppp_sync_wakeup+0x2d/0x60 [ppp_synctty]
> [<c024363a>] do_tty_hangup+0x3ea/0x460
> [<c0244bcd>] release_dev+0x62d/0x660
> [<c0142d53>] unmap_page_range+0x43/0x70
> [<c0168b62>] dput+0x22/0x210
> [<c0244faa>] tty_release+0x2a/0x60
> [<c0152ec0>] __fput+0x100/0x120
> [<c0151529>] filp_close+0x59/0x90
> [<c011f594>] put_files_struct+0x54/0xc0
> [<c01201fd>] do_exit+0x18d/0x410
> [<c012051a>] do_group_exit+0x3a/0xb0
> [<c0109387>] syscall_call+0x7/0xb
This is reminding us that nobody has fixed the tty locking yet. It's
generally harmless in practice.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/