On Fri, May 31, 2019 at 03:46:54PM -0600, Andreas Dilger wrote: > On May 31, 2019, at 6:10 AM, Pavel Tikhomirov <ptikhomirov@xxxxxxxxxxxxx> wrote: > > > > In the "out" label we only iput old/new_ea_inode-s, in all these places > > these variables are always NULL so there is no point in goto to "out". > > > > Signed-off-by: Pavel Tikhomirov <ptikhomirov@xxxxxxxxxxxxx> > > I'm not a fan of changes like this, since it adds potential complexity/bugs > if the error handling path is changed in the future. That is one of the major > benefits of the "goto out_*" model of error handling is that you only need to > add one new label to the end of the function when some new state is added that > needs to be cleaned up, compared to having to check each individual error to > see if something needs to be cleaned up. I'm not a fan either, for the reasons Andreas stated; if you ever move code around, it's much more hazardous because you now have to check if what had previously been a "return ret" now has to change into "goto outl". In some case, it's really obvious, if the code is at the very beginning of the function, but when you're 35 lines down, well over the size of many of an editor window, it's no longer quite so obvious whether or not "goto out" is necessary. - Ted
