From: Prarit Bhargava <prarit@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
clalance@redhat.com, mingo@redhat.com, davej@redhat.com,
Thilo.Cestonaro.external@fujitsu-siemens.com
Subject: Re: [PATCH]: Fix bogus softlockup warning with sysrq-t
Date: Tue, 27 Mar 2007 13:35:08 -0400 [thread overview]
Message-ID: <460955CC.70006@redhat.com> (raw)
In-Reply-To: <46094A70.9080901@goop.org>
Jeremy Fitzhardinge wrote:
>
> diff -r 4c81d8cafb67 drivers/char/sysrq.c
> --- a/drivers/char/sysrq.c Tue Mar 27 01:16:07 2007 -0700
> +++ b/drivers/char/sysrq.c Tue Mar 27 01:18:05 2007 -0700
> @@ -408,6 +408,8 @@ void __handle_sysrq(int key, struct tty_
> int i;
> unsigned long flags;
>
> + softlockup_global_disable();
> +
> spin_lock_irqsave(&sysrq_key_table_lock, flags);
> orig_log_level = console_loglevel;
> console_loglevel = 7;
> @@ -445,6 +447,8 @@ void __handle_sysrq(int key, struct tty_
> console_loglevel = orig_log_level;
> }
> spin_unlock_irqrestore(&sysrq_key_table_lock, flags);
> +
> + softlockup_global_enable();
> }
>
>
I wonder if that's too strong of a fix. It's only the sysrq-t case that
is the problem. AFAIK, none of the other sysrq-t operations hold the
tasklist_lock for a long time. I'd move these around show_state.
P.
prev parent reply other threads:[~2007-03-27 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 13:22 [PATCH]: Fix bogus softlockup warning with sysrq-t Prarit Bhargava
2007-03-23 23:46 ` Rick Lindsley
2007-03-27 5:43 ` Jeremy Fitzhardinge
2007-03-27 6:47 ` Cestonaro, Thilo (external)
2007-03-27 11:41 ` Prarit Bhargava
2007-03-27 16:46 ` Jeremy Fitzhardinge
2007-03-27 16:56 ` Prarit Bhargava
2007-03-27 17:35 ` Prarit Bhargava [this message]
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=460955CC.70006@redhat.com \
--to=prarit@redhat.com \
--cc=Thilo.Cestonaro.external@fujitsu-siemens.com \
--cc=akpm@linux-foundation.org \
--cc=clalance@redhat.com \
--cc=davej@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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.