[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f1ad988d-6385-45e0-d683-048bfca0b9c0@arm.com>
Date: Fri, 29 Jan 2021 18:16:31 +0000
From: Vincenzo Frascino <vincenzo.frascino@....com>
To: Andrey Konovalov <andreyknvl@...gle.com>,
Alexander Potapenko <glider@...gle.com>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Marco Elver <elver@...gle.com>,
Evgenii Stepanov <eugenis@...gle.com>,
Branislav Rankov <Branislav.Rankov@....com>
Subject: Re: [PATCH v9 3/4] kasan: Add report for async mode
On 1/29/21 6:09 PM, Andrey Konovalov wrote:
> On Fri, Jan 29, 2021 at 6:56 PM Vincenzo Frascino
> <vincenzo.frascino@....com> wrote:
>>
>> Hi Andrey,
>>
>> On 1/29/21 5:40 PM, Andrey Konovalov wrote:
>>> I suggest to call end_report(&flags, 0) here and check addr !=0 in
>>> end_report() before calling trace_error_report_end().
>>>
>>
>> Probably this is better as:
>>
>> if (!IS_ENABLED(CONFIG_KASAN_HW_TAGS))
>>
>> Because that condition passes always addr == 0.
>
> Not sure I understand. Call report_end(&flags, 0) and then there do:
>
> if (addr) trace_error_report_end(...);
>
> Although maybe it makes sense to still trace all async bugs to address
> 0. Or to some magic address.
>
> Alex, WDYT?
>
What I meant is instead of:
if (addr) trace_error_report_end(...);
you might want to do:
if (!IS_ENABLED(CONFIG_KASAN_HW_TAGS)) trace_error_report_end(...);
because, could make sense to trace 0 in other cases?
I could not find the implementation of trace_error_report_end() hence I am not
really sure on what it does.
--
Regards,
Vincenzo
Powered by blists - more mailing lists