ladybird/Kernel/Memory/PageFaultResponse.h

/*
 * Copyright (c) 2020, the SerenityOS developers.
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#pragma once

namespace Kernel {

enum class PageFaultResponse {
    ShouldCrash,
    BusError,
    OutOfMemory,
    Continue,
};

}
Kernel: Merge PurgeableVMObject into AnonymousVMObject This implements memory commitments and lazy-allocation of committed memory. 2020-09-05 15:52:14 -06:00			`/*`
Everywhere: Use "the SerenityOS developers." in copyright headers We had some inconsistencies before: - Sometimes "The", sometimes "the" - Sometimes trailing ".", sometimes no trailing "." I picked the most common one (lowecase "the", trailing ".") and applied it to all copyright headers. By using the exact same string everywhere we can ensure nothing gets missed during a global search (and replace), and that these inconsistencies are not spread any further (as copyright headers are commonly copied to new files). 2021-04-28 22:46:44 +02:00			`* Copyright (c) 2020, the SerenityOS developers.`
Kernel: Merge PurgeableVMObject into AnonymousVMObject This implements memory commitments and lazy-allocation of committed memory. 2020-09-05 15:52:14 -06:00			`*`
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt * 2021-04-22 01:24:48 -07:00			`* SPDX-License-Identifier: BSD-2-Clause`
Kernel: Merge PurgeableVMObject into AnonymousVMObject This implements memory commitments and lazy-allocation of committed memory. 2020-09-05 15:52:14 -06:00			`*/`

			`#pragma once`

			`namespace Kernel {`

			`enum class PageFaultResponse {`
			`ShouldCrash,`
Kernel: Send SIGBUS to threads that use after valid Inode mmaped range According to Dr. POSIX, we should allow to call mmap on inodes even on ranges that currently don't map to any actual data. Trying to read or write to those ranges should result in SIGBUS being sent to the thread that did violating memory access. 2022-08-07 22:08:52 +03:00			`BusError,`
Kernel: Merge PurgeableVMObject into AnonymousVMObject This implements memory commitments and lazy-allocation of committed memory. 2020-09-05 15:52:14 -06:00			`OutOfMemory,`
			`Continue,`
			`};`

			`}`