[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+fCnZd2xPEwMGP7QRSyqHAJEbs_TY8Pg1ijG0iDFojMzphnfg@mail.gmail.com>
Date: Tue, 18 Mar 2025 16:32:46 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@...el.com>
Cc: kees@...nel.org, julian.stecklina@...erus-technology.de,
kevinloughlin@...gle.com, peterz@...radead.org, tglx@...utronix.de,
justinstitt@...gle.com, catalin.marinas@....com, wangkefeng.wang@...wei.com,
bhe@...hat.com, ryabinin.a.a@...il.com, kirill.shutemov@...ux.intel.com,
will@...nel.org, ardb@...nel.org, jason.andryuk@....com,
dave.hansen@...ux.intel.com, pasha.tatashin@...een.com,
guoweikang.kernel@...il.com, dwmw@...zon.co.uk, mark.rutland@....com,
broonie@...nel.org, apopple@...dia.com, bp@...en8.de, rppt@...nel.org,
kaleshsingh@...gle.com, richard.weiyang@...il.com, luto@...nel.org,
glider@...gle.com, pankaj.gupta@....com, pawan.kumar.gupta@...ux.intel.com,
kuan-ying.lee@...onical.com, tony.luck@...el.com, tj@...nel.org,
jgross@...e.com, dvyukov@...gle.com, baohua@...nel.org,
samuel.holland@...ive.com, dennis@...nel.org, akpm@...ux-foundation.org,
thomas.weissschuh@...utronix.de, surenb@...gle.com, kbingham@...nel.org,
ankita@...dia.com, nathan@...nel.org, ziy@...dia.com, xin@...or.com,
rafael.j.wysocki@...el.com, andriy.shevchenko@...ux.intel.com, cl@...ux.com,
jhubbard@...dia.com, hpa@...or.com, scott@...amperecomputing.com,
david@...hat.com, jan.kiszka@...mens.com, vincenzo.frascino@....com,
corbet@....net, maz@...nel.org, mingo@...hat.com, arnd@...db.de,
ytcoode@...il.com, xur@...gle.com, morbo@...gle.com,
thiago.bauermann@...aro.org, linux-doc@...r.kernel.org,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org, x86@...nel.org
Subject: Re: [PATCH v2 01/14] kasan: sw_tags: Use arithmetic shift for shadow computation
On Fri, Mar 14, 2025 at 4:58 PM Maciej Wieczor-Retman
<maciej.wieczor-retman@...el.com> wrote:
>
> >KASAN does nothing to deliberately prevent or detect races. Even if
> >the race leads to an OOB or UAF, KASAN might not be able to detect it.
> >But sometimes it does: if poisoned shadow memory values become visible
> >to the other thread/CPU before it makes a shadow memory value check.
>
> Thanks :)
>
> I've came up with a theoretical issue for the following dense series that might
> happen if there is some racing but I'll have to experiment if it actually
> happens.
As long as it doesn't lead to false positive reports or crashes in the
KASAN runtime - I think it should fine.
Powered by blists - more mailing lists