Bug 69941
Summary: | Unsafe dynamic memory allocation using kmalloc | ||
---|---|---|---|
Product: | Other | Reporter: | Jonathan Boyd (jboyd) |
Component: | Other | Assignee: | other_other |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | alan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.14-rc1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Jonathan Boyd
2014-02-04 00:49:52 UTC
This bug report makes almost no sense because you've not looked at the context of whatever your test tool has spewed out. Glancing through these several are init time allocations that cannot be recovered from on failure, one is even a deliberate out of range bug check. None of this has anything to do with bluetooth. If you want this stuff to be useful then a) check the context b) send patches to fix stuff we can all run scanners. |