public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
	Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: EFAULT reading /dev/mem... - broken x86info
Date: Mon, 10 Nov 2003 21:36:53 +0200	[thread overview]
Message-ID: <3FAFE8D5.4020102@kolumbus.fi> (raw)
In-Reply-To: <3FAFDFFF.70100@colorfullife.com>



Manfred Spraul wrote:

> Petr Vandrovec wrote:
>
>> On Mon, Nov 10, 2003 at 06:17:37PM +0100, Manfred Spraul wrote:
>>  
>>
>>> DEBUG_PAGEALLOC unmaps pages on kmem_cache_free and __free_pages(). 
>>> The pages are mapped again during get_free_pages and kmem_cache_alloc.
>>>
>>> 0x86000 looks like a normal page - what guarantees that it's not 
>>> used by the kernel?
>>>   
>>
>>
>> With DEBUG_PAGEALLOC there is no problem with page if it is USED by 
>> the kernel.
>> Problem is if page is NOT USED - in this case kernel does not have it 
>> in its
>> mapping, and bad thing happen.
>>  
>>
> If the page is used by AGP, then it won't have a mapping either.
>
afaics, agp uses change_apge_attr() to turn on NOCACHE bit, and doesn't 
remove the mapping.

--Mika





  reply	other threads:[~2003-11-10 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 16:27 EFAULT reading /dev/mem... - broken x86info Petr Vandrovec
2003-11-10 13:55 ` Richard B. Johnson
2003-11-10 16:11 ` Dave Jones
2003-11-10 16:50   ` Manfred Spraul
2003-11-10 16:56     ` Dave Jones
2003-11-10 17:17       ` Manfred Spraul
2003-11-10 18:05         ` Petr Vandrovec
2003-11-10 18:59           ` Manfred Spraul
2003-11-10 19:36             ` Mika Penttilä [this message]
2003-11-10 19:47               ` Manfred Spraul
2003-11-10 20:24                 ` Dave Jones

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=3FAFE8D5.4020102@kolumbus.fi \
    --to=mika.penttila@kolumbus.fi \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=vandrove@vc.cvut.cz \
    /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