From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Chow Subject: 32/64 bit b_rsector type Date: Wed, 24 Mar 2004 14:36:29 +0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <40612C6D.6030205@shaolinmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from [202.131.75.34] ([202.131.75.34]:44938 "EHLO staff.shaolinmicro.com") by vger.kernel.org with ESMTP id S263027AbUCXGge (ORCPT ); Wed, 24 Mar 2004 01:36:34 -0500 Received: from shaolinmicro.com ([202.131.75.35]) by staff.shaolinmicro.com (8.12.8/8.12.5) with ESMTP id i2O6aGtv030698 for ; Wed, 24 Mar 2004 14:36:27 +0800 To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Dear all, On a native 32-bit Linux system, the bh->b_resetor (type unsigned long) max is limited to 16TB. For 64 bit systems, I know it can get through this point, but what about if I chanage the bh->b_rsector in fs.h to u64 (unsigned long long on 32-bit systems)? Can I simply break through the 16TB on 32-bit Linux by doing so? Please advice with possiblility of impacts. Thanks. regards, David Chow