From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: MT_HIGH_VECTOR mapping set read-only creating illegal access Date: Wed, 13 Apr 2011 08:26:16 +0100 Message-ID: <20110413072616.GJ7806@n2100.arm.linux.org.uk> References: <4DA4F170.4020009@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:37236 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756513Ab1DMH02 (ORCPT ); Wed, 13 Apr 2011 03:26:28 -0400 Content-Disposition: inline In-Reply-To: <4DA4F170.4020009@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Michael Bohan Cc: linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Tue, Apr 12, 2011 at 05:42:24PM -0700, Michael Bohan wrote: > Hi, > > In arch/arm/kernel/traps.c:set_tls() and arch/arm/include/asm/tls.h, > some configurations allow for a assignment of address 0xffff0ff0. This > address falls within the MT_HIGH_VECTORS mapping setup in > devicemaps_init(). That mapping is explicitly made read-only. Thus, the > kernel takes a segfault when writing in set_tls(). > > It looks like this disparity may have been introduced in this commit: > > commit 36bb94ba36f332de767cfaa3af6a5136435a3a9c > Author: Russell King > Date: Tue Nov 16 08:40:36 2010 +0000 > > ARM: pgtable: provide RDONLY page table bit rather than WRITE bit > > Signed-off-by: Russell King > > Is there a reason this mapping must be read-only? Perhaps we could apply > write access for these special cases only? Have you checked the behaviour immediately before this commit, and the behaviour with this commit applied?