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

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: How to explain to lock validator: locking inodes in inode order
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [patch] gitignore quilt's files
• Next by Date: shut down from CPU 0 [regression]
• Previous by thread: CPU numbering & hyperthreading
• Next by thread: Re: How to explain to lock validator: locking inodes in inode order
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]