Bryan> Wow. I have no idea where that extra "goto bail" came
Bryan> from. It's not supposed to be there.
Even without it you still leak the work structure, because there's no
schedule_work().
Now that I look at it, in uverbs_mem.c, the mm will be leaked if the
kmalloc fails...
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- From: Dave Olson <[email protected]>
- Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- From: Roland Dreier <[email protected]>
- Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- From: Dave Olson <[email protected]>
- Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- From: Roland Dreier <[email protected]>
- Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- From: "Bryan O'Sullivan" <[email protected]>
- Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- Prev by Date: Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- Next by Date: Re: [RFC][PATCH 1/6] kconfigurable resources core changes
- Previous by thread: Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- Next by thread: Re: [openib-general] Re: [PATCH 35 of 53] ipath - some interrelated stability and cleanliness fixes
- Index(es):
 |