[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8021dbc4-8745-2430-8d52-6236ae8c47c7@arm.com>
Date: Fri, 29 Jan 2021 18:46:38 +0000
From: Vincenzo Frascino <vincenzo.frascino@....com>
To: Andrey Konovalov <andreyknvl@...gle.com>,
Alexander Potapenko <glider@...gle.com>
Cc: Branislav Rankov <Branislav.Rankov@....com>,
Marco Elver <elver@...gle.com>,
Catalin Marinas <catalin.marinas@....com>,
Evgenii Stepanov <eugenis@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Will Deacon <will@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v9 3/4] kasan: Add report for async mode
Hi Andrey,
On 1/29/21 6:16 PM, Vincenzo Frascino wrote:
> 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.
I figured it out how trace_error_report_end() works. And in doing that I
realized that the problem is sync vs async, hence I agree with what you are
proposing:
if (addr) trace_error_report_end(...);
I will post v10 shortly. If we want to trace the async mode we can improve it in
-rc1.
--
Regards,
Vincenzo
Powered by blists - more mailing lists