Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759352Ab2JSUe2 (ORCPT ); Fri, 19 Oct 2012 16:34:28 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:62710 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759334Ab2JSUe0 (ORCPT ); Fri, 19 Oct 2012 16:34:26 -0400 Date: Fri, 19 Oct 2012 13:34:21 -0700 From: Tejun Heo To: Kent Overstreet Cc: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org, dm-devel@redhat.com, axboe@kernel.dk, neilb@suse.de, "Martin K. Petersen" Subject: Re: [PATCH v2 01/26] block: Convert integrity to bvec_alloc_bs(), and a bugfix Message-ID: <20121019203421.GT13370@google.com> References: <1350331769-14856-1-git-send-email-koverstreet@google.com> <1350331769-14856-31-git-send-email-koverstreet@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1350331769-14856-31-git-send-email-koverstreet@google.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 22 On Mon, Oct 15, 2012 at 01:09:04PM -0700, Kent Overstreet wrote: > This adds a pointer to the bvec array to struct bio_integrity_payload, > instead of the bvecs always being inline; then the bvecs are allocated > with bvec_alloc_bs(). > > This is needed eventually for immutable bio vecs - immutable bvecs > aren't useful if we still have to copy them, hence the need for the > pointer. Less code is always nice too, though. > > Also fix an amusing bug in bio_integrity_split() - struct bio_pair > doesn't have the integrity bvecs after the bio_integrity_payloads, so > there was a buffer overrun. The code was confusing pointers with arrays. Ummm... patch description doesn't agree with the patch content? -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/