Re: [PATCH][RFC] Spinlock-timeout

[Jake Moilanen]

On Sat, 2004-06-05 at 15:51, Jan-Benedict Glaw wrote:
> On Sat, 2004-06-05 15:31:26 -0500, Jake Moilanen <moilanen@xxxxxxxxxxxxxx>
> wrote in message <1086467486.20906.59.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>:
> > Here's a patch that will BUG() when a spinlock is held for longer then X
> > seconds.  It is useful for catching deadlocks since not all archs have a
> > NMI watchdog.  
> 
> I like the idea. However, I don't like touching all arch's Kconfig
> files. I think it's better to either put this into ./lib/Kconfig (well,
> doesn't really fit there), ot (even better:) put it into the Debug
> Kconfig file.
> 

I think you're right that lib/Kconfig would not be the right place, but
I don't think there is a debug Kconfig.  I tried keeping the Kconfig
additions w/ CONFIG_DEBUG_SPINLOCK.  The other option is to make a debug
Kconfig, but every arch seems pretty different in what they have for
their debug section.

> I'd say just include <linux/jiffies.h> and drop the whole #ifdef/#endif
> block.

You're right, I'll take this out.

> > @@ -218,11 +228,27 @@
> >  } while (0)
> >  
> >  #else
> > +#if defined(CONFIG_SPINLOCK_TIMEOUT)
> > +
> > +static inline void spin_lock(spinlock_t * lock) {
> > +	unsigned long jiffy_timeout = jiffies + (SPINLOCK_TIMEOUT * HZ); 
> > +
> > +	preempt_disable(); 
> > +	do { 
> > +		if (jiffies >= jiffy_timeout) 
> > +		        BUG();
> > +	} while (!_raw_spin_trylock(lock)); 
> > +}
> > +
> > +#else /* CONFIG_SPINLOCK_TIMEOUT */
> > +
> >  #define spin_lock(lock)	\
> >  do { \
> >  	preempt_disable(); \
> >  	_raw_spin_lock(lock); \
> >  } while(0)
> > +
> > +#endif /* CONFIG_SPINLOCK_TIMEOUT */
> >  
> >  #define write_lock(lock) \
> >  do { \
> 
> Also, printing out ->module, ->owner and ->oline might help additionally
> to just BUG()ing. So you see the (former) owner of the lock.

I think this would give us some extra info, but ->module, ->owner, and
->oline is only used for !SMP.  I could add that in for all the arch's
spinlock_t in their asm/spinlock.h.  I'm not sure how well that would be
received to increase the size of everyones spinlock_t even though it
would only be when CONFIG_DEBUG_SPINLOCK is on.

Thanks,
Jake

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/