Re: backlight_register_device can oops if name is null ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday, January 01, 2013 6:05 AM, Devendra Naga wrote
> Hello,
> 
> while reading through the backlight_register_device function, there

backlight_register_device -> backlight_device_register

> seems to be a problem if the new object name is null, the pr_debug
> print goes and dereferences a null pointer causing an oops,
> 
> the print should be removed or the check must be placed to ensure that
> name is not null,

Hi,

If name is null in backlight_device_register(),
pr_debug() will work properly and won't cause an oops.

However, dev_set_name() will cause oops, instead of pr_debug().
In this case, NULL check would be better.


Best regards,
Jingoo Han

> 
> any ideas?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Tourism]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux