From: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrey Konovalov <andreyknvl@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Nicholas Tang <nicholas.tang@mediatek.com>,
Miles Chen <miles.chen@mediatek.com>,
kasan-dev <kasan-dev@googlegroups.com>,
"Linux Memory Management List" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
wsd_upstream <wsd_upstream@mediatek.com>
Subject: Re: [PATCH v3 1/1] kasan: fix object remain in offline per-cpu quarantine
Date: Fri, 4 Dec 2020 10:26:18 +0800 [thread overview]
Message-ID: <1607048778.15817.2.camel@mtksdccf07> (raw)
In-Reply-To: <20201203122854.c8d5ed270ec9cfc7c17569d9@linux-foundation.org>
On Thu, 2020-12-03 at 12:28 -0800, Andrew Morton wrote:
> On Thu, 3 Dec 2020 13:46:59 +0100 Andrey Konovalov <andreyknvl@google.com> wrote:
>
> > > #define QLIST_INIT { NULL, NULL, 0 }
> > > @@ -188,6 +190,11 @@ void quarantine_put(struct kasan_free_meta *info, struct kmem_cache *cache)
> > > local_irq_save(flags);
> > >
> > > q = this_cpu_ptr(&cpu_quarantine);
> > > + if (q->offline) {
> > > + qlink_free(&info->quarantine_link, cache);
> >
> > Hi Kuan-Ying,
> >
> > This needs to be rebased onto the mm tree: it has some KASAN patches
> > that touch this code and rename the info variable to meta.
>
> Yup. I'm taking care of that.
Hi Andrew,
Sorry about that.
I will fix that conflict.
Thanks.
next prev parent reply other threads:[~2020-12-04 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 7:53 [PATCH v3 0/1] Fix object remain in offline per-cpu quarantine Kuan-Ying Lee
2020-12-02 7:53 ` [PATCH v3 1/1] kasan: fix " Kuan-Ying Lee
2020-12-02 8:26 ` Dmitry Vyukov
2020-12-03 12:46 ` Andrey Konovalov
2020-12-03 20:28 ` Andrew Morton
2020-12-04 2:26 ` Kuan-Ying Lee [this message]
2020-12-03 17:10 ` Qian Cai
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=1607048778.15817.2.camel@mtksdccf07 \
--to=kuan-ying.lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.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=miles.chen@mediatek.com \
--cc=nicholas.tang@mediatek.com \
--cc=wsd_upstream@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).