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 p8KI9qWY075338 for ; Tue, 20 Sep 2011 13:09:52 -0500 Date: Tue, 20 Sep 2011 14:09:50 -0400 From: Christoph Hellwig Subject: Re: [PATCH v2] xfs: Check the return value of xfs_trans_get_buf() Message-ID: <20110920180950.GA1327@infradead.org> References: <1316527015.9298.60.camel@chandra-lucid.austin.ibm.com> <20110920150029.GA5239@infradead.org> <1316541954.9298.65.camel@chandra-lucid.austin.ibm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1316541954.9298.65.camel@chandra-lucid.austin.ibm.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: Chandra Seetharaman Cc: Christoph Hellwig , Alex Elder , XFS Mailing List On Tue, Sep 20, 2011 at 01:05:54PM -0500, Chandra Seetharaman wrote: > > Hi Christoph, > > I do not understand. Can you elaborate on what needs to be done. All callers that do the xfs_trans_binval only really care about buffers that already exist. So we don't even have to allocate a new buffer if it isn't in memory yet - note that it generally will be given that the buffer is attached to the transaction. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs