Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 348981 - sysreport issues sysrq-t by default - this is dangerous
sysreport issues sysrq-t by default - this is dangerous
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: sysreport (Show other bugs)
All Linux
high Severity urgent
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2007-10-23 12:18 EDT by Sam Knuth
Modified: 2007-12-10 12:12 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2007-1071
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-10 12:12:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to make sysrq optional - not default (1.18 KB, patch)
2007-10-23 12:18 EDT, Sam Knuth
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:1071 normal SHIPPED_LIVE sysreport bug fix update 2007-12-10 12:12:20 EST

  None (edit)
Description Sam Knuth 2007-10-23 12:18:20 EDT
Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Run sysreport command with no options
Actual results:

Sysreport runs and echos "t" to /proc/sysrq-trigger

Expected results:

Sysrq-t should not be issued by default
Additional info:

This went in as a feature but it's really a regression. Issuing sysrq-t should
only be done in specific circumstances. It should not be done as a routine
practice when sysreport is normally run. Sysrq-t can cause a large variety of
problems including applicaiton failover, scsi resets/timeouts, bonding failover,
and application hangs.
Comment 1 Sam Knuth 2007-10-23 12:18:20 EDT
Created attachment 235211 [details]
patch to make sysrq optional - not default
Comment 15 errata-xmlrpc 2007-12-10 12:12:22 EST
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.


Note You need to log in before you can comment on or make changes to this bug.