[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160216230409.GA24379@MBP.local>
Date: Tue, 16 Feb 2016 23:04:12 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Will Deacon <will.deacon@....com>,
"vladimir.murzin@....com" <vladimir.murzin@....com>,
"suzuki.poulose@....com" <suzuki.poulose@....com>,
Peter Zijlstra <peterz@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"salyzyn@...roid.com" <salyzyn@...roid.com>,
"riandrews@...roid.com" <riandrews@...roid.com>,
"james.morse@....com" <james.morse@....com>,
EunTaik Lee <eun.taik.lee@...sung.com>,
Peter Anvin <hpa@...or.com>,
Robin Murphy <robin.murphy@....com>,
"Dave.Martin@....com" <Dave.Martin@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] arm64: add alignment fault hanling
On Tue, Feb 16, 2016 at 01:31:36PM -0800, Arjan van de Ven wrote:
> On 2/16/2016 10:50 AM, Linus Torvalds wrote:
> >On Tue, Feb 16, 2016 at 9:04 AM, Will Deacon <will.deacon@....com> wrote:
> >>[replying to self and adding some x86 people]
> >>
> >>Background: Euntaik reports a problem where userspace has ended up with
> >>a memory page mapped adjacent to an MMIO page (e.g. from /dev/mem or a
> >>PCI memory bar from someplace in /sys). strncpy_from_user happens with
> >>the word-at-a-time implementation, and we end up reading into the MMIO
> >>page.
>
> how does this work if the adjacent page is not accessible?
do_strncpy_from_user() assumes by default that it can read a word at a
time using get_user() but checks its return value in case it failed and
falls back to byte at a time. What happens on arm64 is that for
alignment faults we don't have a handler that would search the exception
table and run the get_user() fixup.
> isn't the general rule for such basic functions "don't touch memory
> unless you KNOW it is there"
Well, user access routines are in general safe with this via the
exception handling + fixup mechanism (which usually returns -EFAULT).
That's what do_strncpy_from_user() tries to do by optimising away the
boundary checks.
--
Catalin
Powered by blists - more mailing lists