From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Tyler Hicks <tyhicks@canonical.com>,
Josh Boyer <jwboyer@redhat.com>, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: hugetlbfs lockdep spew revisited.
Date: Fri, 17 Feb 2012 15:47:41 +0900 [thread overview]
Message-ID: <12592.1329461261@jrobl> (raw)
In-Reply-To: <20120217004922.GN23916@ZenIV.linux.org.uk>
Al Viro:
> Sigh... That patch is correct, but it has nothing to do with the locking
> order violation that really *is* there. The only benefit would be to
> get rid of the "deadlock is not possible" nonsense, since you would see
> read/write vs. mmap instead of readdir vs. mmap in the traces. Locking
:::
How do you think about this patch?
Re: [RFC 0/2] locking order of mm->mmap_sem and various FS
http://marc.info/?l=linux-kernel&m=132124846728745&w=2
Ah, I found mutex_destroy() call in hugetlbfs_destroy_inode() should be
removed.
If you think this approach is good, then I'd post a revised patch.
J. R. Okajima
next prev parent reply other threads:[~2012-02-17 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 0:08 hugetlbfs lockdep spew revisited Dave Jones
2012-02-17 0:16 ` Josh Boyer
2012-02-17 0:34 ` Al Viro
2012-02-17 0:38 ` Tyler Hicks
2012-02-17 0:49 ` Al Viro
2012-02-17 3:42 ` Tyler Hicks
2012-02-21 18:21 ` Mimi Zohar
2012-02-17 6:47 ` J. R. Okajima [this message]
2012-02-17 17:48 ` udf deadlock (was Re: hugetlbfs lockdep spew revisited.) Al Viro
2012-02-20 16:01 ` Jan Kara
2012-02-18 10:55 ` hugetlbfs lockdep spew revisited Aneesh Kumar K.V
2012-02-17 0:27 ` Al Viro
2012-02-23 9:27 ` Aneesh Kumar K.V
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=12592.1329461261@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=davej@redhat.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.com \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.