On 16.03.2015 15:15, Kirill A. Shutemov wrote:
On Mon, Mar 16, 2015 at 12:12:54PM +0100, Christian Borntraeger wrote:
Am 16.03.2015 um 12:00 schrieb Kirill A. Shutemov:
On Mon, Mar 16, 2015 at 09:37:01AM +0100, Christian Borntraeger wrote:
while debugging a memory management problem it helped a lot to
get a system dump as early as possible for bad page states.
Lets assume that if panic_on_oops is set then the system should
not continue with broken mm data structures.
bed_pte is not an oops.
I know that this is not an oops, but semantically it is like one. I certainly
want to a way to hard stop the system if something like that happens.
Would something like panic_on_mm_error be better?
Or panic_on_taint=<mask> where <mask> is bit-mask of TAINT_* values.
The problem is that TAINT_* will effectevely become part of kernel ABI
and I'm not sure it's good idea.
Taint bits have associated letters: for example panic_on_taint=OP
panic on out-of-tree or propriate =)
Oopsing on any taint will have limited usefulness, I think.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>