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: <Pine.LNX.4.58.0710081037420.5290@gandalf.stny.rr.com>
Date:	Mon, 8 Oct 2007 10:41:02 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Gregory Haskins <ghaskins@...ell.com>
cc:	Thomas Gleixner <tglx@...utronix.de>, mingo@...e.hu,
	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 Mon, 8 Oct 2007, Gregory Haskins wrote:
>
> Hi Steve,
>   What you describe is exactly what I did.  The IRQF_NODELAY handler
> just minimally checks to see if the character is a sysrq related one (or
> KDB, if you have the KDB patches applied).  If it is not, it puts the
> character into a ring-buffer and wakes a (kthread-based) tasklet to do
> the normal serial/tty rx path by processing the ring.

Ah, that was in the second patch (I didn't look at that. My fault). I
didn't see this description in the comments. But you are right, it is very
close to what I did too. But before we add this to -rt, it will need to
probably need to be tested quite a bit more. Especially since this is more
to help us developers than to help end users.

I would like to see something like this eventually make it into RT.  Just
because there has been too many times that this would be useful. For now I
just use the NMI watchdog and soft lockup detect. But those are very
limiting.

>
> Hope that helps to clarify.

Yes, thanks!

-- Steve

-
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/