From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40255C43381 for ; Fri, 22 Mar 2019 12:58:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0397221873 for ; Fri, 22 Mar 2019 12:58:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553259528; bh=UCAmDSmoYYaSZWUlQnm+7p6wt8/kDbC/s16U4AKcilQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=d7YGAyS2l9ESaef4Th5thoslzKM3OX2P/9tDSRnx0gWlC29W1SdDeg21EP7iQtivq 59wNzgW6nKnq0K4Mvj1X0ylojSKBCpispePhnZvsuNvJsNaVnji4qrzmd9TooHhz8I GbBCSjFEA8Ykl5Kkfc+LpsxqcMOri8vCVLrIePjw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732019AbfCVLqL (ORCPT ); Fri, 22 Mar 2019 07:46:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:49274 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731604AbfCVLqK (ORCPT ); Fri, 22 Mar 2019 07:46:10 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 79E412075E; Fri, 22 Mar 2019 11:46:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553255170; bh=UCAmDSmoYYaSZWUlQnm+7p6wt8/kDbC/s16U4AKcilQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=faVwQtRSeY66+KIXPXRbdq59vEi5+8NFMazNM6keEA5yxPHReiSv/sYmRy3FpVysM DkMRaKFFdJZ6qW0v72AX0Aw0JV2eIVWlv/l+SfuynRiHELPdO+kFklwkozYVvyEV/3 8ybd7sHRMRIUrTHUbTnnnaaNz3eLjebixotQG62w= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, NeilBrown , Mike Snitzer , =?UTF-8?q?Guillaume=20Perr=C3=A9al?= Subject: [PATCH 4.9 100/118] dm: fix to_sector() for 32bit Date: Fri, 22 Mar 2019 12:16:12 +0100 Message-Id: <20190322111223.448545636@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190322111215.873964544@linuxfoundation.org> References: <20190322111215.873964544@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: NeilBrown commit 0bdb50c531f7377a9da80d3ce2d61f389c84cb30 upstream. A dm-raid array with devices larger than 4GB won't assemble on a 32 bit host since _check_data_dev_sectors() was added in 4.16. This is because to_sector() treats its argument as an "unsigned long" which is 32bits (4GB) on a 32bit host. Using "unsigned long long" is more correct. Kernels as early as 4.2 can have other problems due to to_sector() being used on the size of a device. Fixes: 0cf4503174c1 ("dm raid: add support for the MD RAID0 personality") cc: stable@vger.kernel.org (v4.2+) Reported-and-tested-by: Guillaume Perréal Signed-off-by: NeilBrown Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman --- include/linux/device-mapper.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/include/linux/device-mapper.h +++ b/include/linux/device-mapper.h @@ -627,7 +627,7 @@ extern struct ratelimit_state dm_ratelim */ #define dm_target_offset(ti, sector) ((sector) - (ti)->begin) -static inline sector_t to_sector(unsigned long n) +static inline sector_t to_sector(unsigned long long n) { return (n >> SECTOR_SHIFT); }