linux-kernel - Re: [PATCH 0/3] posix_timers: A few expiry caching fixes

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]

Date:	Thu, 11 Apr 2013 17:19:15 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, Oleg Nesterov <oleg@...hat.com>,
	Chen Gang <gang.chen@...anux.com>
Subject: Re: [PATCH 0/3] posix_timers: A few expiry caching fixes

On Mon, Apr 08, 2013 at 04:55:59PM -0700, Andrew Morton wrote:
> On Sat, 30 Mar 2013 14:15:28 +0100 Frederic Weisbecker <fweisbec@...il.com> wrote:
> 
> > This series is on top of latest -mmotm.
> > 
> > [1/3] fixes some omitting sample capture after a build warning suddenly became visible
> > [2/3] fixes a wrong timer_gettime() result on a timer whose target has been reaped.
> > [3/3] needs some more thinking probably
> 
> Nobody seems to have applied these to anything yet.
> 
> The changelogs don't have an explicit description of the user-visible
> impact of the bugs which were fixed.  Providing such a description
> makes it more likely that others will make the correct patch-scheduling
> decisions ;)

Ok, I'll iterate through these and try to get a better description of that side.

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