linux-kernel - Re: [lttng-dev] Perf ABI (was: Re: [PATCH 09/11] sched: export task

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

Date:	Mon, 16 Jan 2012 09:55:07 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Greg KH <greg@...ah.com>
Cc:	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	devel@...verdev.osuosl.org, Ted Ts'o <tytso@....edu>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	lttng-dev@...ts.lttng.org, Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [lttng-dev] Perf ABI (was: Re: [PATCH 09/11] sched: export
 task_prio to GPL modules)

* Greg KH <greg@...ah.com> wrote:

> So I think udev actually is a good example of how to do it 
> right, we provide proper backwards compatibility in the kernel 
> to keep userspace working.

I agree, i still have a udev system that i installed 5 years 
ago, and it's working mostly fine with current kernels.

Compatibility is a desirable property, it is something that 
preserves our users - and if done right it's almost never a big 
issue technically. If it is hindering someone then there must be 
other problems.

Of course to developers the simplest approach is always to just 
develop without regard for compatibility. The simplest form of 
that is that people write patches that work fine on their own 
systems but crash the kernel on other systems. We fix those 
bugs. Another, subtler form is when the patches work fine on 
their systems but break apps on other systems. We fix those bugs 
too.

That's why we have testing, regression tracking and maintainers, 
to control that - compatibility is just another dimension to 
'correctness', in the typical case with no inherent restrictions 
on future features and possibilities.

Thanks,

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