From: Yury Gribov <y.gribov@samsung.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCHv3][Kasan][PING^2] Allow to override Asan shadow offset from command line
Date: Mon, 06 Oct 2014 11:17:00 -0000 [thread overview]
Message-ID: <54327A3D.3000007@samsung.com> (raw)
In-Reply-To: <5432779C.5030709@samsung.com>
On 10/06/2014 03:06 PM, Yury Gribov wrote:
> On 09/29/2014 09:21 PM, Yury Gribov wrote:
>> Hi all,
>>
>>>> Kasan developers has asked for an option to override offset of Asan
>>>> shadow memory region. This should simplify experimenting with memory
>>>> layouts on 64-bit architectures.
>>
>> New patch which checks that -fasan-shadow-offset is only enabled for
>> -fsanitize=kernel-address. I (unfortunately) can't make this --param
>> because this can be a 64-bit value.
>>
>> Bootstrapped and regtested on x64.
>>
>> -Y
Added Jakub.
next prev parent reply other threads:[~2014-10-06 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 14:29 [PATCH][Kasan] " Yury Gribov
2014-09-15 9:46 ` [PATCH][Kasan][PING] " Yury Gribov
2014-09-18 11:01 ` Jakub Jelinek
2014-09-18 11:05 ` Yury Gribov
2014-09-29 17:21 ` [PATCHv3][Kasan][PING] " Yury Gribov
2014-10-06 11:06 ` [PATCHv3][Kasan][PING^2] " Yury Gribov
2014-10-06 11:17 ` Yury Gribov [this message]
2014-10-15 16:19 ` [PATCHv3][Kasan][PING^3] " Yury Gribov
2014-10-15 16:54 ` Jakub Jelinek
2014-10-17 7:59 ` [PATCHv4][Kasan] " Yury Gribov
2014-10-17 11:25 ` Jakub Jelinek
2014-10-17 12:32 ` Ian Lance Taylor
2014-10-21 10:02 ` Yury Gribov
2014-10-24 13:58 ` [PATCHv5][Kasan] " Yury Gribov
2014-10-24 14:09 ` Jakub Jelinek
2014-10-27 16:02 ` Ian Lance Taylor
2014-11-05 14:50 ` Kirill Yukhin
2014-11-12 16:22 ` H.J. Lu
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=54327A3D.3000007@samsung.com \
--to=y.gribov@samsung.com \
--cc=a.ryabinin@samsung.com \
--cc=dvyukov@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=konstantin.s.serebryany@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).