On Tue, May 20, 2014 at 06:26:51PM -0500, Larry Finger wrote: > On 05/20/2014 04:31 PM, Rickard Strandqvist wrote: > >There is otherwise a risk of a possible null pointer dereference. > > > >Was largely found by using a static code analysis program called cppcheck. > > > >Signed-off-by: Rickard Strandqvist <rickard_strandqvist@xxxxxxxxxxxxxxxxxx> > >--- > > drivers/staging/rtl8188eu/os_dep/usb_intf.c | 127 ++++++++++++++------------- > > 1 file changed, 66 insertions(+), 61 deletions(-) > > Although cppcheck's analysis is correct, pointer padapter can never > be null in any of these routines. In routine rtw_drv_init(), > rtw_usb_if1_init() is called to allocate memory for struct adapter > for the driver. If that fails, none of these other routines will > ever be called as the driver will not be loaded. > > If it is deemed better to fill the code with needless tests because > some static checker points out a place like this, that is OK with > me, but I do not see the point. If it's an invariant of the code that padapter cannot ever be NULL, then that seems perfectly fine to rely on, and the tool just needs fixing or silencing. At most, it might be helpful to add annotations like GCC's "nonnull", if that helps the checker and the compiler generate more useful warnings. - Josh Triplett _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
