linux-kernel - Re: [PATCH 3.4 00/37] 3.4.79-stable review

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: <20140204215221.GA2127@bender.morinfr.org>
Date:	Tue, 4 Feb 2014 22:52:21 +0100
From:	Guillaume Morin <guillaume@...infr.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 3.4 00/37] 3.4.79-stable review

On 04 Feb 13:00, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.79 release.
> There are 37 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> (snip)
> Borislav Petkov <bp@...en8.de>
>     rtc-cmos: Add an alarm disable quirk

This is just one of the 3 patches posted by John Stultz on
http://git.linaro.org/people/john.stultz/linux.git/shortlog/refs/heads/stable/3.4/timefix

The other 2 are backports of 6fdda9a9c5db367130cf32df5d6618d08b89f46a
(timekeeping: Avoid possible deadlock from clock_was_set_delayed) and
ec145babe754f9ea1079034a108104b6001e001c (timekeeping: fix 32-bit
overflow in get_monotonic_boottime)

Could you explain why there were not included?  Are you simply planning
to include these in 3.4.80?

Sorry if this was discussed somewhere but the original thread does not
say when/if they are going to be included in 3.4.  If this information
is somewhere else, could you just point me to the discussion?

Thanks in advance for your help,

Guillaume.

-- 
Guillaume Morin <guillaume@...infr.org>
--
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/