From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752250Ab3EPLLY (ORCPT ); Thu, 16 May 2013 07:11:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20342 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752156Ab3EPLLV (ORCPT ); Thu, 16 May 2013 07:11:21 -0400 Date: Thu, 16 May 2013 14:07:33 +0300 From: "Michael S. Tsirkin" To: linux-kernel@vger.kernel.org Cc: Catalin Marinas , Will Deacon , David Howells , Hirokazu Takata , Michal Simek , Koichi Yasutake , Benjamin Herrenschmidt , Paul Mackerras , Chris Metcalf , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , "H. Peter Anvin" , x86@kernel.org, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org, microblaze-uclinux@itee.uq.edu.au, linux-am33-list@redhat.com, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, kvm@vger.kernel.org Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mutt-Fcc: =sent Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Date: Thu, 16 May 2013 14:07:33 +0300 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline Sender: owner-linux-mm@kvack.org To: linux-kernel@vger.kernel.org Cc: Catalin Marinas , Will Deacon , David Howells , Hirokazu Takata , Michal Simek , Koichi Yasutake , Benjamin Herrenschmidt , Paul Mackerras , Chris Metcalf , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , "H. Peter Anvin" , x86@kernel.org, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org, microblaze-uclinux@itee.uq.edu.au, linux-am33-list@redhat.com, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.orglinux-m List-Id: linux-arch.vger.kernel.org This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Date: Thu, 16 May 2013 14:07:33 +0300 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Catalin Marinas , Will Deacon , David Howells , Hirokazu Takata , Michal Simek , Koichi Yasutake , Benjamin Herrenschmidt , Paul Mackerras , Chris Metcalf , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , "H. Peter Anvin" , x86@kernel.org, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org, microblaze-uclinux@itee.uq.edu.au, linux-am33-list@redhat.com, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org, linux-m To: linux-kernel@vger.kernel.org Return-path: Content-Disposition: inline Sender: owner-linux-mm@kvack.org List-Id: kvm.vger.kernel.org This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx146.postini.com [74.125.245.146]) by kanga.kvack.org (Postfix) with SMTP id 5AD4F6B0033 for ; Thu, 16 May 2013 07:09:09 -0400 (EDT) Date: Thu, 16 May 2013 14:07:33 +0300 From: "Michael S. Tsirkin" Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-linux-mm@kvack.org List-ID: To: linux-kernel@vger.kernel.org Cc: Catalin Marinas , Will Deacon , David Howells , Hirokazu Takata , Michal Simek , Koichi Yasutake , Benjamin Herrenschmidt , Paul Mackerras , Chris Metcalf , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , "H. Peter Anvin" , x86@kernel.org, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-m32r@ml.linux-m32r.org, linux-m32r-ja@ml.linux-m32r.org, microblaze-uclinux@itee.uq.edu.au, linux-am33-list@redhat.com, linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, kvm@vger.kernel.org This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by ozlabs.org (Postfix) with ESMTP id 89A852C0092 for ; Thu, 16 May 2013 21:09:50 +1000 (EST) Date: Thu, 16 May 2013 14:07:33 +0300 From: "Michael S. Tsirkin" To: linux-kernel@vger.kernel.org Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-m32r-ja@ml.linux-m32r.org, kvm@vger.kernel.org, Peter Zijlstra , Catalin Marinas , Will Deacon , David Howells , linux-mm@kvack.org, Paul Mackerras , "H. Peter Anvin" , linux-arch@vger.kernel.org, linux-am33-list@redhat.com, Hirokazu Takata , x86@kernel.org, Ingo Molnar , Arnd Bergmann , microblaze-uclinux@itee.uq.edu.au, Chris Metcalf , Thomas Gleixner , linux-arm-kernel@lists.infradead.org, Michal Simek , linux-m32r@ml.linux-m32r.org, Koichi Yasutake , linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST From mboxrd@z Thu Jan 1 00:00:00 1970 From: mst@redhat.com (Michael S. Tsirkin) Date: Thu, 16 May 2013 14:07:33 +0300 Subject: [PATCH v2 00/10] uaccess: better might_sleep/might_fault behavior Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org This improves the might_fault annotations used by uaccess routines: 1. The only reason uaccess routines might sleep is if they fault. Make this explicit for all architectures. 2. Accesses (e.g through socket ops) to kernel memory with KERNEL_DS like net/sunrpc does will never sleep. Remove an unconditinal might_sleep in the inline might_fault in kernel.h (used when PROVE_LOCKING is not set). 3. Accesses with pagefault_disable return EFAULT but won't cause caller to sleep. Check for that and avoid might_sleep when PROVE_LOCKING is set. I'd like these changes to go in for the benefit of the vhost driver where we want to call socket ops under a spinlock, and fall back on slower thread handler on error. Please review, and consider for 3.11. If the changes look good, what's the best way to merge them? Maybe core/locking makes sense? Note on arch code updates: I tested x86_64 code. Other architectures were build-tested. I don't have cross-build environment for arm64, tile, microblaze and mn10300 architectures. The changes look safe enough but would appreciate review/acks from arch maintainers. Version 1 of this change was titled x86: uaccess s/might_sleep/might_fault/ Changes from v1: add more architectures fix might_fault() scheduling differently depending on CONFIG_PROVE_LOCKING, as suggested by Ingo Michael S. Tsirkin (10): asm-generic: uaccess s/might_sleep/might_fault/ arm64: uaccess s/might_sleep/might_fault/ frv: uaccess s/might_sleep/might_fault/ m32r: uaccess s/might_sleep/might_fault/ microblaze: uaccess s/might_sleep/might_fault/ mn10300: uaccess s/might_sleep/might_fault/ powerpc: uaccess s/might_sleep/might_fault/ tile: uaccess s/might_sleep/might_fault/ x86: uaccess s/might_sleep/might_fault/ kernel: might_fault does not imply might_sleep arch/arm64/include/asm/uaccess.h | 4 ++-- arch/frv/include/asm/uaccess.h | 4 ++-- arch/m32r/include/asm/uaccess.h | 12 ++++++------ arch/microblaze/include/asm/uaccess.h | 6 +++--- arch/mn10300/include/asm/uaccess.h | 4 ++-- arch/powerpc/include/asm/uaccess.h | 16 ++++++++-------- arch/tile/include/asm/uaccess.h | 2 +- arch/x86/include/asm/uaccess_64.h | 2 +- include/asm-generic/uaccess.h | 10 +++++----- include/linux/kernel.h | 1 - mm/memory.c | 14 +++++++++----- 11 files changed, 39 insertions(+), 36 deletions(-) Thanks, -- MST