From: Kees Cook <keescook@chromium.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-mm <linux-mm@kvack.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Eric Biederman <ebiederm@xmission.com>
Subject: Re: WARNING: CPU: 6 PID: 474 at include/linux/maple_tree.h:712 mmap_region (include/linux/maple_tree.h:556 include/linux/maple_tree.h:731
Date: Wed, 6 Dec 2023 14:38:40 -0800 [thread overview]
Message-ID: <202312061435.E57F367C16@keescook> (raw)
In-Reply-To: <B4299DC4-57CF-4CB2-ACB1-A215F429BF6A@kernel.org>
On Thu, Nov 09, 2023 at 09:45:26PM -0800, Kees Cook wrote:
>
>
> On November 9, 2023 6:03:02 AM PST, Mark Brown <broonie@kernel.org> wrote:
> >On Thu, Nov 09, 2023 at 06:57:08PM +0530, Naresh Kamboju wrote:
> >> Following kernel panic noticed while running selftests: exec: load_address
> >> on Fastmodels (FVP) running Linux next-20231109.
> >>
> >
> >Copying in Kees and Eric who maintain the exec API.
>
> I'm traveling tomorrow so I won't be able to investigate this for a couple days. A quick look makes it seem like this is only happening in -next? (This warning was recently added to __mas_set_range?)
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/linux/maple_tree.h?id=02eccbc51164b43c5dadc3e5b40922c757075e08
>
> Adding Liam...
Did this get addressed? I still see the warning checks in
__mas_set_range()...
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-12-06 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:27 Naresh Kamboju
2023-11-09 14:03 ` Mark Brown
2023-11-10 5:45 ` Kees Cook
2023-12-06 22:38 ` Kees Cook [this message]
2023-12-07 1:41 ` Liam R. Howlett
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=202312061435.E57F367C16@keescook \
--to=keescook@chromium.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=ebiederm@xmission.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=will@kernel.org \
/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