linux-kernel - Re: [RFC] Packaging libtraceevent.so

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:	Tue, 3 Dec 2013 10:23:21 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Josh Boyer <jwboyer@...oraproject.org>
Cc:	Namhyung Kim <namhyung@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Jiri Olsa <jolsa@...hat.com>
Subject: Re: [RFC] Packaging libtraceevent.so

On Tue, 3 Dec 2013 08:56:33 -0500
Josh Boyer <jwboyer@...oraproject.org> wrote:


> So the level of stable I think would be needed is basically being able
> to ship a new libtraceevent.so and have it not break a powertop that
> was linked against a previous version.  E.g. libtraceevent.so provided
> with the 3.15 kernel release can be used as an update to the
> libtraceevent.so from the 3.13 release and powertop doesn't need to be
> rebuilt.
> 
> That's typically done with soname and/or symbol versioning.  Clearly
> applications wishing to use new libtraceevent features would need to
> be rebuilt to take advantage of those, but basic functionality should
> be pretty stable.  Changing soname/ABI happens elsewhere in userspace
> libs and isn't a big deal for development, but those bumps typically
> aren't done in the middle of a released distro version.  There are
> several distros that do major kernel version updates during the
> lifetime of a release so anything coming from those needs to be
> handled carefully.

There's a couple of things that need to be cleaned up first, that will
affect current users. But they are minor. I think we can work on this
soon and get something out by the next release.

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