Bug 6936
Summary: | 'more /proc/misc' segfaults | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Kjartan Maraas <kmaraas> |
Component: | util-linux | Assignee: | Crutcher Dunnavant <crutcher> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | steve |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-27 03:08:20 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
Kjartan Maraas
1999-11-11 21:07:29 UTC
This is not a bug in more: it's a bug in /proc/misc(!) When doing a low-level read(2) on /proc/misc, asking for a small number of bytes (say, 2) returns the full size of what /proc/misc has to offer even if this overflows the caller's buffer. More allocates a two-byte buffer on the stack, and the stack gets trashed when the read(2) call returns 26 instead of two. Not sure if I will be able to track down the kernel problem, but at least don't waste your time looking at more(1). |