From: Jeremy Katz <jeremy.katz@windriver.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@tv-sign.ru>,
Stable Team <stable@kernel.org>
Subject: Re: [PATCH] posix-timer: fix deletion race
Date: Tue, 17 Jul 2007 16:58:33 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0707171654020.10358@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0707171558570.10358@localhost.localdomain>
On Tue, 17 Jul 2007, Jeremy Katz wrote:
> On Tue, 17 Jul 2007, Thomas Gleixner wrote:
>
>> With 2.6.14 or with current mainline ?
>
> I haven't been keeping notes quite as studiously as I should have been, but
> this just occurred with 2.6.22.1 + the hrt6 patch + your proposed fix:
Scratch that. I had infrastructure problems, and ended up using the wrong
build.
This is with the patch (and 2.6.22.1 and hrt6):
------------[ cut here ]------------
Kernel BUG at c0125adb [verbose debug info unavailable]
invalid opcode: 0000 [#1]
SMP
Modules linked in:
CPU: 3
EIP: 0060:[<c0125adb>] Not tainted VLI
EFLAGS: 00010246 (2.6.22.1-WR1.4aq_cgl #2)
EIP is at sigqueue_free+0x23/0x72
eax: 00000000 ebx: f6eaf1a8 ecx: f6d4b888 edx: 00000202
esi: f73e2ba8 edi: 00000000 ebp: f7c7bf8c esp: f7c7bf84
ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Process hrtm_test (pid: 15340, ti=f7c7b000 task=f6c0f030 task.ti=f7c7b000)
Stack: 00000202 f73e2ba8 f7c7bf9c c012c941 f73e2ba8 000002fb f7c7bfb0
c012d1c0
00000286 000002fb 00000000 f7c7b000 c01027ca 000002fb 466afff4
08064190
00000000 00000000 ae8d43c8 00000107 ffff007b c010007b 00000000
00000107
Call Trace:
[<c0103504>] show_trace_log_lvl+0x1a/0x30
[<c01035bb>] show_stack_log_lvl+0x8d/0xaa
[<c01037f5>] show_registers+0x1cd/0x2cb
[<c0103a4a>] die+0x113/0x207
[<c039aab5>] do_trap+0x8f/0xc6
[<c0103d35>] do_invalid_op+0x88/0x92
[<c039a882>] error_code+0x72/0x78
[<c012c941>] release_posix_timer+0x1b/0x7a
[<c012d1c0>] sys_timer_delete+0xd7/0x10c
[<c01027ca>] syscall_call+0x7/0xb
=======================
Code: 74 04 83 48 08 01 5d c3 55 89 e5 56 53 89 c3 8b 40 08 a8 01 74 15 39
1b 75 15 83 e0 fe 89 43 08 89 d8 e8 1d ec ff ff 5b 5e 5d c3 <0f> 0b eb fe
64 a1 00 c0 4a c0 8b b0 50 04 00 00 b8 00 1e 46 c0
next prev parent reply other threads:[~2007-07-18 0:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 18:19 POSIX timer deletion race? Jeremy Katz
2007-07-17 8:53 ` [PATCH] posix-timer: fix deletion race Thomas Gleixner
2007-07-17 9:57 ` Ingo Molnar
2007-07-17 18:29 ` Jeremy Katz
2007-07-17 13:07 ` Oleg Nesterov
2007-07-17 17:02 ` Thomas Gleixner
2007-07-17 18:39 ` Jeremy Katz
2007-07-17 20:17 ` Thomas Gleixner
2007-07-17 23:12 ` Jeremy Katz
2007-07-17 23:58 ` Jeremy Katz [this message]
2007-07-18 6:05 ` Thomas Gleixner
2007-07-18 6:58 ` Thomas Gleixner
2007-07-18 19:02 ` Jeremy Katz
2007-07-18 23:43 ` Jeremy Katz
2007-07-19 5:50 ` Thomas Gleixner
2007-07-19 19:24 ` Jeremy Katz
2007-07-18 16:11 ` Oleg Nesterov
2007-07-18 19:08 ` Jeremy Katz
2007-07-20 14:15 ` Oleg Nesterov
2007-07-24 2:07 ` Jeremy Katz
2007-07-24 14:51 ` Oleg Nesterov
2007-07-24 18:36 ` Jeremy Katz
2007-07-24 20:43 ` Oleg Nesterov
2007-07-24 21:19 ` Jeremy Katz
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=Pine.LNX.4.63.0707171654020.10358@localhost.localdomain \
--to=jeremy.katz@windriver.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®