From: Fusion Future <qydwhotmail@gmail.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Paul Turner <pjt@google.com>,
weixugc@google.com, Greg Thelen <gthelen@google.com>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Will Deacon <will@kernel.org>, Mike Rapoport <rppt@kernel.org>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
masahiroy@kernel.org, Sami Tolvanen <samitolvanen@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE" <x86@kernel.org>,
frederic@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [PATCH 2/3] mm: page table check
Date: Mon, 29 Nov 2021 10:55:58 +0800 [thread overview]
Message-ID: <aee858af-f0f7-1da6-5976-cf0057092afa@gmail.com> (raw)
In-Reply-To: <CA+CK2bDiWc2y=CW6d=6raaf9Haq2vuWQDTQZ-aAyLDdpq5aQPQ@mail.gmail.com>
On 2021/11/29 00:57, Pasha Tatashin wrote:
> This commit by itself would not cause the freeze or BUG_ON(), but the
> next commit which enables it on x86 arch might.
Yes, you are right. At the commit
"[1e67abff1820489435aad3fcf258708c21c283ef] x86: mm: add x86_64 support
for page table check" my system starts to experience the freeze.
I can now reproduce the freeze by following the steps below:
1. Open 20 YouTube video pages, and a YouTube Music page.
2. Play music in the background. (The step can be omitted)
3. Run `git clone
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git ln`
git will never successfully clone the repo because the system will
freeze during the operation.
I also tried adding `page_table_check=off` to the boot option but still
experienced the freeze. Perhaps the option is of no use.
next prev parent reply other threads:[~2021-11-29 3:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 21:48 [PATCH 0/3] page table check Pasha Tatashin
2021-11-23 21:48 ` [PATCH 1/3] mm: ptep_clear() page table helper Pasha Tatashin
2021-11-23 21:48 ` [PATCH 2/3] mm: page table check Pasha Tatashin
2021-11-27 8:41 ` Fusion Future
2021-11-27 19:48 ` Pasha Tatashin
2021-11-28 8:13 ` Fusion Future
2021-11-28 9:37 ` Fusion
2021-11-28 16:54 ` Fusion Future
2021-11-28 16:57 ` Pasha Tatashin
2021-11-29 2:55 ` Fusion Future [this message]
2021-11-30 19:25 ` Pasha Tatashin
2021-12-01 8:38 ` Jiri Slaby
2021-11-23 21:48 ` [PATCH 3/3] x86: mm: add x86_64 support for " Pasha Tatashin
2021-12-01 8:00 ` Jiri Slaby
2021-12-01 8:44 ` Jiri Slaby
2021-12-01 13:55 ` Pasha Tatashin
2021-12-02 9:59 ` Jiri Slaby
2021-12-02 10:05 ` Jiri Slaby
2021-12-02 10:30 ` Muchun Song
2021-12-02 15:01 ` Pasha Tatashin
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=aee858af-f0f7-1da6-5976-cf0057092afa@gmail.com \
--to=qydwhotmail@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=frederic@kernel.org \
--cc=gthelen@google.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).