linux-kernel - Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag

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: <51E479D0.4040304@zytor.com>
Date:	Mon, 15 Jul 2013 15:38:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Guenter Roeck <linux@...ck-us.net>
CC:	David Woodhouse <dwmw2@...radead.org>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable
 kernel, let's dump the cc: stable tag

On 07/15/2013 03:07 PM, Guenter Roeck wrote:
> On Mon, Jul 15, 2013 at 11:04:28PM +0100, David Woodhouse wrote:
>> On Mon, 2013-07-15 at 13:19 -0700, Guenter Roeck wrote:
>>> That seems to be a bit drastic. It is quite useful to have the tag,
>>> but maybe it should only be added by the maintainer and not in the initial
>>> patch submission. This would ensure that the maintainer(s) made the decision.
>>> If the original patch submitter thinks that the patch is stable material,
>>> that information could be added in the comments section.
>>
>> In the case where a maintainer applies a patch with 'git am', surely
>> they can *see* that it's cc:stable?
>>
> If that maintainer is careful, yes. But that isn't the point or idea. The
> difference is that the maintainer would have to make an active decision
> to add the cc:stable tag vs. just going along with it.
> 

WTF?  If a maintainer applies a patch and misses that the thing had a
Cc: <stable> tag, that maintainer should never have applied the patch in
the first place.

It gets stickier in the case of submaintainers where there are git pulls
involved.

	-hpa


--
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/