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 14:52:00 -0000	[thread overview]
Message-ID: <bug-13539-6586-VHc32ybqf6@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 #10 from David Smith <dsmith at redhat dot com> 2012-01-27 14:51:13 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > When testing this on RHEL6 (2.6.32-220.4.1.el6.x86_64.debug), I just saw the
> > following (which is still better than an oops):
> > 
> > BUG: MAX_LOCKDEP_KEYS too low!
> > turning off the locking correctness validator.
> 
> See the last section in linux/Documentation/lockdep-design.txt -- in summary,
> the leading causes are (1) every module load/unload leaks lock classes, and (2)
> statically initialized locks create separate classes.
> 
> It might be possible for us to reduce the latter effect, but we can't help the
> former.  Either way, it's not any sign that we have a problem, just that we've
> caused lockdep to exceed its internal maximum.

Right.

If that list of systemtap modules is loaded concurrently, I think I'll need to
look at the testcase.  I'd bet that wasn't intended.

-- 
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 14:52 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 [this message]
2012-01-27 15:10 ` dsmith at redhat dot com
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-VHc32ybqf6@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).