Bug 162257

Summary:	irq stacks not being used for hardirqs
Product:	Red Hat Enterprise Linux 4	Reporter:	Jason Baron <jbaron>
Component:	kernel	Assignee:	Jason Baron <jbaron>
Status:	CLOSED ERRATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	craig, davej, dwmw2, knoel, poelstra
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	RHSA-2005-514	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-05 13:38:56 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:
Bug Depends On:
Bug Blocks:	156322

Description Jason Baron 2005-07-01 18:48:25 UTC

Description of problem:

Currently, x86 boxes make use of a process's stack for hardirq handling. With 4K
stacks, we should really be using irq stacks which are per cpu


Version-Release number of selected component (if applicable):


How reproducible:

We don't have any specific bugs for this issue. But this is a fundamental
assumption that kernel code relies upon, and is the default setup for 4K stacks
upstream.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 4 Jason Baron 2005-07-06 16:06:20 UTC

*** Bug 162548 has been marked as a duplicate of this bug. ***

Comment 6 craig harmer 2005-07-07 07:56:37 UTC

unfortunately, veritas' vxfs tends to use more stack space than other file
systems on linux.  although we don't have any actual overflow cases in our
limited testing with 4 Kbyte stacks, we think they may well occur at customer
sites.  so this bug is high priority for us.

since the bug report i opened was closed as a dup of this one, so i'd like to
change the priority of this bug to "high".

Comment 12 Red Hat Bugzilla 2005-10-05 13:38:57 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-514.html