Re: [patch] ipv4: initialize arp_tbl rw lock
- From: Stephen Hemminger <shemminger@xxxxxxxx>
- Date: Fri, 7 Apr 2006 07:46:27 -0700
On Fri, 7 Apr 2006 10:15:33 +0200
Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote:
From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
The qeth driver makes use of the arp_tbl rw lock. CONFIG_DEBUG_SPINLOCK
detects that this lock is not initialized as it is supposed to be.
Signed-off-by: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
---
This is a initialization order problem then, because:
arp_init
neigh_table_init
rwlock_init
does the initialization already. So fix the initialization sequence
of the qeth driver or you will have other problems.
My impression was the -rt folks wanted all lock initializations t be
done at runtime not compile time.
-
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/
- Follow-Ups:
- Re: [patch] ipv4: initialize arp_tbl rw lock
- From: Heiko Carstens
- Re: [patch] ipv4: initialize arp_tbl rw lock
- References:
- [patch] ipv4: initialize arp_tbl rw lock
- From: Heiko Carstens
- [patch] ipv4: initialize arp_tbl rw lock
- Prev by Date: [PATCH 11/17] uml: move outside spinlock call not needing it
- Next by Date: [PATCH 14/17] uml: fix big stack user
- Previous by thread: [patch] ipv4: initialize arp_tbl rw lock
- Next by thread: Re: [patch] ipv4: initialize arp_tbl rw lock
- Index(es):
Relevant Pages
|
