Fix incorrect check on null pointer after a kzalloc

Bug #1833578 reported by Colin Ian King
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ddcci-driver-linux (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

Currently device is being allocated but buffer is being used to check for a failed allocation. Fix this by checking if device is null rather than buffer.

Tags: patch
Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in ddcci-driver-linux (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Colin Ian King (colin-king)
status: New → In Progress
tags: added: patch
Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ddcci-driver-linux - 0.3.2-1ubuntu1

---------------
ddcci-driver-linux (0.3.2-1ubuntu1) eoan; urgency=medium

  * Fix incorrect check on null pointer after a kzalloc (LP: #1833578)
    - checking if pointer device is null rather than buffer.

 -- Colin Ian King <email address hidden> Thu, 20 Jun 2019 17:04:11 +0100

Changed in ddcci-driver-linux (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.