linux-kernel - Re: [PATCH 3.10 000/143] 3.10.102-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:	Tue, 7 Jun 2016 08:54:53 +0200
From:	Willy Tarreau <w@....eu>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 3.10 000/143] 3.10.102-stable review

On Mon, Jun 06, 2016 at 10:59:27PM -0700, Guenter Roeck wrote:
> On 06/06/2016 10:17 PM, Willy Tarreau wrote:
> > On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote:
> > > > > Do you have a repository, either with the patch
> > > > > series or with the to-be-tested branch, where the builder could
> > > > > pick it up ?
> > > > 
> > > > I don't but I can set something up for you. Would you be OK with a
> > > > branch in my account (eg: "3.10-for-guenter") which I "git push -f"
> > > > from my local branch ? That way you always pull from the same branch
> > > > and we don't care if patches are removed during the process. Just let
> > > > me know. Otherwise let me know if a different form is desired.
> > > > 
> > > 
> > > Yes, that would be excellent. I would suggest to name it something like
> > > stable-3.10-queue, though, to be a bit more generic. After all, other
> > > testers will want to pick it up as well.
> > 
> > Well, for me it would not be a "queue" in the sense of how Greg maintains
> > it but more a release candidate derived from the last 3.10 tag. Basically
> > if nothing changes between the review and the release, it will just get
> > an extra commit which is the release tag. If I produce it just for your
> > use case and you're fine with a force-pushed branch, I'd rather avoid to
> > confuse other people who probably have no business using it.
> > 
> 
> Jiri provides a branch for 3.12, exactly as you suggested. In his case it is
> named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and
> linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it.
> Other testers such as kernelci.org pick it up from there (or from my repository
> after I pull it in). In my repository, all branches are named linux-<release>.y.queue;
> for example, the 3.10 branch in my repository is named linux-3.10.y.queue.
> Those branches are also force-pushed when updated.

OK then that's perfect, I'll do the same ASAP, probably today as time permits.

Cheers,
Willy