linux-kernel - Re: [PATCH RT 3/6] rt: Make cpu_chill() use hrtimer instead of msleep()

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: <20140307095223.2f412a1a@gandalf.local.home>
Date:	Fri, 7 Mar 2014 09:52:23 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	linux-kernel@...r.kernel.org,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Carsten Emde <C.Emde@...dl.org>,
	John Kacur <jkacur@...hat.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	stable-rt@...r.kernel.org
Subject: Re: [PATCH RT 3/6] rt: Make cpu_chill() use hrtimer instead of
 msleep()

On Fri, 07 Mar 2014 10:51:55 +0100
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:

> On 03/05/2014 01:33 AM, Steven Rostedt wrote:
> > 3.2.55-rt79-rc1 stable review patch.
> > If anyone has any objections, please let me know.
> 
> Now that you posted "cpu_chill: Add a UNINTERRUPTIBLE
> hrtimer_nanosleep" wouldn't it make sense to delay this patches from
> the stable series until we get them all in one go?

Sure, say this on the day I'm about to release ;-)

Nah, I'll release these today anyway. Otherwise I can't update to the
mainline stables. When the rc candidates are out, it holds up any new
updates to the versions.

Also, the stable 3.10 has this bug already. Might as well update all
the stables with the same fix. It makes it easier on my side, as the
way I do the updates is to use the same quilt queue for all releases. I
start with 3.10, and get them working, and then apply the same queue to
3.8. Any conflicts in the patch I do a quilt fork, with a -v3.8
appended, and then after getting that working I go to 3.4, and so on.
This also lets me drop patches that are not applicable for earlier
releases.

If I delay this for a new update, then 3.10 will be out of sync. I'm
just going to release these, and then we can start a new one right away.

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/