| To: | Mark Tinguely <tinguely@xxxxxxx> |
|---|---|
| Subject: | Re: [3.0-stable PATCH 30/36] xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 12 Dec 2012 10:53:24 +1100 |
| Cc: | stable@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <20121203144311.580325568@xxxxxxx> |
| References: | <20121203144208.143464631@xxxxxxx> <20121203144311.580325568@xxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Dec 03, 2012 at 05:42:38PM -0600, Mark Tinguely wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > Upstream commit: 76d095388b040229ea1aad7dea45be0cfa20f589 > > When we fail to find an matching extent near the requested extent > specification during a left-right distance search in > xfs_alloc_ag_vextent_near, we fail to free the original cursor that > we used to look up the XFS_BTNUM_CNT tree and hence leak it. Don't back port this - it's buggy. Just backport the patch that fixed it properly. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: [3.0-stable PATCH 27/36] xfs: protect xfs_sync_worker with s_umount semaphore, Dave Chinner |
|---|---|
| Next by Date: | Re: [3.0-stable PATCH 31/36] xfs: shutdown xfs_sync_worker before the log, Dave Chinner |
| Previous by Thread: | [3.0-stable PATCH 30/36] xfs: fix allocbt cursor leak in xfs_alloc_ag_vextent_near, Mark Tinguely |
| Next by Thread: | [3.0-stable PATCH 05/36] xfs: only take the ILOCK in xfs_reclaim_inode(), Mark Tinguely |
| Indexes: | [Date] [Thread] [Top] [All Lists] |