From: Arjan van de Ven <arjan@infradead.org>
To: Michel Lespinasse <walken@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Howells <dhowells@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Waychison <mikew@google.com>,
Suleiman Souhlal <suleiman@google.com>,
Ying Han <yinghan@google.com>
Subject: Re: [PATCH 11/11] Use down_read_critical() for /proc/<pid>/exe and /proc/<pid>/maps files
Date: Thu, 27 May 2010 07:12:05 -0700 [thread overview]
Message-ID: <20100527071205.7095a541@infradead.org> (raw)
In-Reply-To: <1274733081-4623-12-git-send-email-walken@google.com>
On Mon, 24 May 2010 13:31:21 -0700
Michel Lespinasse <walken@google.com> wrote:
> This helps in the following situation:
> - Thread A takes a page fault while reading or writing memory.
> do_page_fault() acquires the mmap_sem for read and blocks on disk
> (either reading the page from file, or hitting swap) for a long
> time.
> - Thread B does an mmap call and blocks trying to acquire the mmap_sem
> for write
> - Thread C is a monitoring process trying to read every /proc/pid/maps
> in the system. This requires acquiring the mmap_sem for read.
> Thread C blocks behind B, waiting for A to release the rwsem. If
> thread C could be allowed to run in parallel with A, it would
> probably get done long before thread A's disk access completes, thus
> not actually slowing down thread B.
>
> Test results with down_read_critical_test (10 seconds):
this is a really bad idea btw
we've had many issues in the past, when this was an unfair lock, that
"top" or other similar things, caused basically a DoS......
now any process that can get to /proc/<pid>/exe or maps, can do this in
a tight enough loop so that the actual process will never get the lock
for write. BAD IDEA ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2010-05-27 14:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 20:31 [PATCH 00/11] V4: rwsem changes + down_read_critical() proposal Michel Lespinasse
2010-05-24 20:31 ` [PATCH 01/11] x86 rwsem: stay on fast path when count>0 in __up_write() Michel Lespinasse
2010-05-24 20:31 ` [PATCH 02/11] x86 rwsem: minor cleanups Michel Lespinasse
2010-05-24 20:31 ` [PATCH 03/11] rwsem: fully separate code pathes to wake writers vs readers Michel Lespinasse
2010-05-24 20:31 ` [PATCH 04/11] rwsem: lighter active count checks when waking up readers Michel Lespinasse
2010-05-24 20:49 ` Daniel Walker
2010-05-24 20:31 ` [PATCH 05/11] rwsem: let RWSEM_WAITING_BIAS represent any number of waiting threads Michel Lespinasse
2010-05-24 20:31 ` [PATCH 06/11] rwsem: wake queued readers when writer blocks on active read lock Michel Lespinasse
2010-08-12 1:24 ` Tony Luck
2010-08-12 5:02 ` Michel Lespinasse
2010-08-12 5:09 ` Michel Lespinasse
2010-08-12 15:57 ` Linus Torvalds
2010-08-12 16:24 ` Tony Luck
2010-08-12 22:23 ` Tony Luck
2010-08-13 16:09 ` Tony Luck
2010-08-13 21:19 ` Tony Luck
2010-08-13 23:38 ` Tony Luck
2010-08-13 23:48 ` Michel Lespinasse
2010-08-12 16:22 ` Tony Luck
2010-05-24 20:31 ` [PATCH 07/11] rwsem: smaller wrappers around rwsem_down_failed_common Michel Lespinasse
2010-05-24 20:31 ` [PATCH 08/11] generic rwsem: implement down_read_critical() / up_read_critical() Michel Lespinasse
2010-05-24 20:31 ` [PATCH 09/11] rwsem: down_read_critical infrastructure support Michel Lespinasse
2010-05-24 20:31 ` [PATCH 10/11] x86 rwsem: down_read_critical implementation Michel Lespinasse
2010-05-24 20:31 ` [PATCH 11/11] Use down_read_critical() for /proc/<pid>/exe and /proc/<pid>/maps files Michel Lespinasse
2010-05-24 21:12 ` Daniel Walker
2010-05-27 14:12 ` Arjan van de Ven [this message]
2010-05-25 8:47 ` [PATCH 00/11] V4: rwsem changes + down_read_critical() proposal Peter Zijlstra
2010-05-25 9:12 ` Michel Lespinasse
2010-05-25 9:27 ` Peter Zijlstra
2010-05-26 1:23 ` KAMEZAWA Hiroyuki
2010-05-27 11:02 ` Michel Lespinasse
2010-05-27 11:45 ` Peter Zijlstra
2010-05-27 10:59 ` Michel Lespinasse
2010-05-27 11:18 ` Peter Zijlstra
2010-05-27 11:47 ` Michel Lespinasse
2010-05-25 15:16 ` Linus Torvalds
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=20100527071205.7095a541@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=suleiman@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.com \
--cc=yinghan@google.com \
/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
Powered by JetHome