From: Linus Torvalds <torvalds@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, hugh <hugh@veritas.com>,
Paul E McKenney <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] another crazy idea to get rid of mmap_sem in faults
Date: Sun, 30 Nov 2008 11:27:53 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811301123320.24125@nehalem.linux-foundation.org> (raw)
In-Reply-To: <1227886959.4454.4421.camel@twins>
On Fri, 28 Nov 2008, Peter Zijlstra wrote:
>
> While pondering the page_fault retry stuff, I came up with the following
> idea.
I don't know if your idea is any good, but this part of your patch is
utter crap:
- if (!down_read_trylock(&mm->mmap_sem)) {
- if ((error_code & PF_USER) == 0 &&
- !search_exception_tables(regs->ip))
- goto bad_area_nosemaphore;
- down_read(&mm->mmap_sem);
- }
-
+ down_read(&mm->mmap_sem);
because the reason we do a down_read_trylock() is not because of any lock
order issue or anything like that, but really really fundamental: we want
to be able to print an oops, instead of deadlocking, if we take a page
fault in kernel code while holding/waiting-for the mmap_sem for writing.
... and I don't even see the reason why you did tht change anyway, since
it seems to be totally independent of all the other locking changes.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-11-30 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 15:42 Peter Zijlstra
2008-11-28 17:04 ` Paul E. McKenney
2008-11-30 19:27 ` Linus Torvalds [this message]
2008-11-30 19:42 ` Peter Zijlstra
2008-12-01 22:55 ` Hugh Dickins
2008-12-01 14:00 ` Christoph Lameter
2008-12-01 14:48 ` Peter Zijlstra
2008-12-01 15:06 ` Christoph Lameter
2008-12-01 15:28 ` Peter Zijlstra
2008-12-01 16:22 ` Paul E. McKenney
2008-12-01 15:27 ` Lee Schermerhorn
2008-12-01 15:33 ` Peter Zijlstra
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=alpine.LFD.2.00.0811301123320.24125@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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