Can user space memory make the system go haywire?High memory (user space) and highmem (kernel space)Maximum...

Is it ethical to cite a reviewer's papers even if they are rather irrelevant?

Why are backslashes included in this shell script?

Arrows inside a commutative diagram using tikzcd

Do Veracrypt encrypted volumes have any kind of brute force protection?

In The Incredibles 2, why does Screenslaver's name use a pun on something that doesn't exist in the 1950s pastiche?

Am I being scammed by a sugar daddy?

I received a gift from my sister who just got back from

How to search for Android apps without ads?

Placement of positioning lights on A320 winglets

Why can't we feel the Earth's revolution?

Dedicated bike GPS computer over smartphone

Can Dive Down protect a creature against Pacifism?

Would a bit of grease on overhead door cables or bearings cause the springs to break?

Can artificial satellite positions affect tides?

New Site Design!

How can I detect if I'm in a subshell?

usage of mir gefallen

The best in flight meal option for those suffering from reflux

My parents claim they cannot pay for my college education; what are my options?

All Raised to the Power of U

Idiom for 'person who gets violent when drunk"

Should I worry about having my credit pulled multiple times while car shopping?

Certain list transform

Can an escape pod land on Earth from orbit and not be immediately detected?



Can user space memory make the system go haywire?


High memory (user space) and highmem (kernel space)Maximum memory usable by a 32 bit RHEL 6 systemHow is user space process/thread controlled by the operating systemCan swap space accomodate single process?Differences between system processes, and user processes, kernel control paths and kernel threadHow to constrain all user mode processes to access physical memory only in specific range?What's the use of having a kernel part in the virtual memory space of Linux processes?Doesn't allowing a user mode program to access kernel space memory and execute the IN and OUT instructions defeat the purpose of having CPU modes?Examples of the damage that a buggy program running in kernel mode can makeCan a user mode program access the kernel memory and the memory of other processes?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















So I was reading How Linux Works by Brian Ward. In it, he says, the user-space applications going bad will not wreck the system.




Figure 1-1. General Linux system organization
There is a critical difference between the ways that the kernel and user processes run: The kernel runs in kernel
mode, and the user processes run in user mode. Code running in kernel mode has unrestricted access to the
processor and main memory. This is a powerful but dangerous privilege that allows a kernel process to easily
crash the entire system. The area that only the kernel can access is called kernel space.



User mode, in comparison, restricts access to a (usually quite small)
subset of memory and safe CPU operations. User space refers to the
parts of main memory that the user processes can access. If a process
makes a mistake and crashes, the consequences are limited and can be
cleaned up by the kernel. This means that if your web browser crashes,
it probably won’t take down the scientific computation that you’ve
been running in the background for days.



In theory, a user process gone haywire can’t cause serious damage to
the rest of the system. In reality, it depends on what you consider
“serious damage,” as well as the particular privileges of the process,
because some processes are allowed to do more than others. For
example, can a user process completely wreck the data on a disk? With
the correct permissions, yes—and you may consider this to be fairly
dangerous. There are safeguards to prevent this, however, and most
processes simply aren’t allowed to wreak havoc in this manner.




I have read that a web server, for example, runs in user-space and I have seen it consuming all the memory of the system and forcing the server to be crashed. But what the author says is contradicting to this.



I don't know if I am misinterpreting what the author is trying to say. My apologies.



Can someone please explain if the userspace applications can wreck the system or not and why.



Thanks for your humble help.










share|improve this question























  • "consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

    – muru
    11 mins ago


















0















So I was reading How Linux Works by Brian Ward. In it, he says, the user-space applications going bad will not wreck the system.




Figure 1-1. General Linux system organization
There is a critical difference between the ways that the kernel and user processes run: The kernel runs in kernel
mode, and the user processes run in user mode. Code running in kernel mode has unrestricted access to the
processor and main memory. This is a powerful but dangerous privilege that allows a kernel process to easily
crash the entire system. The area that only the kernel can access is called kernel space.



User mode, in comparison, restricts access to a (usually quite small)
subset of memory and safe CPU operations. User space refers to the
parts of main memory that the user processes can access. If a process
makes a mistake and crashes, the consequences are limited and can be
cleaned up by the kernel. This means that if your web browser crashes,
it probably won’t take down the scientific computation that you’ve
been running in the background for days.



In theory, a user process gone haywire can’t cause serious damage to
the rest of the system. In reality, it depends on what you consider
“serious damage,” as well as the particular privileges of the process,
because some processes are allowed to do more than others. For
example, can a user process completely wreck the data on a disk? With
the correct permissions, yes—and you may consider this to be fairly
dangerous. There are safeguards to prevent this, however, and most
processes simply aren’t allowed to wreak havoc in this manner.




I have read that a web server, for example, runs in user-space and I have seen it consuming all the memory of the system and forcing the server to be crashed. But what the author says is contradicting to this.



I don't know if I am misinterpreting what the author is trying to say. My apologies.



Can someone please explain if the userspace applications can wreck the system or not and why.



Thanks for your humble help.










share|improve this question























  • "consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

    – muru
    11 mins ago














0












0








0








So I was reading How Linux Works by Brian Ward. In it, he says, the user-space applications going bad will not wreck the system.




Figure 1-1. General Linux system organization
There is a critical difference between the ways that the kernel and user processes run: The kernel runs in kernel
mode, and the user processes run in user mode. Code running in kernel mode has unrestricted access to the
processor and main memory. This is a powerful but dangerous privilege that allows a kernel process to easily
crash the entire system. The area that only the kernel can access is called kernel space.



User mode, in comparison, restricts access to a (usually quite small)
subset of memory and safe CPU operations. User space refers to the
parts of main memory that the user processes can access. If a process
makes a mistake and crashes, the consequences are limited and can be
cleaned up by the kernel. This means that if your web browser crashes,
it probably won’t take down the scientific computation that you’ve
been running in the background for days.



In theory, a user process gone haywire can’t cause serious damage to
the rest of the system. In reality, it depends on what you consider
“serious damage,” as well as the particular privileges of the process,
because some processes are allowed to do more than others. For
example, can a user process completely wreck the data on a disk? With
the correct permissions, yes—and you may consider this to be fairly
dangerous. There are safeguards to prevent this, however, and most
processes simply aren’t allowed to wreak havoc in this manner.




I have read that a web server, for example, runs in user-space and I have seen it consuming all the memory of the system and forcing the server to be crashed. But what the author says is contradicting to this.



I don't know if I am misinterpreting what the author is trying to say. My apologies.



Can someone please explain if the userspace applications can wreck the system or not and why.



Thanks for your humble help.










share|improve this question














So I was reading How Linux Works by Brian Ward. In it, he says, the user-space applications going bad will not wreck the system.




Figure 1-1. General Linux system organization
There is a critical difference between the ways that the kernel and user processes run: The kernel runs in kernel
mode, and the user processes run in user mode. Code running in kernel mode has unrestricted access to the
processor and main memory. This is a powerful but dangerous privilege that allows a kernel process to easily
crash the entire system. The area that only the kernel can access is called kernel space.



User mode, in comparison, restricts access to a (usually quite small)
subset of memory and safe CPU operations. User space refers to the
parts of main memory that the user processes can access. If a process
makes a mistake and crashes, the consequences are limited and can be
cleaned up by the kernel. This means that if your web browser crashes,
it probably won’t take down the scientific computation that you’ve
been running in the background for days.



In theory, a user process gone haywire can’t cause serious damage to
the rest of the system. In reality, it depends on what you consider
“serious damage,” as well as the particular privileges of the process,
because some processes are allowed to do more than others. For
example, can a user process completely wreck the data on a disk? With
the correct permissions, yes—and you may consider this to be fairly
dangerous. There are safeguards to prevent this, however, and most
processes simply aren’t allowed to wreak havoc in this manner.




I have read that a web server, for example, runs in user-space and I have seen it consuming all the memory of the system and forcing the server to be crashed. But what the author says is contradicting to this.



I don't know if I am misinterpreting what the author is trying to say. My apologies.



Can someone please explain if the userspace applications can wreck the system or not and why.



Thanks for your humble help.







linux linux-kernel memory






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 15 mins ago









Vignesh SPVignesh SP

51




51













  • "consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

    – muru
    11 mins ago



















  • "consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

    – muru
    11 mins ago

















"consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

– muru
11 mins ago





"consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server.

– muru
11 mins ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f524579%2fcan-user-space-memory-make-the-system-go-haywire%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f524579%2fcan-user-space-memory-make-the-system-go-haywire%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...