Re: [PATCH v4 1/2] staging: vt6655: check for memory allocation failures

This will crash. Please see my comments that I just posted to v3. regards, dan carpenter

Re: [PATCH v4 1/2] staging: vt6655: check for memory allocation failures

This will crash. Please see my comments that I just posted to v3. regards, dan carpenter

Re: [PATCH v4 1/2] staging: vt6655: check for memory allocation failures

On 2018/3/30 13:51, Ji-Hun Kim wrote: There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation

Re: [PATCH v4 1/2] staging: vt6655: check for memory allocation failures

On 2018/3/30 13:51, Ji-Hun Kim wrote: There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation

[PATCH v4 1/2] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim

[PATCH v4 1/2] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim --- Changes