linux-kernel - Re: [PATCH try #1] Kconfig: cleanup block/Kconfig help descriptions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090407123148.GA11750@mail.local.tull.net>
Date:	Tue, 7 Apr 2009 22:31:48 +1000
From:	Nick Andrew <nick@...k-andrew.net>
To:	don fisher <hdf3@...cast.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH try #1] Kconfig: cleanup block/Kconfig help descriptions

On Sun, Mar 15, 2009 at 08:15:04PM -0700, don fisher wrote:
> Nick,
>
> I am trying to configure a linux-2.6.28.7 kernel.
>
> Please explain why the switch for large block devices should be !64BIT.  
> I have a 64BIT system and currently cannot generate files greater than  
> 2TB. Is this the problem? Should this be true for 64BIT systems?

Sorry I didn't see this email earlier.

Probably due to this:

#ifdef CONFIG_LBD
typedef u64 sector_t;
typedef u64 blkcnt_t;
#else
typedef unsigned long sector_t;
typedef unsigned long blkcnt_t;
#endif

With a 64-bit machine, your sector_t and blkcnt_t are already 64 bits
wide, so CONFIG_LBD is not required.

Nick.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/