From: "David S. Miller" <davem@redhat.com>
To: aprasad@in.ibm.com
Cc: bsuparna@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Oddness in i_shared_lock and page_table_lock nesting hierarchies ?
Date: Thu, 9 Nov 2000 23:34:26 -0800 [thread overview]
Message-ID: <200011100734.XAA26767@pizda.ninka.net> (raw)
In-Reply-To: <CA256993.0026C8BD.00@d73mta05.au.ibm.com> (aprasad@in.ibm.com)
In-Reply-To: <CA256993.0026C8BD.00@d73mta05.au.ibm.com>
From: aprasad@in.ibm.com
Date: Fri, 10 Nov 2000 12:25:24 +0530
this link might be useful
http://mail.nl.linux.org/linux-mm/2000-07/msg00038.html
This talks about a completely different bug.
We are talking here about inconsistant ordering of lock acquisition
when both mapping->i_shared_lock and mm->page_table_lock must be
held simultaneously.
The thread you quoted merely mentions the issue we have mm->rss
modifications are not always protected properly by the
page_table_lock.
There were no previous public discussions about the
i_shared_lock/page_table_lock deadlock problems.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-10 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 6:55 aprasad
2000-11-10 7:34 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-10 9:29 bsuparna
2000-11-09 12:16 bsuparna
2000-11-10 6:44 ` David S. Miller
2000-11-06 13:50 bsuparna
2000-11-05 5:51 bsuparna
2000-11-06 3:14 ` David S. Miller
2000-11-06 18:42 ` tytso
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=200011100734.XAA26767@pizda.ninka.net \
--to=davem@redhat.com \
--cc=aprasad@in.ibm.com \
--cc=bsuparna@in.ibm.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®