mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	akpm@linux-foundation.org, ak@suse.de,
	linux-kernel@vger.kernel.org, "Mallick,
	Asit K" <asit.k.mallick@intel.com>
Subject: RE: x86_64: potential critical issue with quicklists and page table pages
Date: Fri, 21 Sep 2007 13:15:40 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709211304440.18254@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A027C22D4@scsmsx411.amr.corp.intel.com>

On Fri, 21 Sep 2007, Luck, Tony wrote:

> > The quicklists have a long history and this bug has therefore also been in 
> > IA64 for a long time and it also likely exists on sparc64, sh and sh64. We 
> > need the patch that I posted to fix the other platforms. And with this fix 
> > there would be nothing amiss on x86_64 either.
> 
> IA64 doesn't do a pgd>pud>pmd>pte table walk in h/w.  The VHPT leaps
> straight to the pte page (through the virtual mapping of the VHPT). So
> this wasn't a problem for IA64.

But this is concerning a page being freed before the TLB flush has been 
performed. Another process may then reuse the page and may rely on the 
fact that there is no TLB entry installed for the page that was just 
allocated. But there is still one there. The issues that result from this 
may be depend on the nature of each MMU.

Granted we usually install another TLB entry for the page mapping the page 
into a different address space and never use the old TLB. Which is likely 
the reason why we have never seen an issue before and also why this is 
probably difficult to cause any issues in the first place.

Plus this can only occur for off node pages, meaning this must involve a 
remote processor and the other processor is likely to have a completely 
different set of TLB entries.

  reply	other threads:[~2007-09-21 20:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 18:07 Siddha, Suresh B
2007-09-21 18:18 ` Andi Kleen
2007-09-21 18:48 ` Linus Torvalds
2007-09-21 18:50   ` Christoph Lameter
2007-09-21 18:55     ` Linus Torvalds
2007-09-21 19:05       ` Linus Torvalds
2007-09-21 19:07         ` Christoph Lameter
2007-09-21 19:21           ` Linus Torvalds
2007-09-21 19:26             ` Christoph Lameter
2007-09-21 19:40               ` Linus Torvalds
2007-09-21 19:44                 ` Linus Torvalds
2007-09-21 19:56                 ` Christoph Lameter
2007-09-21 19:59                   ` Luck, Tony
2007-09-21 20:15                     ` Christoph Lameter [this message]
2007-09-24 21:27             ` Benjamin Herrenschmidt
2007-09-24 21:42               ` Christoph Lameter
2007-09-25  0:09                 ` Benjamin Herrenschmidt
2007-09-21 18:48 ` Christoph Lameter

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.64.0709211304440.18254@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=asit.k.mallick@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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®