public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: BUG: warning at kernel/lockdep.c:2427/check_flags()
Date: Thu, 8 Jun 2006 21:59:35 +0200	[thread overview]
Message-ID: <20060608215935.37c52bff@localhost> (raw)
In-Reply-To: <20060608213809.101161b0@localhost>

On Thu, 8 Jun 2006 21:38:09 +0200
Paolo Ornati <ornati@fastwebnet.it> wrote:

> After some hours running 2.6.17-rc6-mm1 + combo-patch I've got this:
> 
> [12138.880686] BUG: warning at kernel/lockdep.c:2427/check_flags()
> [12138.880692]
> [12138.880693] Call Trace:
> [12138.880702]  [<ffffffff80240374>] check_flags+0x86/0x201
> [12138.880707]  [<ffffffff80240873>] lock_acquire+0x2f/0xa3
> [12138.880713]  [<ffffffff8025fcae>] sys_munmap+0x5e/0xa7
> [12138.880719]  [<ffffffff8020944e>] system_call+0x7e/0x83
> [12138.880723]
> [12138.880725] irq event stamp: 18146
> [12138.880728] hardirqs last  enabled at (18145): [<ffffffff8049dffc>] _spin_unlock_irq+0x28/0x50
> [12138.880734] hardirqs last disabled at (18146): [<ffffffff8049d61e>] trace_hardirqs_off_thunk+0x35/0x67
> [12138.880742] softirqs last  enabled at (18112): [<ffffffff8022c1ae>] __do_softirq+0xb2/0xba
> [12138.880748] softirqs last disabled at (18105): [<ffffffff8020a2c2>] call_softirq+0x1e/0x28
> 
> 
> I don't know if/how it is reproducible.

Wow, now I can reproduce it easly :)

Just run under "gdb" a program that segfaults:

void main(void)
{
        *(int*)(0) = 1;
}

and it will trigger.

-- 
	Paolo Ornati
	Linux 2.6.17-rc6-mm1-lockdep on x86_64

  reply	other threads:[~2006-06-08 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 19:38 BUG: warning at kernel/lockdep.c:2427/check_flags() Paolo Ornati
2006-06-08 19:59 ` Paolo Ornati [this message]
2006-06-08 20:02   ` Ingo Molnar
2006-06-09  8:59   ` [patch, -rc6-mm1] irqflags tracing: fix x86_64 entry/exit Ingo Molnar
2006-06-09 10:01     ` Paolo Ornati

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=20060608215935.37c52bff@localhost \
    --to=ornati@fastwebnet.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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