From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: hailong <hailongliiu@yeah.net>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Ziliang Guo <guo.ziliang@zte.com.cn>,
Hailong Liu <liu.hailong6@zte.com.cn>,
Russell King <linux@armlinux.org.uk>,
kasan-dev <kasan-dev@googlegroups.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm/kasan:fix the arry size of kasan_early_shadow_pte
Date: Mon, 11 Jan 2021 22:18:20 -0800 [thread overview]
Message-ID: <20210111221820.b252f44de1e0bf4add506776@linux-foundation.org> (raw)
In-Reply-To: <CACRpkdY7eYyVNvqMRYvTQsLNrXa+fzPsWA5JHDuS4nqry+CHcw@mail.gmail.com>
On Sun, 10 Jan 2021 13:03:49 +0100 Linus Walleij <linus.walleij@linaro.org> wrote:
> On Sun, Jan 10, 2021 at 11:21 AM hailong <hailongliiu@yeah.net> wrote:
>
> > >> +#ifndef PTE_HWTABLE_PTRS
> > >> +#define PTE_HWTABLE_PTRS 0
> > >> +#endif
> > >
> > >Can this even happen? We have either pgtable-2level.h or
> > >pgtable-3level.h, both of which define PTE_HWTABLE_PTRS.
> > >
> >
> > I guess not for arm. But I'm not sure for other ARCHs.
>
> Oh it's a generic include. Sorry for the confusion.
>
> All good then!
>
This code is 2+ years old. Do we think it warrants a cc:stable?
next prev parent reply other threads:[~2021-01-12 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 4:46 [PATCH] arm/kasan:fix the arry size of kasan_early_shadow_pte Hailong liu
2021-01-09 8:51 ` Ard Biesheuvel
2021-01-09 21:26 ` Linus Walleij
2021-01-10 10:20 ` hailong
2021-01-10 12:03 ` Linus Walleij
2021-01-12 6:18 ` Andrew Morton [this message]
2021-01-12 9:05 ` Ard Biesheuvel
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=20210111221820.b252f44de1e0bf4add506776@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=guo.ziliang@zte.com.cn \
--cc=hailongliiu@yeah.net \
--cc=kasan-dev@googlegroups.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=liu.hailong6@zte.com.cn \
/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).