From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: TLB corruption in 2.4.31 scenario?
Date: Wed, 15 Jun 2005 06:31:23 +0000 [thread overview]
Message-ID: <16182.1118817083@kao2.melbourne.sgi.com> (raw)
Mario cannot get to the ia64 list, so I am forwarding this for him.
Please cc Mario on any replies.
------- Forwarded Message
I noticed during a do_fork() -> copy_mm() -> dup_mmap() - flush_tlb_mm()
gets called that clears current->mm->context. Now if on another
CPU is running wrap_mmu_context() it can potenitally
step over this context number and assign an alias context to
a new task, then there is a window between the flushing of
the TLB and some other task getting its new context
assigned and returning to user space. Do you think
there is potential here?
The question comes from TLB aliasing like core files that
I've analyzed. We have not been able to isolate this to
a self-contained executable so the next best thing I could
do is read the code, the issue is very critical for us.
I'd appreciate any insights you may have, btw I can't get
on the ia64 maillist for some reason.
- mario
------- End of Forwarded Message
reply other threads:[~2005-06-15 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16182.1118817083@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-ia64@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