stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: stable <stable@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Stable maintainer tools
Date: Mon, 9 Nov 2015 22:26:55 +0100	[thread overview]
Message-ID: <20151109212655.GL26584@1wt.eu> (raw)
In-Reply-To: <5640BC1D.9030507@oracle.com>

Hi Sasha,

On Mon, Nov 09, 2015 at 10:30:37AM -0500, Sasha Levin wrote:
> Hi all,
> 
> As I've started working on maintaining stable kernels I found that it's nearly
> impossible to assure the correctness of the resulting kernel without a fair
> amount of tools to help with the job.
> 
> Every missing commit means that there's an unfix bug, which may be critical.
> Likewise, every commit that wasn't intended to that kernel version, or is
> incorrectly backported means we might be introducing new bugs - some might
> be non obvious to detect.
> 
> There is also very little coordination and cooperation between maintainers when
> there should be much more. It's important to audit your tree against other
> maintainers and both fix your tree if necessary and report mistakes to other
> maintainers.
> 
> Therefore, to try and create a common toolset for stable tree maintainers
> I've cleaned up and published my scripts, and below I'll describe some of
> my workflows with them. The scripts are built around git, and I'd be happy
> to take in a quilt version in as well if someone wants to donate his scripts.
> 
> The code is available at
> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/stable-tools.git . Ideas,
> suggestions, bug reports and patches are more than welcome!

(...)

I'll take a look at your work next time I work on a series, this looks
interesting and indeed covers some of the painful cases I'm sometimes
running though.

Thanks for publishing this and explaining how to use it.

Willy


      reply	other threads:[~2015-11-09 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 15:30 Stable maintainer tools Sasha Levin
2015-11-09 21:26 ` Willy Tarreau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151109212655.GL26584@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).