linux-kernel - Re: [PATCH RT] preempt: Define preempt_check_resched

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: <1331662422.25686.662.camel@gandalf.stny.rr.com>
Date:	Tue, 13 Mar 2012 14:13:42 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	John Kacur <jkacur@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Clark Williams <clark@...hat.com>
Subject: Re: [PATCH RT] preempt: Define preempt_check_resched_rt() for non
 PREEMPT config

On Tue, 2012-03-13 at 14:32 +0100, John Kacur wrote:

> This is the same patch I sent for v3.2.9-rt17. (where you complained
> because I gave clark a SOB instead of a Tested-by:) I see that
> #define preempt_check_resched()
> without the _rt has been shuffled to a more logical spot which is the
> only way I recognized that you mean this for v3.0.23-rt.

Actually it should be for 3.2-rt, my mistake to have done it against
3.0-rt, as the only person with the bug in 3.0-rt is me (It failed my
initial tests).

> 
> Could we please start to specify the rt-kernel version in these patches?

The fix was for Thomas.

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