[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241112230644.cfe24aa5e863112de04b16c0@linux-foundation.org>
Date: Tue, 12 Nov 2024 23:06:44 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Qun-Wei Lin <qun-wei.lin@...iatek.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>, Shakeel Butt
<shakeel.butt@...ux.dev>, Kent Overstreet <kent.overstreet@...ux.dev>,
Pasha Tatashin <pasha.tatashin@...een.com>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <catalin.marinas@....com>, Casper Li
<casper.li@...iatek.com>, Chinwen Chang <chinwen.chang@...iatek.com>,
Andrew Yang <andrew.yang@...iatek.com>, Elena Yu <elena.yu@...iatek.com>,
<wsd_upstream@...iatek.com>
Subject: Re: [PATCH] sched/task_stack: Fix object_is_on_stack() for KASAN
tagged pointers
On Wed, 13 Nov 2024 12:25:43 +0800 Qun-Wei Lin <qun-wei.lin@...iatek.com> wrote:
> When CONFIG_KASAN_SW_TAGS and CONFIG_KASAN_STACK are enabled, the
> object_is_on_stack() function may produce incorrect results due to the
> presence of tags in the obj pointer, while the stack pointer does not
> have tags. This discrepancy can lead to incorrect stack object detection
> and subsequently trigger warnings if CONFIG_DEBUG_OBJECTS is also
> enabled.
>
> Example of the warning:
Thanks.
Are we able to identify when this started happening? ie, a suitable
Fixes: taret?
Powered by blists - more mailing lists