linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Paul Lawrence <paullawrence@google.com>,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-mm@kvack.org, linux-kbuild@vger.kernel.org,
	Matthias Kaehlcke <mka@chromium.org>,
	Michael Davidson <md@google.com>,
	Greg Hackmann <ghackmann@google.com>
Subject: Re: [PATCH v4 4/5] kasan: Add tests for alloca poisoning
Date: Tue, 5 Dec 2017 19:36:58 +0300	[thread overview]
Message-ID: <f0ae37b7-1560-f079-6c93-089c9e7b5a31@virtuozzo.com> (raw)
In-Reply-To: <20171204191735.132544-5-paullawrence@google.com>



On 12/04/2017 10:17 PM, Paul Lawrence wrote:
> Signed-off-by: Greg Hackmann <ghackmann@google.com>
> Signed-off-by: Paul Lawrence <paullawrence@google.com>
> ---
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>

--
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>

  reply	other threads:[~2017-12-05 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 19:17 [PATCH v4 0/5] kasan: support alloca, LLVM Paul Lawrence
2017-12-04 19:17 ` [PATCH v4 1/5] kasan: add compiler support for clang Paul Lawrence
2017-12-05 16:35   ` Andrey Ryabinin
2017-12-04 19:17 ` [PATCH v4 2/5] kasan/Makefile: Support LLVM style asan parameters Paul Lawrence
2017-12-08  9:25   ` Alexander Potapenko
2017-12-04 19:17 ` [PATCH v4 3/5] kasan: support alloca() poisoning Paul Lawrence
2017-12-05 16:36   ` Andrey Ryabinin
2017-12-04 19:17 ` [PATCH v4 4/5] kasan: Add tests for alloca poisoning Paul Lawrence
2017-12-05 16:36   ` Andrey Ryabinin [this message]
2017-12-04 19:17 ` [PATCH v4 5/5] kasan: added functions for unpoisoning stack variables Paul Lawrence
2017-12-05 16:37   ` Andrey Ryabinin

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=f0ae37b7-1560-f079-6c93-089c9e7b5a31@virtuozzo.com \
    --to=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=ghackmann@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=md@google.com \
    --cc=mka@chromium.org \
    --cc=paullawrence@google.com \
    --cc=yamada.masahiro@socionext.com \
    /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