From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: pasha.tatashin@soleen.com, akpm@linux-foundation.org,
corbet@lwn.net, linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rick.p.edgecombe@intel.com
Subject: [PATCH v2 0/3] page table check warn instead of panic
Date: Sat, 22 Jul 2023 23:15:05 +0000 [thread overview]
Message-ID: <20230722231508.1030269-1-pasha.tatashin@soleen.com> (raw)
Changelog:
v2:
- Moved "Check writable zero page in page table check" to be last in
series so not to add more BUG_ON.
- Removed page_table_check=panic as was suggested by Mathew Wilcox
v1:
https://lore.kernel.org/linux-mm/20220911095923.3614387-1-pasha.tatashin@soleen.com/
Page table check when detects errors panics the kernel, instead,
print warnings as it is more useful, and it was agreed the right
behaviour for kernel.
In case when panic is still preferred, there is panic_on_warn sysctl
option.
Pasha Tatashin (2):
mm/page_table_check: Do WARN_ON instead of BUG_ON
doc/vm: add information about page_table_check warn_on behavior
Rick Edgecombe (1):
mm/page_table_check: Check writable zero page in page table check
Documentation/mm/page_table_check.rst | 5 ++--
mm/page_table_check.c | 39 ++++++++++++++++-----------
2 files changed, 27 insertions(+), 17 deletions(-)
--
2.41.0.487.g6d72f3e995-goog
next reply other threads:[~2023-07-22 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 23:15 Pasha Tatashin [this message]
2023-07-22 23:15 ` [PATCH v2 1/3] mm/page_table_check: Do WARN_ON instead of BUG_ON Pasha Tatashin
2023-07-23 1:56 ` Matthew Wilcox
2023-07-23 3:35 ` Pasha Tatashin
2023-07-22 23:15 ` [PATCH v2 2/3] doc/vm: add information about page_table_check warn_on behavior Pasha Tatashin
2023-07-22 23:59 ` Randy Dunlap
2023-07-23 3:37 ` Pasha Tatashin
2023-07-22 23:15 ` [PATCH v2 3/3] mm/page_table_check: Check writable zero page in page table check 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=20230722231508.1030269-1-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rick.p.edgecombe@intel.com \
/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