From: Andrew Morton <akpm@linux-foundation.org>
To: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
Cc: <aryabinin@virtuozzo.com>, <dvyukov@google.com>,
<glider@google.com>, <guangye.yang@mediatek.com>,
<matthias.bgg@gmail.com>, <miles.chen@mediatek.com>,
<mm-commits@vger.kernel.org>, <nicholas.tang@mediatek.com>,
<qcai@redhat.com>, <qiang.zhang@windriver.com>,
<sfr@canb.auug.org.au>
Subject: Re: [merged] kasan-fix-object-remain-in-offline-per-cpu-quarantine.patch removed from -mm tree
Date: Mon, 14 Dec 2020 10:19:57 -0800 [thread overview]
Message-ID: <20201214101957.51e0e05d2b7bf5d2f9707bd2@linux-foundation.org> (raw)
In-Reply-To: <1607924810.31376.14.camel@mtksdccf07>
On Mon, 14 Dec 2020 13:46:50 +0800 Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com> wrote:
> On Sat, 2020-12-12 at 22:05 -0800, akpm@linux-foundation.org wrote:
> > The patch titled
> > Subject: kasan: fix object remaining in offline per-cpu quarantine
> > has been removed from the -mm tree. Its filename was
> > kasan-fix-object-remain-in-offline-per-cpu-quarantine.patch
> >
> > This patch was dropped because it was merged into mainline or a subsystem tree
> >
>
> Hi Andrew,
>
> Sorry to bother.
> This patch has dependency with two patches of Andrey's patch series as
> below.
> "kasan: rename get_alloc/free_info"
> "kasan: sanitize objects when metadata doesnt fit"
Are you sure? Please check 5.10 and if there are problems there,
please propose a standalone fix.
next prev parent reply other threads:[~2020-12-14 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 6:05 [merged] kasan-fix-object-remain-in-offline-per-cpu-quarantine.patch removed from -mm tree akpm
2020-12-14 5:46 ` Kuan-Ying Lee
2020-12-14 18:19 ` Andrew Morton [this message]
2020-12-15 9:06 ` Kuan-Ying Lee
2020-12-17 13:50 ` Kuan-Ying Lee
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=20201214101957.51e0e05d2b7bf5d2f9707bd2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=guangye.yang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=mm-commits@vger.kernel.org \
--cc=nicholas.tang@mediatek.com \
--cc=qcai@redhat.com \
--cc=qiang.zhang@windriver.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.