How to explain to lock validator: locking inodes in inode order

["Joshua Hudson" <joshudson@gmail.com>]

Code does this:

/* Lock two items. See locking.txt */
static inline void kb0_lock2m(struct kb0_idata *m1, struct kb0_idata *m2)
{
       if (m1->vi.i_ino > m2->vi.i_ino)
               mutex_lock(&m2->k_mutex);
       mutex_lock(&m1->k_mutex);
       if (m1->vi.i_ino < m2->vi.i_ino)
               mutex_lock(&m2->k_mutex);
}

Not sure how to explain to the lock validator that this code can never deadlock.

Note struct kb0_idata has an element of struct inode called vi.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/