mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Hui Yu <hyu@ati.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
	Andrea Arcangeli <andrea@suse.de>
Subject: Re: [PATCH] mm: data overlapping in page struct
Date: Tue, 7 Mar 2006 19:39:55 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0603071933070.4158@goblin.wat.veritas.com> (raw)
In-Reply-To: <E6F1C74189C227449B7C7BC9F60926F901B4EC4C@torcaexmb2.atitech.com>

On Tue, 7 Mar 2006, Hui Yu wrote:

> This patch is to fix a data overlapping issue in struct page. The
> problem was introduced a few months ago by "split page table lock"
> change in which mapping is moved into the same union with ptl. Since
> private has fixed length (size of unsigned long), depending on config
> options, ptl may have larger size than private. In this case, ptl will
> overlap to mapping and may overwrite the original data in mapping. 
> The simplest way of fixing this is to move mapping out of the union, as
> in this patch. There may be better approaches; I'll leave it to the
> experts more familiar with this part of code.  

Nak.  We use ->mapping for page cache pages, or pages mapped into
user address space.  We use ->ptl for page table pages of user
address space.  Where is it that you expect a data page to be
used as a page table page at the same time?

This 2.6.16 change was precisely to share that part of the struct
page between mapping and ptl, so as to bring struct page back down
to its 2.6.14 size on the non-DEBUG_SPINLOCK configurations.

Hugh

  reply	other threads:[~2006-03-07 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 19:04 Hui Yu
2006-03-07 19:39 ` Hugh Dickins [this message]
2006-03-07 20:06   ` Andi Kleen

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.0603071933070.4158@goblin.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=ak@suse.de \
    --cc=andrea@suse.de \
    --cc=hyu@ati.com \
    --cc=linux-kernel@vger.kernel.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 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®