From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Nick Piggin <npiggin@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] splice mmap_sem deadlock
Date: Fri, 28 Sep 2007 13:02:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0709281247490.3579@woody.linux-foundation.org> (raw)
In-Reply-To: <20070928193017.GC11717@kernel.dk>
On Fri, 28 Sep 2007, Jens Axboe wrote:
>
> Hmm, part of me doesn't like this patch, since we now end up beating on
> mmap_sem for each part of the vec. It's fine for a stable patch, but how
> about
>
> - prefaulting the iovec
> - using __get_user()
> - only dropping/regrabbing the lock if we have to fault
"__get_user()" doesn't help any. But we should do the same thing we do for
generic_file_write(), or whatever - probe it while in an atomic region.
So something like the appended might work. Untested.
Linus
---
fs/splice.c | 32 +++++++++++++++++++++-----------
1 files changed, 21 insertions(+), 11 deletions(-)
diff --git a/fs/splice.c b/fs/splice.c
index c010a72..07e880e 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -1236,31 +1236,41 @@ static int get_iovec_page_array(const struct iovec __user *iov,
{
int buffers = 0, error = 0;
- /*
- * It's ok to take the mmap_sem for reading, even
- * across a "get_user()".
- */
down_read(¤t->mm->mmap_sem);
while (nr_vecs) {
unsigned long off, npages;
+ struct iovec entry;
void __user *base;
size_t len;
int i;
/*
- * Get user address base and length for this iovec.
+ * We do not want to recursively take the mmap_sem semaphore
+ * on a page fault, since that could deadlock with a writer
+ * that comes in in the middle. So disable pagefaults, and
+ * do it the slow way if the copy fails..
*/
- error = get_user(base, &iov->iov_base);
- if (unlikely(error))
- break;
- error = get_user(len, &iov->iov_len);
- if (unlikely(error))
- break;
+ pagefault_disable();
+ i = __copy_from_user_inatomic(&entry, iov, sizeof(entry));
+ pagefault_enable();
+
+ if (unlikely(i)) {
+ up_read(¤t->mm->mmap_sem);
+ i = copy_from_user(&entry, iov, sizeof(entry));
+ down_read(¤t->mm->mmap_sem);
+ error = -EFAULT;
+ if (i)
+ break;
+ }
+
+ len = entry.iov_len;
+ base = entry.iov_base;
/*
* Sanity check this iovec. 0 read succeeds.
*/
+ error = 0;
if (unlikely(!len))
break;
error = -EFAULT;
--
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:[~2007-09-28 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 16:00 Nick Piggin
2007-09-28 17:31 ` Jens Axboe
2007-09-28 18:10 ` Linus Torvalds
2007-09-28 18:15 ` Jens Axboe
2007-09-28 18:23 ` Linus Torvalds
2007-09-28 19:30 ` Jens Axboe
2007-09-28 20:02 ` Linus Torvalds [this message]
2007-09-28 20:08 ` Linus Torvalds
2007-09-29 6:37 ` Jens Axboe
2007-10-01 12:03 ` Jens Axboe
2007-10-01 15:11 ` Linus Torvalds
2007-10-01 15:45 ` Balbir Singh
2007-10-01 16:11 ` Linus Torvalds
2007-10-01 18:19 ` Balbir Singh
2007-10-01 17:33 ` Jens Axboe
2007-09-29 13:10 ` Nick Piggin
2007-09-30 6:46 ` Jens Axboe
2007-09-30 12:07 ` Nick Piggin
2007-09-30 20:05 ` Jens Axboe
2007-09-30 20:12 ` Nick Piggin
2007-09-29 13:08 ` Nick Piggin
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.0.999.0709281247490.3579@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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