linux-ext4 - Re: GRUB and the risk of block list corruption in extX

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 for Android: free password hash cracker in your pocket

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

Message-ID: <5119106C.2050608@redhat.com>
Date:	Mon, 11 Feb 2013 09:38:20 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Chris Murphy <lists@...orremedies.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: GRUB and the risk of block list corruption in extX

On 2/9/13 6:17 PM, Chris Murphy wrote:
> 
> On 2013-02-07 15:50:07 GMT Eric Sandeen wrote:
> 
>> To be clear, this is only the case when installing the bootloader
>> itself to a partition containing a filesystem, not when installing
>> to the MBR, correct?
> 
> Correct.
> 
>> Which is different than saying "/boot is on ext4" - it's putting
>> the bootloader itself on a partition containing a filesystem,
>> something which is a bit more unusual, I think.
> 
> Some users apparently want distribution specific boot loaders as
> secondary, chain loaded from a primary boot loader that goes in the
> MBR gap.
> 

Understood, just didn't want this to turn into a "grub2 doesn't work
on ext4?!" meme.  :)

Thanks,
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html