linux-kernel - Re: Proposed stable release changes

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: <20130821134248.GB16493@home.goodmis.org>
Date:	Wed, 21 Aug 2013 09:42:48 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Josh Boyer <jwboyer@...oraproject.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	stable <stable@...r.kernel.org>, lwn@....net,
	Guenter Roeck <linux@...ck-us.net>,
	Hugh Dickins <hughd@...gle.com>,
	Johannes Berg <johannes@...solutions.net>,
	Borislav Petkov <bp@...en8.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Proposed stable release changes

On Tue, Aug 20, 2013 at 08:41:23PM -0400, Josh Boyer wrote:
> 
> Let me phrase this as a question instead.  Is there something we can
> do to help catch the patches that get sucked into stable during the
> merge window and then wind up causing issues and reverted/fixed after
> things settle down in the -rc releases?

I'm curious. Of the patches that went into stable that caused problems,
how many were from the merge window?

Reason that I ask this, is because the patches I tag for stable that I
wait for a merge window for release, goes through the process of all my
patches that enter the merge window. It sits in linux-next for a while
and usually gets much more testing than a fix that may come later in the
-rc cycles.

Personally, I still let my stable patches that go into later -rc sit
in linux-next for a few days before pushing them to mainline. I may even
wait for the next -rc to push it just to make sure the patch wont cause
more issues. But I know others that just send the fix directly to
mainline without going through linux-next. Those, I would think, are the
most prone to cause issues in stable.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/