Hi Dominik > Well, as we're seeing real issues relating to the lack of locking, 2.6.33 is > still some time away, and 2.6.34 is even further away, I tend to aim for > 2.6.34, unless any further major problems appear.
Ah, okay, I agree.
> The v3 of the locking pathes are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git#locking
>
> and will be send out to this list.
Complete series:
Tested-by: Wolfram Sang <w.s...@pengutronix.de>
No lockdep-warnings anymore whatever I tried. kmemleak reports something, but
this is a different issue (haven't even checked if this is a false positive). I
just put it here as I stumbled over it during this test-run:
unreferenced object 0xb5c644a0 (size 32):
comm "pccardd", pid 1298, jiffies 202222 (age 1400.050s)
hex dump (first 32 bytes):
20 00 a7 a6 20 a4 a5 9e d6 a4 87 f4 9c b4 c5 96 ... ...........
2e 62 6a a6 27 23 e2 ca 62 e2 a2 62 6e c2 ae ee .bj.'#..b..bn...
backtrace:
[<8052ece1>] kmemleak_alloc+0x61/0xb0
[<801c4b8a>] __kmalloc+0x1ba/0x1f0
[<c1db240c>] pcmcia_device_query+0x26c/0x320 [pcmcia]
[<c1db33b8>] pcmcia_device_add+0x368/0x490 [pcmcia]
[<c1db359a>] pcmcia_card_add+0xba/0x1e0 [pcmcia]
[<c1db373e>] ds_event+0x7e/0x230 [pcmcia]
[<c186157a>] send_event+0xba/0x160 [pcmcia_core]
[<c18623a6>] socket_insert+0x156/0x1b0 [pcmcia_core]
[<c1862865>] pccardd+0x2c5/0x3a0 [pcmcia_core]
[<8014b374>] kthread+0x74/0x80
[<801031ba>] kernel_thread_helper+0x6/0x10
[<ffffffff>] 0xffffffff
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
signature.asc
Description: Digital signature
_______________________________________________ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
