lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 25 Feb 2020 07:29:20 +0100
From:   Marcel Holtmann <>
To:     Luiz Augusto von Dentz <>
Cc:     Abhishek Pandit-Subedi <>,
        syzbot <>,
        "David S. Miller" <>,
        Johan Hedberg <>,
        Jakub Kicinski <>,
        Bluez mailing list <>,
        LKML <>,
        netdev <>,
Subject: Re: WARNING: refcount bug in l2cap_chan_put

Hi Luiz,

>> (Resent in plain text; sorry for double send)
>> I took a brief look at this error and uncovered that 6lowpan uses zero
>> locks when using l2cap (should be using the channel lock).
>> It seems like it would be better just to convert its direct use of
>> l2cap channel into using an l2cap socket.
> I recall having some thought on that, I think having a socket like
> RFCOMM does would be better but I don't remember why I haven't
> follow-up on that, well we wanted to discontinue the bt specific
> 6lowpan on the kernel side though.

because sockets have their own locking issues for Bluetooth. We actually want to get rid of the internal socket usage.



Powered by blists - more mailing lists