linux-kernel - Re: RFC: kconfig option CONFIG_LBDAF should be auto-selected if EXT4 is chosen

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]

Date:	Sat, 27 Oct 2012 10:40:22 +0200
From:	Toralf Förster <toralf.foerster@....de>
To:	Theodore Ts'o <tytso@....edu>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: kconfig option CONFIG_LBDAF should be auto-selected if EXT4
 is chosen

On 10/27/2012 10:24 AM, Theodore Ts'o wrote:
> On Sat, Oct 27, 2012 at 10:00:46AM +0200, Toralf Förster wrote:
>>
>> otherwise booting an EXT4 image won't work b/c the root fs can't be
>> mounted read-write - and as a side effect no syslog messages might
>> point the user to this issue (at least in my setup) ...
> 
> This is only a problem on 32-bit architectues. and it's actually
> documented in the Kconfig help message, and it's enabled by default.
> So someone would have had to have gone out of their way to turn off
> CONFIG_LBDAF.  This is the first time I've heard of someone getting
> surprised by this; do you know how CONFIG_LBDAF got disabled?  Did you
> just disable it without reading the help message?

When I use the attached UML config and run "$>make ARCH=um menuconfig"
to select EXT4, then CONFIG_LBDAF is not selected automatically.

> What we might be able to do instead is to allow the mount to succeed,
> but to simply fail any attempts to open(2) or stat(2) files larger
> than 2TB with an EFBIG error.

That would be a cool idea.

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

View attachment ".config" of type "text/plain" (21936 bytes)