All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Jon Bernard <jbernard@debian.org>
Cc: lttng-dev <lttng-dev@lists.lttng.org>,
	Alexandre Montplaisir <alexmonthy@efficios.com>
Subject: Re: Debian 3.16.7-ckt9-2 issue with lttng-modules kmem probe
Date: Fri, 24 Apr 2015 17:45:56 +0000 (UTC)	[thread overview]
Message-ID: <1563471161.35791.1429897556370.JavaMail.zimbra__28340.6017617837$1429897619$gmane$org@efficios.com> (raw)
In-Reply-To: <20150424165935.GA5843@helmut>

----- Original Message -----
> * Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> > Hi Jon,
> > 
> > It appears that lttng-modules cannot build on the
> > Debian kernel 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13)
> > x86_64 GNU/Linux.
> > 
> > It appears that their exported kmem.h header differs from
> > the upstream stable branch, but AFAIK there is no Debian-specific
> > version number available to distinguish between upstream stable
> > and the Debian kernel.
> 
> Indeed.  The only distinguishing characteristic I see is EXTRAVERSION
> defined to '-ckt9'.  I haven't had a chance to try yet, but could that
> be acceptable?

No, because we need to do conditionals comparing numeric values
both in Makefiles and within C.

> 
> > We have been hit by this in the past for Ubuntu kernels, and the
> > solution has been to introduce a UTS_UBUNTU_RELEASE_ABI define
> > into their kernels, which can be used to follow their own kernel
> > versions.
> > 
> > Do you think we could ask Debian to do the same ?
> 
> I'm happy to ask, the argument is certainly sound.

Thanks!

Mathieu

> 
> --
> Jon
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  parent reply	other threads:[~2015-04-24 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1082981755.35270.1429823095435.JavaMail.zimbra@efficios.com>
2015-04-23 21:07 ` Debian 3.16.7-ckt9-2 issue with lttng-modules kmem probe Mathieu Desnoyers
     [not found] ` <844104542.35292.1429823245769.JavaMail.zimbra@efficios.com>
2015-04-24 16:59   ` Jon Bernard
     [not found]   ` <20150424165935.GA5843@helmut>
2015-04-24 17:45     ` Mathieu Desnoyers [this message]
     [not found]     ` <1563471161.35791.1429897556370.JavaMail.zimbra@efficios.com>
2015-04-24 19:40       ` Jon Bernard
     [not found]       ` <20150424194045.GA18076@helmut>
2015-04-27 14:35         ` Jon Bernard
     [not found]         ` <20150427143532.GA21372@helmut>
2015-04-27 15:06           ` Mathieu Desnoyers
     [not found]           ` <198139162.36696.1430147217813.JavaMail.zimbra@efficios.com>
2015-04-27 15:25             ` Jon Bernard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='1563471161.35791.1429897556370.JavaMail.zimbra__28340.6017617837$1429897619$gmane$org@efficios.com' \
    --to=mathieu.desnoyers@efficios.com \
    --cc=alexmonthy@efficios.com \
    --cc=jbernard@debian.org \
    --cc=lttng-dev@lists.lttng.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.