* lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
@ 2013-10-14 15:54 Woegerer, Paul
2013-10-14 16:32 ` Tom Zanussi
0 siblings, 1 reply; 6+ messages in thread
From: Woegerer, Paul @ 2013-10-14 15:54 UTC (permalink / raw)
To: openembedded-core; +Cc: Christopher Larson, Tom Zanussi, Mathieu Desnoyers
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 ?
Many thanks,
Paul
--
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
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
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Tom Zanussi @ 2013-10-14 16:32 UTC (permalink / raw)
To: Woegerer, Paul; +Cc: Mathieu Desnoyers, Christopher Larson, openembedded-core
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.
Tom
> Many thanks,
> Paul
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
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:50 ` Woegerer, Paul
2 siblings, 0 replies; 6+ messages in thread
From: Tom Zanussi @ 2013-10-14 22:19 UTC (permalink / raw)
To: Woegerer, Paul; +Cc: Mathieu Desnoyers, Christopher Larson, openembedded-core
On Mon, 2013-10-14 at 11:32 -0500, Tom Zanussi 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.
>
Adding Bruce to Cc:
Tom
> Tom
>
> > Many thanks,
> > Paul
> >
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
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
2013-10-15 6:50 ` Woegerer, Paul
2 siblings, 1 reply; 6+ messages in thread
From: Bruce Ashfield @ 2013-10-14 22:50 UTC (permalink / raw)
To: Tom Zanussi
Cc: Christopher Larson,
Patches and discussions about the oe-core layer,
Mathieu Desnoyers
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.
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
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
2013-10-14 22:50 ` Bruce Ashfield
@ 2013-10-15 6:59 ` Woegerer, Paul
0 siblings, 0 replies; 6+ messages in thread
From: Woegerer, Paul @ 2013-10-15 6:59 UTC (permalink / raw)
To: Bruce Ashfield, Tom Zanussi
Cc: Christopher Larson, Mathieu Desnoyers,
Patches and discussions about the oe-core layer
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
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:50 ` Woegerer, Paul
2 siblings, 0 replies; 6+ messages in thread
From: Woegerer, Paul @ 2013-10-15 6:50 UTC (permalink / raw)
To: Tom Zanussi; +Cc: Mathieu Desnoyers, Christopher Larson, openembedded-core
On 10/14/2013 06:32 PM, Tom Zanussi wrote:
> On Mon, 2013-10-14 at 17:54 +0200, Woegerer, Paul wrote:
>> 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,
That would be the ideal solution.
--
Paul
>
> Tom
>
>> Many thanks,
>> Paul
>>
>
--
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-10-15 6:59 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2013-10-15 6:50 ` Woegerer, Paul
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox