linux-kernel - Re: "EXT3-fs error" after resume from s2ram

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]

Date:	Fri, 10 Jul 2009 22:21:13 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Robert Hancock <hancockrwd@...il.com>
CC:	Christof Warlich <christof@...lich.name>,
	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	ide <linux-ide@...r.kernel.org>
Subject: Re: "EXT3-fs error" after resume from s2ram

Hello,

Robert Hancock wrote:
> On Thu, Jul 9, 2009 at 12:17 PM, Christof Warlich<christof@...lich.name> wrote:
>> Just one clarification: From what I understood so far, it will be impossible
>> to ever utilize the full disk capacity as long as the BIOS applies the HPA
>> on boot, right?
> 
> I believe that's the case, yes.. if the BIOS is applying the HPA on
> each boot, then we can't change the max address again without a
> hardware reset..

This is one of the reasons why libata was switched to prefer hardreset
so that BIOS lock downs can be circumvented.  PATA drivers
unfortunately usually don't implement hardreset.  :-(

I'll forward the patch upstream.

Thanks.

-- 
tejun
--
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/