linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Daniel Axtens <dja@axtens.net>,
	kasan-dev@googlegroups.com, linux-mm@kvack.org, x86@kernel.org,
	aryabinin@virtuozzo.com, glider@google.com, luto@kernel.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	dvyukov@google.com
Cc: linuxppc-dev@lists.ozlabs.org, gor@linux.ibm.com
Subject: Re: [PATCH v7 0/5] kasan: support backing vmalloc space with real shadow memory
Date: Wed, 11 Sep 2019 14:38:02 +0200	[thread overview]
Message-ID: <f1798d6b-96c5-18a7-3787-2307d0899b59@c-s.fr> (raw)
In-Reply-To: <87ftl39izy.fsf@dja-thinkpad.axtens.net>



Le 11/09/2019 à 13:20, Daniel Axtens a écrit :
> Hi Christophe,
> 
>> Are any other patches required prior to this series ? I have tried to
>> apply it on later powerpc/merge branch without success:
> 
> It applies on the latest linux-next. I didn't base it on powerpc/*
> because it's generic.
> 

Ok, thanks.

I backported it to powerpc/merge and I'm testing it on PPC32 with 
VMAP_STACK.

Got a few challenges but it is working now.

Christophe


      reply	other threads:[~2019-09-11 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 14:55 [PATCH v7 0/5] kasan: support backing vmalloc space with real shadow memory Daniel Axtens
2019-09-03 14:55 ` [PATCH v7 1/5] " Daniel Axtens
2019-09-03 14:55 ` [PATCH v7 2/5] kasan: add test for vmalloc Daniel Axtens
2019-09-03 14:55 ` [PATCH v7 3/5] fork: support VMAP_STACK with KASAN_VMALLOC Daniel Axtens
2019-09-03 14:55 ` [PATCH v7 4/5] x86/kasan: support KASAN_VMALLOC Daniel Axtens
2019-09-03 14:55 ` [PATCH v7 5/5] kasan debug: track pages allocated for vmalloc shadow Daniel Axtens
2019-09-03 15:01   ` Andrey Konovalov
2019-09-03 23:41     ` Daniel Axtens
2019-09-11  6:27 ` [PATCH v7 0/5] kasan: support backing vmalloc space with real shadow memory Christophe Leroy
2019-09-11 11:20   ` Daniel Axtens
2019-09-11 12:38     ` Christophe Leroy [this message]

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=f1798d6b-96c5-18a7-3787-2307d0899b59@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=aryabinin@virtuozzo.com \
    --cc=dja@axtens.net \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=gor@linux.ibm.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --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).