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] [day] [month] [year] [list]

Message-Id: <1191855976.4281.13.camel@ghaskins-t60p.haskins.net>
Date:	Mon, 08 Oct 2007 11:06:16 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	Steven Rostedt <rostedt@...dmis.org>
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, 2007-10-08 at 10:41 -0400, Steven Rostedt wrote:
> --
> 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.

Well, the lack of a proper description is my fault.  I can fix this if
there is interest in actually including it.

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

Totally agree.  Note that it already is configurably inert, and defaults
to disabled so that might make it work for the general user just fine.
FWIW, our "debug" kernels have been running with the feature on for
quite a few weeks without problems.  But I would fully expect someone
external to want to quantify that claim on their own before it would be
considered.  So give it a whirl if you get a chance.

Regards,
-Greg

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