| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
Change-Id: Ibc6d6e691b7f97611d16f96220346dfd6ffbbf52
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some standard library functions are used while relying on bionic headers
including the headers the functions were actually declared on. Add those
missing #includes so that bluetooth.default.so will compile on glibc.
Change-Id: Ied9f89ce5a05911fca63f6bfe1b8cc8196ab3b1c
|
|\|
| |
| |
| | |
Change-Id: Iaaec1ea0bf3009b7e32a9a60f697631a3f56e889
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If profile connection requests come in too quickly
for us to handle, clients can effectively DoS the bluetooth
stack.
We used to see out of buffer errors because the requests
were batched up and sitting on buffers the rest of the stack
needed. With the switch to pure allocation we didn't see that
specific problem anymore, but we were still running into the
sanity assert.
Bug: 18323666
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ASSERTC isn't a real assert. It just prints a message and allows the
code to carry on. Switch to asserts so the exception condition is
evident in the crash log.
Make the profile queue use osi_malloc/free instead of gki buffers, so it
can't drain the buffer pool.
|
| |
| |
| |
| | |
Bug: 18139425
|
|/
|
|
| |
Change-Id: I72c08984aeef60e4833e600b4351759b9687a014
|
|
|
|
| |
Change-Id: I9affefdd2d00597545e49c593ef3bddb110d4c9c
|
|
|
|
|
|
|
|
|
|
|
|
| |
The profile queue maintains a list of pending connect operations
for each profile. If a connect is followed by a disconnect before
the queued connect is dispatched, the disconnect will have no
effect and the connect will proceed.
This code clearly needs to be re-thought; it may be a good idea to
abandon the connect queue entirely in the long-run.
Change-Id: Ic0e85654abcf7a47f65953edb301eb9524394950
|
|
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
|