linux-kernel - Re: combinatorial explosion in lockdep

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080803.011440.137037332.davem@davemloft.net>
Date:	Sun, 03 Aug 2008 01:14:40 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hugh@...itas.com
Cc:	mingo@...e.hu, peterz@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: combinatorial explosion in lockdep

From: Hugh Dickins <hugh@...itas.com>
Date: Fri, 1 Aug 2008 12:57:27 +0100 (BST)

> @@ -113,6 +113,7 @@ static void __spin_lock_debug(spinlock_t
>  		/* lockup suspected: */
>  		if (print_once) {
>  			print_once = 0;
> +			oops_in_progress = 1;
>  			printk(KERN_EMERG "BUG: spinlock lockup on CPU#%d, "
>  					"%s/%d, %p\n",
>  				raw_smp_processor_id(), current->comm,
> @@ -121,6 +122,7 @@ static void __spin_lock_debug(spinlock_t
>  #ifdef CONFIG_SMP
>  			trigger_all_cpu_backtrace();
>  #endif
> +			oops_in_progress = 0;
>  		}
>  	}
>  }

It's probably best to not later clear oops_in_progress when we trigger
an event like this, to ensure that we do actually get any followon
messages on the console.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/