[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6wdzi5lszeaycdfjjowrbsnniks35zhatavknktskslwop5fne@uv5wzotu4ri4>
Date: Tue, 25 Feb 2025 21:12:57 +0100
From: Maciej Wieczor-Retman <maciej.wieczor-retman@...el.com>
To: Andrey Konovalov <andreyknvl@...il.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 2025-02-25 at 20:12:40 +0100, Maciej Wieczor-Retman wrote:
>On 2025-02-25 at 18:20:08 +0100, Maciej Wieczor-Retman wrote:
>>On 2025-02-22 at 16:06:02 +0100, Andrey Konovalov wrote:
>>>On Fri, Feb 21, 2025 at 2:12 PM Maciej Wieczor-Retman
>>><maciej.wieczor-retman@...el.com> wrote:
>>>> > Thus, the possible values a shadow address can
>>>> >take are the result of the memory-to-shadow mapping applied to
>>>> >[0xff00000000000000, 0xffffffffffffffff], not to the whole address
>>>> >space. So we can make this check more precise.
>>>>
>>>> In case my question above didn't lead to this: what happens to the rest of the
>>>> values if they get plugged into kasan_mem_to_shadow()?
>>>
>>>We will get some invalid addresses. But this should never happen in
>>>the first place.
>>
>>Thanks for letting me know about the tag resets, that should make changing the
>>check in kasan_non_canonical_hook() easier.
>
>Ah, but the [0xff00000000000000, 0xffffffffffffffff] won't be true for x86
>right? Here the tag reset function only resets bits 60:57. So I presume
>[0x3e00000000000000, 0xffffffffffffffff] would be the range?
Sorry, brain freeze, I meant [0x1e00000000000000, 0xffffffffffffffff]
--
Kind regards
Maciej Wieczór-Retman
Powered by blists - more mailing lists