On Sat, 30 Nov 2013, Nicholas Mc Guire wrote:
> On Fri, 29 Nov 2013, Sebastian Andrzej Siewior wrote:
>
> > * Sebastian Andrzej Siewior | 2013-11-29 16:14:01 [+0100]:
> >
> > >* Nicholas Mc Guire | 2013-11-23 01:51:58 [+0100]:
> > >
> > >>>From 5c9a0c1510ec29c1e148f66f3c111f52f7565df1 Mon Sep 17 00:00:00 2001
> > >>From: Nicholas Mc Guire <der.herr@xxxxxxx>
> > >>Date: Fri, 22 Nov 2013 02:41:48 -0500
> > >>Subject: [PATCH] migrate_disable pushd down in rt_read_trylock
> > >>
> > >> No need to migrate_disable before requesting the lock and no need to
> > >> speculatively disable/enable on every recursive call. migration_disable
> > >> can be done at the latest point in the code before returning an acquired
> > >> ``lock.
> > >>
> > >> patch is on top of 3.12-rt2
> > >>
> > >> No change of functionality
> > >Applied without this line.
> >
> > and dropped because there is a problem with this:
> > - Now
> > if you read_lock() and then read_try_lock() then migrate_disable() is
> > called by each caller. Also on read_unlock() migrate_enable() is called
> > by each caller.
> >
> > - with patch
> > read_lock() calls migrate_disable() and read_try_lock() does not. Both
> > get the lock. So on read_unlock(), the read_try_lock() owner remains
> > unbalanced.
> >
> > disabling migration prior incrementing read_depth should fix this.
> >
> yup - that one is broken - interesting that the boxes run happily for
> days now with this bug applied :)
> 4core i3 and a 4core i7
>
Maybe not so suprising after all read_lock is only in use in three places
the lockdep cases definitely were not on in my configuration
and the mca.c case seemes not to have been hit ither (or there simply was
no recursive call in that path).
call sites:
0 mca.c default_monarch_init_proc 1634 if (read_trylock(&tasklist_lock)) {
1 lockdep.c debug_show_all_locks 4139 if (!read_trylock(&tasklist_lock)) {
2 lockdep.c debug_show_all_locks 4166 if (read_trylock(&tasklist_lock))
given that the broken patch was disabling once and enabling potentially a
number of times it should have triggert the
WARN_ON_ONCE(p->migrate_disable <= 0); in migrate_enable() if the recursive
case would have ever bin hit... so much to testing and locking...
thx!
hofrat
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
