From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stanislav Meduna <stano@meduna.org>
Cc: Rik van Riel <riel@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
Hai Huang <hhuang@redhat.com>
Subject: Re: [PATCH] mm: fix up a spurious page fault whenever it happens
Date: Tue, 18 Jun 2013 19:20:37 -1000 [thread overview]
Message-ID: <CA+55aFwm-a0O-jvznYpXM4Ctf_jex+gcgELq_pqXL38Y6X-JPg@mail.gmail.com> (raw)
In-Reply-To: <51C0B177.2000006@meduna.org>
On Tue, Jun 18, 2013 at 9:13 AM, Stanislav Meduna <stano@meduna.org> wrote:
>
> No crash in 2 days running with preempt none...
Is this UP?
There's the fast_tlb race that Peter fixed in commit 29eb77825cc7
("arch, mm: Remove tlb_fast_mode()"). I'm not seeing how it would
cause infinite TLB faults, but it definitely causes potentially
incoherent TLB contents. And afaik it only happens with
CONFIG_PREEMPT, and on UP systems. Which sounds like it might match
your setup...
Linus
next prev parent reply other threads:[~2013-06-19 5:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 8:42 [PATCH - sort of] x86: Livelock in handle_pte_fault Stanislav Meduna
2013-05-22 0:39 ` Steven Rostedt
2013-05-22 7:32 ` Stanislav Meduna
2013-05-22 12:33 ` Rik van Riel
2013-05-22 15:01 ` Linus Torvalds
2013-05-22 17:41 ` [PATCH] mm: fix up a spurious page fault whenever it happens Rik van Riel
2013-05-22 18:04 ` Stanislav Meduna
2013-05-22 18:11 ` Steven Rostedt
2013-05-22 18:21 ` Stanislav Meduna
2013-05-22 18:35 ` Rik van Riel
2013-05-22 18:42 ` H. Peter Anvin
2013-05-22 18:43 ` Rik van Riel
2013-05-23 8:07 ` Stanislav Meduna
2013-05-23 12:19 ` Rik van Riel
2013-05-23 13:29 ` Steven Rostedt
2013-05-23 15:06 ` H. Peter Anvin
2013-05-23 15:27 ` Steven Rostedt
2013-05-23 17:24 ` H. Peter Anvin
2013-05-23 17:36 ` Steven Rostedt
2013-05-23 17:38 ` H. Peter Anvin
2013-05-24 8:29 ` Stanislav Meduna
2013-05-24 10:28 ` Stanislav Meduna
2013-05-24 13:06 ` Rik van Riel
2013-05-24 13:55 ` Stanislav Meduna
2013-05-24 14:23 ` Stanislav Meduna
2013-06-16 21:34 ` Stanislav Meduna
2013-06-18 19:13 ` Stanislav Meduna
2013-06-19 5:20 ` Linus Torvalds [this message]
2013-06-19 7:36 ` Stanislav Meduna
2013-06-19 8:06 ` Peter Zijlstra
2013-06-20 17:50 ` Stanislav Meduna
2013-05-23 14:45 ` Linus Torvalds
2013-05-23 14:50 ` Linus Torvalds
2013-05-23 15:03 ` Stanislav Meduna
2013-05-22 18:47 ` Stanislav Meduna
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=CA+55aFwm-a0O-jvznYpXM4Ctf_jex+gcgELq_pqXL38Y6X-JPg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=hhuang@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stano@meduna.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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.