linux-kernel - Re: [PATCH lttng-modules] Fix: bump stable kernel version ranges for clock work-around

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: <20161013150036.GA21105@kroah.com>
Date:   Thu, 13 Oct 2016 17:00:36 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:     linux-kernel@...r.kernel.org, lttng-dev@...ts.lttng.org,
        John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH lttng-modules] Fix: bump stable kernel version ranges for
 clock work-around

On Thu, Oct 13, 2016 at 03:56:55PM +0200, Mathieu Desnoyers wrote:
> Linux commit 27727df240c7 ("Avoid taking lock in NMI path with
> CONFIG_DEBUG_TIMEKEEPING"), changed the logic to open-code
> the timekeeping_get_ns() function, but forgot to include
> the unit conversion from cycles to nanoseconds, breaking the
> function's output, which impacts LTTng.
> 
> We expected Linux commit 58bfea9532 "timekeeping: Fix
> __ktime_get_fast_ns() regression" to make its way into stable
> kernels promptly, but it appears new stable kernel releases were
> done before the fix was cherry-picked from the master branch.

Sorry, will go queue that up now...

greg k-h