From: John Richard Moser <nigelenki@comcast.net>
To: Jason Baron <jbaron@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix altsysrq deadlock
Date: Tue, 26 Oct 2004 14:33:47 -0400 [thread overview]
Message-ID: <417E988B.3060402@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0410261413240.12088-100000@dhcp83-105.boston.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Baron wrote:
| On Tue, 26 Oct 2004, John Richard Moser wrote:
|
|
[...]
|
|
| The patch only drops a sysrq that is about to cause a system deadlock. So
| if you haven't had any deadlocks this patch shouldn't have a noticeable
| affect.
|
| If a caller wants to rely on handle_sysrq, then it should not be called
| from interrupt context. handle_sysrq can not defer the work, since the
| point of sysrq is to be able get information out when the system is
| potentially unusable. How would you know when to defer the work and when
| not to?
Eh? Wha? I was just pointing out that it's useful beyond just
debugging, not proposing any feature changes or stuff.
|
| -Jason
|
|
|
|
|
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBfpiKhDd4aOud5P8RAlyhAJ9/qfkA27SGGvgZ4WDPOzVm2VaKKQCdHrsk
R4V/S9phuxUVOXB8Zq7d5oI=
=9UZt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-26 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:27 [PATCH] fix altsysrq deadlock Jason Baron
2004-10-26 17:43 ` John Richard Moser
2004-10-26 18:22 ` Jason Baron
2004-10-26 18:33 ` John Richard Moser [this message]
[not found] <Pine.LNX.4.44.0410261311590.12088-100000@dhcp83-105.boston.redhat.com>
2004-10-27 2:40 ` Andrew Morton
2004-10-27 19:05 ` Jason Baron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417E988B.3060402@comcast.net \
--to=nigelenki@comcast.net \
--cc=akpm@osdl.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.