linux-kernel - Re: [PATCH 4.4 00/32] 4.4.15-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]

Date:	Thu, 07 Jul 2016 10:55:13 -0700
From:	Kevin Hilman <khilman@...libre.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux@...ck-us.net,
	shuah.kh@...sung.com, patches@...nelci.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/32] 4.4.15-stable review

Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:

> This is the start of the stable review cycle for the 4.4.15 release.
> There are 32 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.
>
> Responses should be made by Sat Jul  9 01:16:17 UTC 2016.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.15-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y
> and the diffstat can be found below.

another minor nit/request: can you update your scripts to push all the
released stable tags to the new stable-rc tree?

Currently, it's missing the v4.4.14 tag, so the git-describe comes
looking like it's 115 patches on top of v4.4.13 instead of 33 patches on
top of v4.4.14:

$ git checkout origin/linux-4.4.y
HEAD is now at 5db8024c795f... Linux 4.4.15-rc1
$ git describe
v4.4.13-115-g5db8024c795f

Note that in my previous email, I did the git describe in a tree that
also had the released stable tree tags, so the git describe came out
right, but the auto-builders don't do that.

For the git describe to be most useful, it probably makes the most sense
if the released stable tree tags are also pushed to the stable-rc tree.

Thanks,

Kevin