Bug 1048
Summary: | Linux gets the swap info all wrong when pushed... | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | keybounce |
Component: | kernel | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-04-10 03:03:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
keybounce
1999-02-05 00:32:55 UTC
This fork bomb attack will probably succeed less well against a 2.2.x kernel than a 2.0.x kernel but yes, much more so with some hardware than other hardware, it is possible to get effects like this. I've marked this fixed because I think that the later kernel we released as part of 5.2 fixed some bugs that might be related to this, and because the 2.2.x kernels have many more improvements in the way the deal with swap. If you have users who are crashing machines like this, disabling their accounts is a good option; instituting process and cpu limits is another option if the first is not open to you. I hope that is useful information. |