Date: Fri, 18 Nov 2005 09:33:20 +0000 (GMT)
From: Hugh Dickins <hugh@veritas.com>
To: "David S. Miller" <davem@davemloft.net>
cc: nickpiggin@yahoo.com.au, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/11] unpaged: COW on VM_UNPAGED
In-Reply-To: <20051118.003606.59385217.davem@davemloft.net>
Message-ID: <Pine.LNX.4.61.0511180920110.6333@goblin.wat.veritas.com>
References: <Pine.LNX.4.61.0511180730530.5435@goblin.wat.veritas.com>
 <20051118.000802.81426185.davem@davemloft.net>
 <Pine.LNX.4.61.0511180813110.5788@goblin.wat.veritas.com>
 <20051118.003606.59385217.davem@davemloft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 928
Lines: 23

On Fri, 18 Nov 2005, David S. Miller wrote:
> 
> If we use MAP_SHARED and let vbetool modify the real BIOS data
> area, resume fails.  That's convincing enough for me :)

Yes, I agree with your analysis: I was expecting Dominik's resume
failure to have a more conventional cause, but yes, it's from that
new vbetool actually corrupting the memory instead of using it as
a template.

Right, no warning message then.  (Some other time we might want to
withdraw the feature - as you said, they could just read /dev/mem -
and put in a research warning in preparation; but right now I've
had enough of such noise.)

Dominik's Bad page states I'll be thinking about later in the day.

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