All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Andrea Arcangeli <andrea@novell.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: fix iounmap and a pageattr memleak (x86 and x86-64)
Date: Tue, 02 Nov 2004 18:48:09 -0800	[thread overview]
Message-ID: <418846E9.1060906@us.ibm.com> (raw)
In-Reply-To: <20041103022606.GI3571@dualathlon.random>

Andrea Arcangeli wrote:
> On Tue, Nov 02, 2004 at 05:43:45PM -0800, Dave Hansen wrote:
> 
>>Oh, crap.  I meant to clear ->mapped when change_attr(__pgprot(0)) was 
>>done on it, and set it when it was changed back.  Doing that correctly 
>>preserves the symmetry, right?
> 
> yes it should. I agree with Andrew a bitflag would be enough. I'd call
> it PG_prot_none.

It should be enough, but I don't think we want to waste a bitflag for 
something that's only needed for debugging anyway.  They're getting 
precious these days.  Might as well just bloat the kernel some more when 
the alloc debugging is on.

I'll see what I can do to get some backtraces of the __pg_prot(0) &&
page->mapped cases.

WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Andrea Arcangeli <andrea@novell.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>
Subject: Re: fix iounmap and a pageattr memleak (x86 and x86-64)
Date: Tue, 02 Nov 2004 18:48:09 -0800	[thread overview]
Message-ID: <418846E9.1060906@us.ibm.com> (raw)
In-Reply-To: <20041103022606.GI3571@dualathlon.random>

Andrea Arcangeli wrote:
> On Tue, Nov 02, 2004 at 05:43:45PM -0800, Dave Hansen wrote:
> 
>>Oh, crap.  I meant to clear ->mapped when change_attr(__pgprot(0)) was 
>>done on it, and set it when it was changed back.  Doing that correctly 
>>preserves the symmetry, right?
> 
> yes it should. I agree with Andrew a bitflag would be enough. I'd call
> it PG_prot_none.

It should be enough, but I don't think we want to waste a bitflag for 
something that's only needed for debugging anyway.  They're getting 
precious these days.  Might as well just bloat the kernel some more when 
the alloc debugging is on.

I'll see what I can do to get some backtraces of the __pg_prot(0) &&
page->mapped cases.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-11-03  2:49 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 21:21 fix iounmap and a pageattr memleak (x86 and x86-64) Dave Hansen
2004-11-02 21:21 ` Dave Hansen
2004-11-02 22:07 ` Andrea Arcangeli
2004-11-02 22:07   ` Andrea Arcangeli
2004-11-02 22:21   ` Dave Hansen
2004-11-02 22:21     ` Dave Hansen
2004-11-02 22:29     ` Andrew Morton
2004-11-02 22:29       ` Andrew Morton
2004-11-02 22:34       ` Dave Hansen
2004-11-02 22:34         ` Dave Hansen
2004-11-03  0:54     ` Andrea Arcangeli
2004-11-03  0:54       ` Andrea Arcangeli
2004-11-02 22:45   ` Dave Hansen
2004-11-02 23:00     ` Dave Hansen
2004-11-02 23:00       ` Dave Hansen
2004-11-03  1:35       ` Andrea Arcangeli
2004-11-03  1:35         ` Andrea Arcangeli
2004-11-03  1:43         ` Dave Hansen
2004-11-03  1:43           ` Dave Hansen
2004-11-03  2:26           ` Andrea Arcangeli
2004-11-03  2:26             ` Andrea Arcangeli
2004-11-03  2:48             ` Dave Hansen [this message]
2004-11-03  2:48               ` Dave Hansen
2004-11-03  3:05               ` Andrea Arcangeli
2004-11-03  3:05                 ` Andrea Arcangeli
2004-11-03 19:37                 ` Dave Hansen
2004-11-03 19:37                   ` Dave Hansen
2004-11-05  0:02                 ` Dave Hansen
2004-11-05  0:40                   ` Dave Hansen
2004-11-05  0:53                     ` Andrea Arcangeli
2004-11-05  0:53                       ` Andrea Arcangeli
2004-11-05  1:55                       ` Dave Hansen
2004-11-05  1:55                         ` Dave Hansen
2004-11-05  2:08                         ` Andrea Arcangeli
2004-11-05  2:08                           ` Andrea Arcangeli
2004-11-05  2:23                           ` Dave Hansen
2004-11-05  4:03                             ` Andrea Arcangeli
2004-11-05  4:03                               ` Andrea Arcangeli
2004-11-05  4:20                               ` Andrea Arcangeli
2004-11-05  4:20                                 ` Andrea Arcangeli
2004-11-02 23:04     ` Andrew Morton
2004-11-02 23:04       ` Andrew Morton
2004-11-03  1:40       ` Andrea Arcangeli
2004-11-03  1:40         ` Andrea Arcangeli
2004-11-02 22:34 ` Jason Baron
2004-11-02 22:34   ` Jason Baron
2004-11-02 23:12   ` Andrea Arcangeli
2004-11-02 23:12     ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2004-10-28 19:21 Andrea Arcangeli
2004-11-05  8:07 ` Andrea Arcangeli
2004-11-05  8:31   ` Andi Kleen
2004-11-05  8:49     ` Andrea Arcangeli
2005-02-14 23:15       ` Andrea Arcangeli
2005-02-15 10:39         ` Andi Kleen
2005-02-15 10:48           ` Andrea Arcangeli
2005-02-15 10:51             ` Andi Kleen
2005-02-15 11:11               ` Andrea Arcangeli
2005-02-15 13:14                 ` Hugh Dickins

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=418846E9.1060906@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=andrea@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.