[Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches

[Sasha Levin]

On Sat, Sep 08, 2018 at 06:33:51PM +0200, Greg Kroah-Hartman wrote:
>On Fri, Sep 07, 2018 at 10:57:45PM +0000, Sasha Levin via Ksummit-discuss wrote:
>> On Fri, Sep 07, 2018 at 03:53:08PM -0700, Linus Torvalds wrote:
>> >On Fri, Sep 7, 2018 at 3:43 PM Guenter Roeck <linux at roeck-us.net> wrote:
>> >>
>> >> On Fri, Sep 07, 2018 at 03:27:01PM -0700, Linus Torvalds wrote:
>> >> >
>> >> > So maybe an automated "linux-next" that starts happening *before* the
>> >> > rc stage would catch some things?
>> >>
>> >> And it does, as soon as Greg publishes a set of patches.
>> >
>> >Yes, yes, I was clearly not explaining myself well.
>> >
>> >I see all the reports that you (and Nathan, and Shuah, and others) do
>> >for stable rc's. So I very much know that happens.
>> >
>> >But I was literally thinking of that week or two *before* Greg
>> >actually picks up the stable patches because he wants to have them get
>> >some testing in mainline first.
>> >
>> >*If* the same kinds of scripts that Greg and Sasha already use to pick
>> >up their stable patches could be automated early, maybe the patches
>> >would also get a bit of special testing in the *context* of the stable
>> >tree? A special automated "these are marked for stable, but haven't
>> >been picked up yet" stable-next testing thing?
>>
>> I agree. This is what I was suggesting with stable-next branches.
>
>Ok, this sounds semi-reasonable.  I'll knock something up this week to
>see if it's viable to do automated and then have it get sent to 0-day to
>do a basic "smoke test".
>
>let's see how that works...

I've pushed an autogenerated branch for 4.14 here: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git/log/?h=linux-4.14.y-next

Would be interesting to compare with what you end up with.


--
Thanks,
Sasha