From mboxrd@z Thu Jan 1 00:00:00 1970 From: a.ryabinin@samsung.com (Andrey Ryabinin) Date: Fri, 10 Apr 2015 13:48:52 +0300 Subject: [PATCH 2/2] arm64: add KASan support In-Reply-To: <3164609.kEhR8riVSV@wuerfel> References: <1427208544-8232-1-git-send-email-a.ryabinin@samsung.com> <1427208544-8232-3-git-send-email-a.ryabinin@samsung.com> <3164609.kEhR8riVSV@wuerfel> Message-ID: <5527AA94.5080803@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/09/2015 11:17 PM, Arnd Bergmann wrote: > On Tuesday 24 March 2015 17:49:04 Andrey Ryabinin wrote: >> arch/arm64/mm/kasan_init.c | 211 +++++++++++++++++++++++++++++++++++ >> > > Just one very high-level question: as this code is clearly derived from > the x86 version and nontrivial, could we move most of it out of > arch/{x86,arm64} into mm/kasan/init.c and have the rest in some header > file? > I think most of this could be moved out from arch code, but not everything. E.g. kasan_init() function is too arch-specific. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) by kanga.kvack.org (Postfix) with ESMTP id 458196B0038 for ; Fri, 10 Apr 2015 06:49:03 -0400 (EDT) Received: by paboj16 with SMTP id oj16so18296542pab.0 for ; Fri, 10 Apr 2015 03:49:02 -0700 (PDT) Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com. [210.118.77.13]) by mx.google.com with ESMTPS id f6si2376074pdn.231.2015.04.10.03.49.01 for (version=TLSv1 cipher=RC4-MD5 bits=128/128); Fri, 10 Apr 2015 03:49:02 -0700 (PDT) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0NML00FSO7KDHZ50@mailout3.w1.samsung.com> for linux-mm@kvack.org; Fri, 10 Apr 2015 11:53:01 +0100 (BST) Message-id: <5527AA94.5080803@samsung.com> Date: Fri, 10 Apr 2015 13:48:52 +0300 From: Andrey Ryabinin MIME-version: 1.0 Subject: Re: [PATCH 2/2] arm64: add KASan support References: <1427208544-8232-1-git-send-email-a.ryabinin@samsung.com> <1427208544-8232-3-git-send-email-a.ryabinin@samsung.com> <3164609.kEhR8riVSV@wuerfel> In-reply-to: <3164609.kEhR8riVSV@wuerfel> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Arnd Bergmann , linux-arm-kernel@lists.infradead.org Cc: Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton On 04/09/2015 11:17 PM, Arnd Bergmann wrote: > On Tuesday 24 March 2015 17:49:04 Andrey Ryabinin wrote: >> arch/arm64/mm/kasan_init.c | 211 +++++++++++++++++++++++++++++++++++ >> > > Just one very high-level question: as this code is clearly derived from > the x86 version and nontrivial, could we move most of it out of > arch/{x86,arm64} into mm/kasan/init.c and have the rest in some header > file? > I think most of this could be moved out from arch code, but not everything. E.g. kasan_init() function is too arch-specific. -- 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: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932261AbbDJKtG (ORCPT ); Fri, 10 Apr 2015 06:49:06 -0400 Received: from mailout3.w1.samsung.com ([210.118.77.13]:59975 "EHLO mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754140AbbDJKtB (ORCPT ); Fri, 10 Apr 2015 06:49:01 -0400 X-AuditID: cbfec7f5-b7f1e6d00000617c-a2-5527a9ec9461 Message-id: <5527AA94.5080803@samsung.com> Date: Fri, 10 Apr 2015 13:48:52 +0300 From: Andrey Ryabinin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-version: 1.0 To: Arnd Bergmann , linux-arm-kernel@lists.infradead.org Cc: Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton Subject: Re: [PATCH 2/2] arm64: add KASan support References: <1427208544-8232-1-git-send-email-a.ryabinin@samsung.com> <1427208544-8232-3-git-send-email-a.ryabinin@samsung.com> <3164609.kEhR8riVSV@wuerfel> In-reply-to: <3164609.kEhR8riVSV@wuerfel> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsVy+t/xa7pvVqqHGkyczGsxZ/0aNou/k46x W7xf1sNosenxNVaLy7vmsFncW/Of1eLlxxMsDuwea+atYfT4/WsSo8emT5PYPU7M+M3isXlJ vcfnTXIBbFFcNimpOZllqUX6dglcGf8fTmAsWMNS8bn3IWsD427mLkZODgkBE4lVz1ZC2WIS F+6tZ+ti5OIQEljKKHFt4TQop5lJovXrIzaQKl4BLYlL7WfAbBYBVYlJ85cwgdhsAnoS/2Zt B4pzcIgKREjcvswJUS4o8WPyPRYQW0TAXWLd9HmsIDOZBTYySvTMWgG2WVjAUGLx5b1gRUIC CxglLs21ALE5BTQlbiw8wA4ykxlo/v2LWiBhZgF5ic1r3jJPYBSYhWTFLISqWUiqFjAyr2IU TS1NLihOSs810itOzC0uzUvXS87P3cQICfWvOxiXHrM6xCjAwajEw/uDRS1UiDWxrLgy9xCj BAezkggv2xL1UCHelMTKqtSi/Pii0pzU4kOMTBycUg2Mi9ffOHmhIlatevu9f5IqnPPqKpcZ Rzv2pJxcsrdy3pGw288kjHjrKm4ccd6+RPPgYdd2v6nCLeYBCs7r64/XzJSfea/5wd2Hvw6c 8paQs/PoUYhZ4aPFsHNF8Q4tns1XHyrcvM3Cseq/qpflgU+aC0xrlFSmTTkxJ13KV++HWM/i xxNuWGw0UmIpzkg01GIuKk4EABTQVOhTAgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/09/2015 11:17 PM, Arnd Bergmann wrote: > On Tuesday 24 March 2015 17:49:04 Andrey Ryabinin wrote: >> arch/arm64/mm/kasan_init.c | 211 +++++++++++++++++++++++++++++++++++ >> > > Just one very high-level question: as this code is clearly derived from > the x86 version and nontrivial, could we move most of it out of > arch/{x86,arm64} into mm/kasan/init.c and have the rest in some header > file? > I think most of this could be moved out from arch code, but not everything. E.g. kasan_init() function is too arch-specific.