From: Andrew Morton <akpm@linux-foundation.org>
To: Andrey Konovalov <andreyknvl@gmail.com>
Cc: "Kuan-Ying Lee" <Kuan-Ying.Lee@mediatek.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Chinwen Chang" <chinwen.chang@mediatek.com>,
"Nicholas Tang" <nicholas.tang@mediatek.com>,
"James Hsu" <James.Hsu@mediatek.com>,
"Yee Lee" <Yee.Lee@mediatek.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH] kmemleak: fix kmemleak false positive report with HW tag-based kasan enable
Date: Sat, 27 Nov 2021 16:20:28 -0800 [thread overview]
Message-ID: <20211127162028.07d1a9fc392d91e7d234daae@linux-foundation.org> (raw)
In-Reply-To: <CA+fCnZchvHjU9G_SSf_M2--jHPqEa6PEr3u_5q-wJWvZK4N2pA@mail.gmail.com>
On Thu, 25 Nov 2021 17:13:36 +0100 Andrey Konovalov <andreyknvl@gmail.com> wrote:
> > > kmemleak_object *object)
> > > static struct kmemleak_object *lookup_object(unsigned long ptr, int
> > > alias)
> > > {
> > > struct rb_node *rb = object_tree_root.rb_node;
> > > + unsigned long untagged_ptr = (unsigned
> > > long)kasan_reset_tag((void *)ptr);
> > >
> > > while (rb) {
> > > struct kmemleak_object *object =
> > > rb_entry(rb, struct kmemleak_object, rb_node);
> > > - if (ptr < object->pointer)
> > > + unsigned long untagged_objp;
> > > +
> > > + untagged_objp = (unsigned long)kasan_reset_tag((void
> > > *)object->pointer);
>
> The two lines above can be squashed together.
That would make a too-long line even longer. In fact I think it's
better to go the other way:
--- a/mm/kmemleak.c~kmemleak-fix-kmemleak-false-positive-report-with-hw-tag-based-kasan-enable-fix
+++ a/mm/kmemleak.c
@@ -384,10 +384,10 @@ static struct kmemleak_object *lookup_ob
unsigned long untagged_ptr = (unsigned long)kasan_reset_tag((void *)ptr);
while (rb) {
- struct kmemleak_object *object =
- rb_entry(rb, struct kmemleak_object, rb_node);
+ struct kmemleak_object *object;
unsigned long untagged_objp;
+ object = rb_entry(rb, struct kmemleak_object, rb_node);
untagged_objp = (unsigned long)kasan_reset_tag((void *)object->pointer);
if (untagged_ptr < untagged_objp)
_
next prev parent reply other threads:[~2021-11-28 0:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 5:44 [PATCH] kmemleak: fix kmemleak false positive report with HW tag-based kasan enable Kuan-Ying Lee
2021-11-18 9:20 ` Kuan-Ying Lee
2021-11-19 14:15 ` Andrey Konovalov
2021-11-19 15:12 ` Kuan-Ying Lee
2021-11-19 22:43 ` Andrew Morton
2021-11-24 2:00 ` Kuan-Ying Lee
2021-11-25 16:13 ` Andrey Konovalov
2021-11-28 0:20 ` Andrew Morton [this message]
2021-12-02 18:19 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211127162028.07d1a9fc392d91e7d234daae@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Hsu@mediatek.com \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=Yee.Lee@mediatek.com \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=chinwen.chang@mediatek.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=nicholas.tang@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).