linux-kernel - Re: Autoselect patches for stable (Was: Re: [PATCH AUTOSEL for 4.9 36/56] drm/i915: Fix the level 0 max

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: <20171121150728.7o5zvf7sog5yric3@sasha-lappy>
Date:   Tue, 21 Nov 2017 15:07:32 +0000
From:   alexander.levin@...izon.com
To:     Emil Velikov <emil.l.velikov@...il.com>
CC:     Greg KH <gregkh@...uxfoundation.org>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        ML dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: Autoselect patches for stable (Was: Re: [PATCH AUTOSEL for 4.9
 36/56] drm/i915: Fix the level 0 max_wm hack on VLV/CHV)

On Mon, Nov 20, 2017 at 11:21:52AM +0000, Emil Velikov wrote:
> - Document the autoselect process
>Information about about What, Why, and [ideally] How - analogous to
>the normal stable nominations.
>Insert reference to the process in the patch notification email.

I agree with this one, and it'll definitely happen. The story behind
this is that this is all based on Julia Lawall's work which is well
documented in a published paper here:

	https://soarsmu.github.io/papers/icse12-patch.pdf

I have modified inputs and process, but it essentially is very similar
to what's described in that paper.

While I have no problem with sharing what I have so far, this is
still very much work in progress, and things keep constantly changing
based on comments I receive from reviewers and Greg, so I want to
reach a more stable point before trying to explain things and change
my mind the day after :)

If anyone is really interested in seeing the guts of this mess I
currently have I can push it to github, but bear in mind that in it's
current state it's very custom to the configuration I have, and is
a borderline unreadable mix of bash scripts and LUA.

Ideally it'll all get cleaned up and pushed anyways once I feel
comfortable with the quality of the process.

> - Make the autoselect nominations _more_ distinct than the normal stable ones.
>Maintainers will want to put more cognitive effort into the patches.

So this came up before, and the participants of that thread agreed
that adding "AUTOSEL" in the patch prefix is sufficient. What else
would you suggest adding?

-- 

Thanks,
Sasha