| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [ANNOUNCE] xfs; for-next branch updated to 31bb236 |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 3 Mar 2016 08:09:31 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160302094559.GB18130@xxxxxxxxxxxxx> |
| References: | <20160301231511.GM30721@dastard> <20160302094559.GB18130@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, Mar 02, 2016 at 01:45:59AM -0800, Christoph Hellwig wrote: > > Mateusz Guzik (1): > > [2e83b79] xfs: fix two memory leaks in xfs_attr_list.c error paths > > This didn't seem to address the comment about using a goto for > error handling? I looked at it, and there isn't a case for a goto. The allocated memory is in a variable local to the if branch where the leak was found. Using a jump-based error handling stack means making all those variables global, and then having to make the freeing of it conditional. Simply didn't seem worth it to me. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH v2] [RFC] xfs: allocate log vector buffers outside CIL context lock, Darrick J. Wong |
|---|---|
| Next by Date: | Re: block allocations for the refcount btree, Darrick J. Wong |
| Previous by Thread: | Re: [ANNOUNCE] xfs; for-next branch updated to 31bb236, Christoph Hellwig |
| Next by Thread: | [PATCH] xfs: fix computation of inode btree maxlevels, Darrick J. Wong |
| Indexes: | [Date] [Thread] [Top] [All Lists] |