* Michael Ellerman <mpe@xxxxxxxxxxxxxx> wrote: > Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > > > On Tue, Jul 03, 2018 at 01:36:43PM +0200, Vlastimil Babka wrote: > >> On 06/18/2018 10:13 AM, Greg Kroah-Hartman wrote: > >> > 4.16-stable review patch. If anyone has any objections, please let me know. > >> > >> So I was wondering, why backport such a considerable number of > >> *selftests* to stable, given the stable policy? Surely selftests don't > >> affect the kernel itself breaking for users? > > > > These came in as part of Sasha's "backport fixes" tool. It can't hurt > > to add selftest fixes/updates to stable kernels, as for some people, > > they only run the selftests for the specific kernel they are building. > > While others run selftests for the latest kernel on older kernels, both > > of which are valid ways of testing. > > I don't have a problem with these sort of patches being backported, but > it seems like Documentation/process/stable-kernel-rules.txt could use an > update? > > I honestly don't know what the rules are anymore. Self-tests are standalone tooling which help the testing of the kernel, and it makes sense to either update all of them, or none of them. Here it makes sense to update all of them, because if a self-test on a stable kernel shows a failure then a fix is probably missing from -stable, right? Also note that self-test tooling *cannot possibly break the kernel*, because they are not used in the kernel build process, so the normally conservative backporting rules do not apply. Thanks, Ingo
