On Thu, Sep 13, 2012 at 09:31:45AM +0100, David Laight wrote: > > Remove useless kfree() and clean up code related to the removal. > ... > > diff --git a/drivers/isdn/gigaset/common.c b/drivers/isdn/gigaset/common.c > > index aa41485..30a6b17 100644 > > --- a/drivers/isdn/gigaset/common.c > > +++ b/drivers/isdn/gigaset/common.c > > @@ -1123,7 +1123,6 @@ struct gigaset_driver *gigaset_initdriver(unsigned minor, unsigned minors, > > return drv; > > > > error: > > - kfree(drv->cs); > > kfree(drv); > > return NULL; > > } > > > > Seems to me that (assuming kfree(NULL) is ok) the kfree() > is best left in - just in case some other error path is > added after drv->cs is assigned. > Better safe than a memory leak. No. Delete vestigial code. There are all kinds of no-ops we could add to the unwind bits of code if we wanted to so why is "drv->cs" better than anything else. First of all, no one is going to change the ISDN code to add an allocation, but if they did then they have to make sure they don't leak memory. That's how it always works. They can't just assume that there is going to be a forgotten kfree() hanging off to the side which is going to take care of it. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
