From: Hugh Dickins <hugh@veritas.com>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: PageReserved removal woes: vbetool, suspend-to-ram breakage
Date: Tue, 22 Nov 2005 19:51:56 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0511221947230.28813@goblin.wat.veritas.com> (raw)
In-Reply-To: <E1EedI9-0005O6-00@chiark.greenend.org.uk>
On Tue, 22 Nov 2005, Matthew Garrett wrote:
> Dominik Brodowski <linux@dominikbrodowski.net> wrote:
>
> > Just wanted to let you know that the warning introduced in
> > [PATCH] core remove PageReserved
>
> It's not much of a warning, it seems to stop vbetool from working (which
> may explain a few complaints about ACPI suspend being broken in 2.6.15 -
> it's not, but vbetool is...)
>
> vbetool (well, strictly it's LRMI, but...) needs to access real-mode
> memory. On the other hand, it's probably a bad idea to let it actually
> scribble over RAM that the kernel may be using. So
> MAP_PRIVATE|PROT_WRITE seems to be the correct thing to do. This
> certainly /seemed/ to work in older kernels, but doesn't any more. What
> should I be doing instead?
>
> (I'm also not quite sure why the error claims that it's deprecated,
> whereas in fact it doesn't actually work at all. Breaking userspace
> without warning isn't terribly nice)
Sorry about that, we really didn't expect that it was being used.
And sorry I didn't get the fixes ready in time for 2.6.15-rc2.
But they've gone into Linus' git tree a couple of hours ago.
Please let me know if tomorrow's 2.6.15-rc2-git3 does not work for you.
Hugh
prev parent reply other threads:[~2005-11-22 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 10:38 Dominik Brodowski
2005-11-22 18:54 ` Matthew Garrett
2005-11-22 19:51 ` Hugh Dickins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0511221947230.28813@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=npiggin@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®