From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM/kirkwood: v3.12-rc6: kernel BUG at mm/util.c:390!
Date: Sun, 27 Oct 2013 13:47:19 +0000 [thread overview]
Message-ID: <20131027134718.GC16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131027134257.GB30783@mtj.dyndns.org>
On Sun, Oct 27, 2013 at 09:42:57AM -0400, Tejun Heo wrote:
> On Sun, Oct 27, 2013 at 09:16:53PM +0800, Ming Lei wrote:
> > On Sun, Oct 27, 2013 at 8:50 PM, Aaro Koskinen <aaro.koskinen@iki.fi> wrote:
> > >
> > > On ARM v3.9 or older kernels do not trigger this BUG, at seems it only
> > > started to appear with the following commit (bisected):
> > >
> > > commit 1bc39742aab09248169ef9d3727c9def3528b3f3
> > > Author: Simon Baatz <gmbnomis@gmail.com>
> > > Date: Mon Jun 10 21:10:12 2013 +0100
> > >
> > > ARM: 7755/1: handle user space mapped pages in flush_kernel_dcache_page
> >
> > The above commit only starts to implement the helper on ARM,
> > but according to Documentation/cachetlb.txt, looks caller of
> > flush_kernel_dcache_page() should make sure the passed
> > 'page' is a user space page.
>
> I don't think PageSlab() is the right test tho. Wouldn't testing
> against user_addr_max() make more sense?
How does that help for a function passed a struct page pointer?
next prev parent reply other threads:[~2013-10-27 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 20:07 ARM/kirkwood: v3.12-rc6: kernel BUG at mm/util.c:390! Aaro Koskinen
2013-10-26 14:36 ` Will Deacon
2013-10-26 17:23 ` Aaro Koskinen
2013-10-27 11:51 ` Ming Lei
2013-10-27 12:50 ` Aaro Koskinen
2013-10-27 13:16 ` Ming Lei
2013-10-27 13:42 ` Tejun Heo
2013-10-27 13:47 ` Russell King - ARM Linux [this message]
2013-10-27 13:53 ` Russell King - ARM Linux
2013-10-27 14:18 ` Simon Baatz
2013-10-28 12:48 ` Catalin Marinas
2013-10-27 14:19 ` Ming Lei
2013-10-28 14:13 ` Simon Baatz
2013-10-28 15:45 ` Ming Lei
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=20131027134718.GC16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).