From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753802Ab2H2OHe (ORCPT ); Wed, 29 Aug 2012 10:07:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34530 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751000Ab2H2OHd (ORCPT ); Wed, 29 Aug 2012 10:07:33 -0400 From: Jeff Moyer To: "Martin K. Petersen" Cc: linux-kernel@vger.kernel.org, Jens Axboe Subject: Re: [PATCH] block: Fix bad range check in bio_sector_offset References: X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Wed, 29 Aug 2012 10:07:27 -0400 In-Reply-To: (Martin K. Petersen's message of "Tue, 28 Aug 2012 14:03:18 -0400") Message-ID: User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Martin K. Petersen" writes: > DM would occasionally end up splitting data integrity-enabled requests > incorrectly. The culprit was a bad range check in bio_sector_offset. The patch looks ok to me, but what is the user visible behavior when this happens? Cheers, Jeff