linux-kernel - Re: [PATCH 0/2] [RFC] RT: Optionally allow IRQF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.0.999.0710051831000.10191@www.tglx.de>
Date:	Fri, 5 Oct 2007 18:41:59 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Gregory Haskins <ghaskins@...ell.com>
cc:	mingo@...e.hu, rostedt@...dmis.org, linux-rt-users@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] [RFC] RT: Optionally allow IRQF_NODELAY on serial
 console

On Fri, 5 Oct 2007, Gregory Haskins wrote:
> This series may help debugging certain circumstances where the serial
> console is unreponsive (e.g. RT51+ spinner, or scheduler problem).  It changes
> the serial8250 driver to use IRQF_NODELAY so that interrupts execute in irq
> context instead of a kthread.
> 
> It works pretty well on this end, though it is admitted not fully baked.  For
> instance, a few paths in sysrq can still call into non-raw spinlocks
> (sched_debug_show, for instance) which will cause subsequent errors.  Also,
> if you use KDB, be sure to convert the kdb_printf_lock to raw as well.  I may
> send a KDB related patch seperately.
> 
> I am sending this out now in case it is helpful to someone.

The simple non-patch solution is to up the priority of the serial 
console irq to maximum. That's usually sufficient to catch runnaway tasks 
etc. It does not interfere with the system in normal operation as long as 
you do not hit keys in your minicom.

I doubt that your patch has a chance to survive lockdep and anything which 
is not a sysrq.

	tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/