All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Woegerer, Paul" <Paul_Woegerer@mentor.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
Date: Tue, 15 Oct 2013 08:59:43 +0200	[thread overview]
Message-ID: <525CE7DF.4040102@mentor.com> (raw)
In-Reply-To: <CADkTA4MsaVcdtEkG8VJOuneZwayuRi4uwXrRVt6PW_3_Nv8kTw@mail.gmail.com>

On 10/15/2013 12:50 AM, Bruce Ashfield wrote:
> On Mon, Oct 14, 2013 at 12:32 PM, Tom Zanussi
> <tom.zanussi@linux.intel.com> wrote:
>> On Mon, 2013-10-14 at 17:54 +0200, Woegerer, Paul wrote:
>>> Hi,
>>>
>>> looking at the following commits shows that the current version of
>>> lttng-modules 2.3.x can trigger a deadlock in the timekeeping subsystem
>>> of Linux.
>>>
>>> http://git.lttng.org/?p=lttng-modules.git;a=commit;h=fc8216ae9ec5d18172d8227d179475e7cc1fb45c
>>> http://git.lttng.org/?p=lttng-modules.git;a=commit;h=9998f5216f4641a79e158135c4c1658dcc6cd2d8
>>> http://git.lttng.org/?p=lttng-modules.git;a=commit;h=e14bf96416c39675a5f785b032d1c5279020b93d
>>>
>>> This is caused by a bug in the kernel that was introduced in 3.10. The
>>> problem is already fixed in Linux 3.10.14, 3.11.3 and 3.12. See:
>>> http://marc.info/?l=linux-kernel&m=137894350929349
>>>
>>> lttng-modules 2.3.2 contains preprocessor-code that makes sure that
>>> building of lttng-modules fails for the unlucky combinations of kernel
>>> and lttng-modules. The problem is when we update our lttng-modules 2.3.0
>>> to 2.3.2 then we would have lttng-modules failing to build for our qemu*
>>> MACHINEs.
>>>
>>> Any recommendations on how we should address this ?
>>>
>> Probably just get Bruce to update linux-yocto-3.10 to 3.10.14, or pull
>> the specific commit that fixes it in.
> Precisely. And I already have all the -stable updates queued, it just needs
> to be 1.5.1, since I stopped sending updates to 3.10 for 1.5 proper a few
> weeks ago.

Bruce, as soon as you have updated linux-yocto-3.10 to 3.10.14 (or
later) I will send the patch that updates lttng-modules from 2.3.0 to
2.3.2. This will ensure we will have the checks from 2.3.2 in, so that
users of other bsps will get a compile time error if they are tring to
build a fatal combination of lttng-modules and kernel.

Thanks,
Paul

>
> This isn't severe enough to warrant any special handling outside of getting
> the -stable update into 1.5.1.
>
> Cheers,
>
> Bruce
>
>> Tom
>>
>>> Many thanks,
>>> Paul
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


-- 
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division



  reply	other threads:[~2013-10-15  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 15:54 lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2 Woegerer, Paul
2013-10-14 16:32 ` Tom Zanussi
2013-10-14 22:19   ` Tom Zanussi
2013-10-14 22:50   ` Bruce Ashfield
2013-10-15  6:59     ` Woegerer, Paul [this message]
2013-10-15  6:50   ` Woegerer, Paul

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=525CE7DF.4040102@mentor.com \
    --to=paul_woegerer@mentor.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=chris_larson@mentor.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom.zanussi@linux.intel.com \
    /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.