On 06/02/2016 03:02 PM, Alexander Potapenko wrote:
> On Wed, Jun 1, 2016 at 6:31 PM, Alexander Potapenko wrote:
>> On Wed, Jun 1, 2016 at 5:23 PM, Andrey Ryabinin
>> wrote:
>>> On 05/31/2016 08:49 PM, Alexander Potapenko wrote:
On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin
wrote:
On Thu, Jun 2, 2016 at 2:17 PM, Andrey Ryabinin wrote:
>
>
> On 06/02/2016 03:02 PM, Alexander Potapenko wrote:
>> On Wed, Jun 1, 2016 at 6:31 PM, Alexander Potapenko
>> wrote:
>>> On Wed, Jun 1, 2016 at 5:23 PM, Andrey Ryabinin
>>> wrote:
On 05/31/2016 08:49 PM, Alexander Potapenko wrote
On Wed, Jun 1, 2016 at 6:31 PM, Alexander Potapenko wrote:
> On Wed, Jun 1, 2016 at 5:23 PM, Andrey Ryabinin
> wrote:
>> On 05/31/2016 08:49 PM, Alexander Potapenko wrote:
>>> On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin
>>> wrote:
On 05/31/2016 01:44 PM, Alexander Potapenko
On Wed, Jun 1, 2016 at 5:23 PM, Andrey Ryabinin wrote:
> On 05/31/2016 08:49 PM, Alexander Potapenko wrote:
>> On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin
>> wrote:
>>>
>>>
>>> On 05/31/2016 01:44 PM, Alexander Potapenko wrote:
Add a special shadow value to distinguish accesses to KASAN
On 05/31/2016 08:49 PM, Alexander Potapenko wrote:
> On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin
> wrote:
>>
>>
>> On 05/31/2016 01:44 PM, Alexander Potapenko wrote:
>>> Add a special shadow value to distinguish accesses to KASAN-specific
>>> allocator metadata.
>>>
>>> Unlike AddressSanitize
On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin
wrote:
>
>
> On 05/31/2016 01:44 PM, Alexander Potapenko wrote:
>> Add a special shadow value to distinguish accesses to KASAN-specific
>> allocator metadata.
>>
>> Unlike AddressSanitizer in the userspace, KASAN lets the kernel proceed
>> after a m
On 05/31/2016 01:44 PM, Alexander Potapenko wrote:
> Add a special shadow value to distinguish accesses to KASAN-specific
> allocator metadata.
>
> Unlike AddressSanitizer in the userspace, KASAN lets the kernel proceed
> after a memory error. However a write to the kmalloc metadata may cause
>
Add a special shadow value to distinguish accesses to KASAN-specific
allocator metadata.
Unlike AddressSanitizer in the userspace, KASAN lets the kernel proceed
after a memory error. However a write to the kmalloc metadata may cause
memory corruptions that will make the tool itself unreliable and
8 matches
Mail list logo