Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Steven Rostedt
Date: Monday, August 16, 2010 - 10:55 am

On Mon, 2010-08-16 at 19:31 +0200, Eric Dumazet wrote:

I still do not see how this is a false positive. Per-cpu locks do not
solve the issue.


Please tell me what prevents an interrupt going off after we grab the
xt_info_wrlock(cpu) in get_counters().

IOW, what prevents this:

	get_counters() {
		xt_info_wrlock(cpu);

		<interrupt> --> softirq

			xt_info_rblock_bh();
				/* which grabs the writer lock */
			DEADLOCK!!


-- Steve



--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Steven Rostedt, (Mon Aug 16, 10:07 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Eric Dumazet, (Mon Aug 16, 10:31 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Steven Rostedt, (Mon Aug 16, 10:55 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Steven Rostedt, (Mon Aug 16, 11:16 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Peter Zijlstra, (Mon Aug 16, 11:36 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Eric Dumazet, (Mon Aug 16, 11:48 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Eric Dumazet, (Mon Aug 16, 11:48 am)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Peter Zijlstra, (Mon Aug 16, 12:16 pm)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Eric Dumazet, (Mon Aug 16, 12:35 pm)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, David Miller, (Mon Aug 16, 12:44 pm)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Peter Zijlstra, (Mon Aug 16, 1:01 pm)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Peter Zijlstra, (Mon Aug 16, 1:04 pm)
Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock?, Eric Dumazet, (Mon Aug 16, 1:17 pm)