public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/13539] occasional oops, kernel SEGV, RHEL5, :uprobes:uprobe_free_process+0xba/0x131
Date: Fri, 27 Jan 2012 15:10:00 -0000	[thread overview]
Message-ID: <bug-13539-6586-FBdfN1WyPP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13539-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13539

--- Comment #11 from David Smith <dsmith at redhat dot com> 2012-01-27 15:09:46 UTC ---
I ran the unprivileged_myproc.exp in a loop last night on 2 borrowed systems:

1) RHEL5 (2.6.18-305.el5debug - x86_64) - Each test run takes normally around
13-15 minutes to complete on this system.  But, this system only made it
through 13 iterations of the test (in around 10 hours).  Looking through the
/var/log/messages, I see this:

Jan 27 04:05:23 hp-sl2x170zg6-02 kernel: INFO: task stapio:16032 blocked for
mor
e than 120 seconds.
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel: "echo 0 >
/proc/sys/kernel/hung_task_ti
meout_secs" disables this message.
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel: stapio        D ffff8101bcd64088     0 
16032  16029         16038       (NOTLB)
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  ffff81018fe09dc8 0000000000000046
0000
000000000000 0000000000000046
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  ffff8101bce008d0 0000000000000007
ffff
81018fc3e080 ffff8101bd0cc600
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  00001edff65e7937 000000000000178f
ffff
81018fc3e268 000000018be2c720
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel: Call Trace:
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff88657c6e>]
:uprobes:__unregi
ster_uprobe+0x1ef/0x22f
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff800a811e>]
autoremove_wake_f
unction+0x0/0x2e
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff8866babe>]
:stap_9846269314f
b177561661c8b9fe159f3_2043:_stp_cleanup_and_exit+0x140/0x311
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff8866bdbc>]
:stap_9846269314f
b177561661c8b9fe159f3_2043:_stp_ctl_write_cmd+0xf1/0xdbd
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff8013d5fb>]
file_has_perm+0x4
8/0xa3
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff80017800>]
vfs_write+0xce/0x
174
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff800180f4>]
sys_write+0x45/0x
6e
Jan 27 04:05:23 hp-sl2x170zg6-02 kernel:  [<ffffffff800602a6>]
tracesys+0xd5/0xd
f

It is possible this is a separate problem.

2) On RHEL6 (2.6.32-220.4.1.el6.x86_64.debug), the system did 57 iterations
with no OOPS.  However, I do see the following in /var/log/messages:

Jan 27 01:41:01 dell-pe1955-01 kernel: Slab corruption (Not tainted):
utrace_engine start=ffff880037ae5c88, len=56
Jan 27 01:41:01 dell-pe1955-01 kernel: Redzone:
0x9f911029d74e35b/0x9f911029d74e35b.
Jan 27 01:41:01 dell-pe1955-01 kernel: Last user:
[<ffffffff810d9179>](__utrace_engine_release+0x39/0x50)
Jan 27 01:41:01 dell-pe1955-01 kernel: 020: e0 9c 54 81 ff ff ff ff 6b 6b 6b 6b
6b 6b 6b 6b
Jan 27 01:41:01 dell-pe1955-01 kernel: 030: 01 00 00 00 00 00 00 00
Jan 27 01:41:01 dell-pe1955-01 kernel: Prev obj: start=ffff880037ae5c38, len=56
Jan 27 01:41:01 dell-pe1955-01 kernel: Redzone:
0xd84156c5635688c0/0xd84156c5635688c0.
Jan 27 01:41:01 dell-pe1955-01 kernel: Last user:
[<ffffffff810d926a>](utrace_attach_task+0xba/0x2b0)
Jan 27 01:41:01 dell-pe1955-01 kernel: 000: 01 00 00 00 5a 5a 5a 5a 00 00 00 00
00 00 00 00
Jan 27 01:41:01 dell-pe1955-01 kernel: 010: 08 86 7a c7 00 88 ff ff e8 8c 7a c7
00 88 ff ff
Jan 27 01:41:02 dell-pe1955-01 kernel: Next obj: start=ffff880037ae5cd8, len=56
Jan 27 01:41:02 dell-pe1955-01 kernel: Redzone:
0xd84156c5635688c0/0xd84156c5635688c0.
Jan 27 01:41:02 dell-pe1955-01 kernel: Last user:
[<ffffffff810d926a>](utrace_attach_task+0xba/0x2b0)
Jan 27 01:41:02 dell-pe1955-01 kernel: 000: 01 00 00 00 5a 5a 5a 5a 00 00 00 00
00 00 00 00
Jan 27 01:41:02 dell-pe1955-01 kernel: 010: e8 5c ae 37 00 88 ff ff e8 5c ae 37
00 88 ff ff

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-01-27 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 22:38 [Bug uprobes/13539] New: " fche at redhat dot com
2011-12-21 22:59 ` [Bug uprobes/13539] " fche at redhat dot com
2011-12-22  1:38 ` fche at redhat dot com
2011-12-22 12:20 ` fche at redhat dot com
2011-12-31 14:27 ` fche at redhat dot com
2012-01-02 22:31 ` fche at redhat dot com
2012-01-06 12:25   ` Srikar Dronamraju
2012-01-06 17:01     ` David Smith
2012-01-06 16:57 ` dsmith at redhat dot com
2012-01-06 17:01 ` dsmith at redhat dot com
2012-01-26 16:10 ` fche at redhat dot com
2012-01-26 22:35 ` dsmith at redhat dot com
2012-01-26 22:58 ` jistone at redhat dot com
2012-01-27 14:52 ` dsmith at redhat dot com
2012-01-27 15:10 ` dsmith at redhat dot com [this message]
2012-01-27 16:20 ` jistone at redhat dot com
2012-01-30 22:05 ` fche at redhat dot com

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=bug-13539-6586-FBdfN1WyPP@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).