| Summary: |
alloc function maybe return NULL and hit memory access violation without any checking before using the C structure |
| Product: |
libva
|
Reporter: |
Lim Siew Hoon <siew.hoon.lim> |
| Component: |
intel | Assignee: |
haihao <haihao.xiang> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Sean V Kelley <seanvk> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| Hardware: |
All | |
|
| OS: |
Linux (All) | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
| Attachments: |
0001-Fix-klockwork-critical-message-hit-on-calloc-function
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 117804 [details] 0001-Fix-klockwork-critical-message-hit-on-calloc-function Fix on Klockwork scanning critical message on calloc function that possible return NULL, and hit memory access violation if we continue using it without notice it return NULL. Add in assert function to do NULL checking. Attached the patch.