linux-kernel - Elaboration on "Equivalent fix must already exist in Linus' tree"

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-next>] [day] [month] [year] [list]

Date:	Mon, 2 Mar 2009 21:43:26 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	wireless <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Elaboration on "Equivalent fix must already exist in Linus' tree"

While extending the documentation for submitting Linux wireless bug
reports [1] we note the stable series policy on patches -- that of
having an equivalent fix already in Linus' tree. I find this
documented in Documentation/stable_kernel_rules.txt but I'm curious if
there is any other resource which documents this or elaborates on this
a bit more. I often tell people about this rule or push _really_ hard
on testing "upstream" but some people tend to not understand. I think
that elaborating a little on this can help and will hopefully create
more awareness around the importance of trees like Stephen's
linux-next tree.

[1] http://wireless.kernel.org/en/users/Documentation/Reporting_bugs
[2] git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git

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