> Not that I am aware of. I am only working on l2cap.c and l2cap.h from
> this subset. Once I enhance the functionality by some functions and
> logic, I get these preemption problems. I did not even make use of any
> more locks/mutexes/etc. than those that were present in the original
> code -- but probably (or obviously?) this is the error. But I don't know
> were to start investigating.
> But thanks for your reply. Any more help is appreciated and welcome.
>
> Martin
I think this is incorrect:
> static int l2cap_sock_connect(struct socket *sock, struct sockaddr *addr, int alen, int flags)
> {
> [...]
> lock_sock(sk);
> BT_DBG("sk %p", sk);
Probably should be reversed. Of course this is only problem if debug is enabled.
Maybe try something like this:
lock_sock(sk);
local_value = sk;
[...]
unlock_sock(sk); /* Or whatever this function name is */
BT_DBG("sk %p", local_value);
Rafal
----------------------------------------------------------------------
Poznaj Stefana! Zmien komunikator! >>> http://link.interia.pl/f1924
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
