From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Will Deacon <will.deacon@arm.com>,
mhocko@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
x86@kernel.org, kasan-dev@googlegroups.com,
borntraeger@de.ibm.com, heiko.carstens@de.ibm.com,
davem@davemloft.net, willy@infradead.org,
ard.biesheuvel@linaro.org, mark.rutland@arm.com,
catalin.marinas@arm.com, sam@ravnborg.org,
mgorman@techsingularity.net, steven.sistare@oracle.com,
daniel.m.jordan@oracle.com, bob.picco@oracle.com
Subject: Re: [PATCH v12 08/11] arm64/kasan: add and use kasan_map_populate()
Date: Fri, 3 Nov 2017 18:40:47 +0300 [thread overview]
Message-ID: <07ab0b77-0e2a-97b5-73ff-a6598bcb94cd@virtuozzo.com> (raw)
In-Reply-To: <a587687a-5d90-c03d-f3d2-1ea9cab1b0c4@oracle.com>
On 10/18/2017 08:23 PM, Pavel Tatashin wrote:
> Hi Andrew and Michal,
>
> There are a few changes I need to do to my series:
>
> 1. Replace these two patches:
>
> arm64/kasan: add and use kasan_map_populate()
> x86/kasan: add and use kasan_map_populate()
>
> With:
>
> x86/mm/kasan: don't use vmemmap_populate() to initialize
> shadow
> arm64/mm/kasan: don't use vmemmap_populate() to initialize
> shadow
>
Pavel, could you please send the patches? These patches doesn't interfere with rest of the series,
so I think it should be enough to send just two patches to replace the old ones.
> 2. Fix a kbuild warning about section mismatch in
> mm: deferred_init_memmap improvements
>
> How should I proceed to get these replaced in mm-tree? Send three new patches, or send a new series?
>
> Thank you,
> Pavel
>
next prev parent reply other threads:[~2017-11-03 15:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 17:32 [PATCH v12 00/11] complete deferred page initialization Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 01/11] mm: deferred_init_memmap improvements Pavel Tatashin
2017-10-17 11:40 ` Michal Hocko
2017-10-17 15:13 ` Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 02/11] x86/mm: setting fields in deferred pages Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 03/11] sparc64/mm: " Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 04/11] sparc64: simplify vmemmap_populate Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 05/11] mm: defining memblock_virt_alloc_try_nid_raw Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 06/11] mm: zero reserved and unavailable struct pages Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 07/11] x86/kasan: add and use kasan_map_populate() Pavel Tatashin
2017-10-18 17:11 ` Andrey Ryabinin
2017-10-18 17:14 ` Pavel Tatashin
2017-10-18 17:20 ` Andrey Ryabinin
2017-10-13 17:32 ` [PATCH v12 08/11] arm64/kasan: " Pavel Tatashin
2017-10-18 16:55 ` Andrey Ryabinin
2017-10-18 17:03 ` Pavel Tatashin
2017-10-18 17:06 ` Will Deacon
2017-10-18 17:08 ` Pavel Tatashin
2017-10-18 17:18 ` Andrey Ryabinin
2017-10-18 17:23 ` Pavel Tatashin
2017-11-03 15:40 ` Andrey Ryabinin [this message]
2017-11-03 15:50 ` Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 09/11] mm: stop zeroing memory during allocation in vmemmap Pavel Tatashin
2017-10-19 23:59 ` Andrew Morton
2017-10-20 1:13 ` Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 10/11] sparc64: optimized struct page zeroing Pavel Tatashin
2017-10-13 17:32 ` [PATCH v12 11/11] arm64: kasan: Avoid using vmemmap_populate to initialise shadow Pavel Tatashin
2017-10-13 18:23 ` [PATCH v12 00/11] complete deferred page initialization Bob Picco
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=07ab0b77-0e2a-97b5-73ff-a6598bcb94cd@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bob.picco@oracle.com \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.m.jordan@oracle.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=steven.sistare@oracle.com \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).