From: Jack Steiner <steiner@sgi.com>
To: linux-mm@kvack.org
Subject: Possible bug in tlb shootdown patch (IA64)
Date: Fri, 25 May 2001 11:40:39 -0500 (CDT) [thread overview]
Message-ID: <200105251640.LAA50840@fsgi056.americas.sgi.com> (raw)
We hit a problem that looks like it is related to the tlb
shootdown patch.
We are running on an IA64. The application does frequent
mmap/munmap operations. The initial symptom was that although the
the application normally ran fine, it would fail intermittently
when a "ps -efl" was run. The cause of the failure was stale
TLB entries from a prior mmap mapping.
The problem appears to be caused by the following sequence in
the tlb_remove_page/tlb_finish_mmu macros that are called as
part of do_munmap->zap_page_range->zap_pmd_range->zap_pte_range:
- tlb_gather_mmu is called while "ps" is also looking
at the address space (ie., mm->mm_users >1)
- tlb_remove_page is called. "address" is not the user virtual
being unmapped - it is a relative offset into a page table.
This address gets stashed in the free_pte_ctx struct.
- tlb_finish_mmu calls flush_tlb_range & passes the stashed
address (ctx->start_addr) to flush_tlb_range. Since this
is not the user virtual address being unmapped, it causes
the TLB shootdown to fail.
Does this make sense and is this a known problem. Perhap I am just running
with an old patch.
--
Thanks
Jack Steiner (651-683-5302) steiner@sgi.com
--
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.eu.org/Linux-MM/
next reply other threads:[~2001-05-25 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 16:40 Jack Steiner [this message]
[not found] <200105251729.MAA46671@fsgi056.americas.sgi.com>
2001-05-25 19:11 ` Ben LaHaise
2001-05-29 17:48 ` Jack Steiner
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=200105251640.LAA50840@fsgi056.americas.sgi.com \
--to=steiner@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox