From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id qAL9n5Z2028157 for ; Wed, 21 Nov 2012 03:49:06 -0600 Date: Wed, 21 Nov 2012 04:51:13 -0500 From: Christoph Hellwig Subject: Re: [PATCH 1/2] xfs: use b_maps[] for discontiguous buffers Message-ID: <20121121095113.GA23339@infradead.org> References: <20121120224120.224166649@sgi.com> <20121120224146.376767354@sgi.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121120224146.376767354@sgi.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Mark Tinguely Cc: xfs@oss.sgi.com On Tue, Nov 20, 2012 at 04:41:21PM -0600, Mark Tinguely wrote: > This patch sets all the b_bmap accesses to be b_maps[0]. b_maps[0] > works for single and multiple segment buffers. > > This fixes a bug where xfs_trans_buf_item_match() could not find a > multi-segment buffer associated with the transaction because it was > looking for the block number in the single segment location > b_map.bm.bn rather than the new generic b_maps[0].bm.bn. This > resulted in recursive buffer lock that can never be satisfied. Should b_map be renamed to __b_map so that accesses to it are cought more easily? Also do hyou have a test case for the issue? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs