From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: arm kernel oops in highmem.c with 4.2
Date: Wed, 12 Aug 2015 09:33:56 -0400 [thread overview]
Message-ID: <1439386436.3153.23.camel@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1508112116320.1515@knanqh.ubzr>
On Tue, 2015-08-11 at 22:18 -0400, Nicolas Pitre wrote:
> On Tue, 11 Aug 2015, Mark Salter wrote:
>
> > On Tue, 2015-08-11 at 16:20 -0400, Nicolas Pitre wrote:
> > > On Tue, 11 Aug 2015, Russell King - ARM Linux wrote:
> > >
> > > > It needs fixing or removing.
> > >
> > > Absolutely. I'm not disputing that. I'm only asking so we can wisely
> > > choose between fixing or removing. Personally I'd be inclined
> > > towards
> > > the later, unless the following is sufficient to fix it:
> > >
> > > diff --git a/arch/arm/lib/uaccess_with_memcpy.c
> > > b/arch/arm/lib/uaccess_with_memcpy.c
> > > index 3e58d71001..4b39af2dfd 100644
> > > --- a/arch/arm/lib/uaccess_with_memcpy.c
> > > +++ b/arch/arm/lib/uaccess_with_memcpy.c
> > > @@ -96,7 +96,7 @@ __copy_to_user_memcpy(void __user *to, const void
> > > *from, unsigned long n)
> > > }
> > >
> > > /* the mmap semaphore is taken only if not in an atomic
> > > context
> > > */
> > > - atomic = in_atomic();
> > > + atomic = faulthandler_disabled();
> > >
> > > if (!atomic)
> > > down_read(¤t->mm->mmap_sem);
> >
> > Yeah, that fixes the problem I was seeing.
>
> Good! Then I'll add it to RMK's patch system. May I add a tested-by
> tag with your name?
Yes
>
> > This was on a calxeda highbank.
>
> Any idea why this option was set?
None. It seems to have been there in the original fedora config
for v7 kernels. But nothing in the config turns on CPU_FEROCEON
so there is no real need for it.
>
> > With CONFIG_UACCESS_WITH_MEMCPY, the dd copy test reported 1.8GB/s
> > Without CONFIG_UACCESS_WITH_MEMCPY, 2.1GB/s
>
> Therefore this is of no benefit to you.
>
>
> Nicolas
next prev parent reply other threads:[~2015-08-12 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 10:01 arm kernel oops in highmem.c with 4.2 Peter Robinson
2015-08-05 10:07 ` Russell King - ARM Linux
2015-08-05 10:13 ` Peter Robinson
2015-08-05 11:27 ` Russell King - ARM Linux
2015-08-11 17:48 ` Mark Salter
2015-08-11 18:10 ` Russell King - ARM Linux
2015-08-11 19:41 ` Nicolas Pitre
2015-08-11 19:56 ` Russell King - ARM Linux
2015-08-11 20:20 ` Nicolas Pitre
2015-08-11 21:17 ` Mark Salter
2015-08-12 2:18 ` Nicolas Pitre
2015-08-12 13:33 ` Mark Salter [this message]
2015-08-12 15:50 ` Nicolas Pitre
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=1439386436.3153.23.camel@redhat.com \
--to=msalter@redhat.com \
--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).