From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to explain to lock validator: locking inodes in inode order
Date: Mon, 17 Jul 2006 19:24:53 -0700 [thread overview]
Message-ID: <bda6d13a0607171924v5cd15811v7c9749ad481b232d@mail.gmail.com> (raw)
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.
next reply other threads:[~2006-07-18 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 2:24 Joshua Hudson [this message]
2006-07-18 3:31 ` Arjan van de Ven
2006-07-18 4:19 ` Joshua Hudson
2006-07-18 9:09 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bda6d13a0607171924v5cd15811v7c9749ad481b232d@mail.gmail.com \
--to=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®