linux-kernel - RE: Domain faults when CONFIG_CPU_SW_DOMAIN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Dec 2015 08:33:13 +0000
From:	Peter Rosin <peda@...ntia.se>
To:	"Russell King (rmk+kernel@....linux.org.uk)" 
	<rmk+kernel@....linux.org.uk>
CC:	"'linux-arm-kernel@...ts.infradead.org'" 
	<linux-arm-kernel@...ts.infradead.org>,
	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: RE: Domain faults when CONFIG_CPU_SW_DOMAIN_PAN is enabled

I wrote:
> If I enable CONFIG_CPU_SW_DOMAIN_PAN, I sometimes (but not always) get the
> following (or very similar) on boot.

I should have said "if I don't disable", as the option is "default y".

Also, if it survives on boot, below is an example of later trouble (after 30+ minutes on
this occasion).

Cheers,
Peter

Unhandled fault: page domain fault (0x81b) at 0x00190f40
pgd = c2890000
[00190f40] *pgd=22f96831, *pte=21d9934f, *ppte=21d9983f
Internal error: : 81b [#1] ARM
Modules linked in:
CPU: 0 PID: 970 Comm: tse Not tainted 4.3.0+ #29
Hardware name: Atmel SAMA5
task: c3957480 ti: c2d62000 task.ti: c2d62000
PC is at memcpy+0x50/0x330
LR is at 0x0
pc : [<c01daff0>]    lr : [<00000000>]    psr: 80070013
sp : c2d63de4  ip : 00000000  fp : 00000000
r10: 00000000  r9 : 00000084  r8 : 00000000
r7 : 00000000  r6 : 1e6602e3  r5 : 00000000  r4 : 00000003
r3 : 00000002  r2 : ffffffe4  r1 : c2d63e4c  r0 : 00190f40
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
Control: 10c53c7d  Table: 22890059  DAC: 00000051
Process tse (pid: 970, stack limit = 0xc2d62208)
Stack: (0xc2d63de4 to 0xc2d64000)
3de0:          00000000 c2d62000 00000000 c2d63e2c 00190f40 00190f40 c01e76c4
3e00: c2f96640 c2fee874 00000000 00190f40 00000051 00000000 c2f7f000 c2ebd000
3e20: c3be3800 c0389620 400a0013 00000002 00000003 00000000 1e6602e3 00000000
3e40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3e60: 00000000 00000000 00000000 00000000 1e66a56c 000015f9 00000000 00000000
3e80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3ea0: 00000000 00000000 00000000 00000000 c3be3800 00190f40 c3a281c0 0000000e
3ec0: 00190f40 c038aa6c 00000001 c3be3800 b611b948 00001194 00000000 b5ffed8c
3ee0: c2d62000 c3be3800 00190f40 c3a281c0 0000000e 00190f40 c2d62000 00000000
3f00: 00000000 c038b704 00190f40 00000000 b611b948 00001194 c0844123 00190f40
3f20: c3be1c60 c3a281c0 0000000e 00190f40 c2d62000 c00a8b38 00000000 00000000
3f40: c2f14018 00000000 0000000d 00000000 b5ffedc0 00000000 0000000d 00000000
3f60: b5ffedc0 c00aa5dc 00000000 00000000 00190e10 c3a281c1 0000000e c3a281c0
3f80: c0844123 00190f40 c2d62000 c00a8d54 00190e10 00190dc0 00000000 00000036
3fa0: c0010224 c0010060 00190e10 00190dc0 0000000e c0844123 00190f40 00000000
3fc0: 00190e10 00190dc0 00000000 00000036 00000001 00000001 00000000 00000000
3fe0: b6c974a8 b5ffed7c b6c3d98d b6b2dc26 200a0030 0000000e 00000000 00000000
[<c01daff0>] (memcpy) from [<c01e76c4>] (__copy_to_user_memcpy+0x138/0x17c)
[<c01e76c4>] (__copy_to_user_memcpy) from [<c0389620>] (snd_pcm_sync_ptr+0x18c/0x1d0)
[<c0389620>] (snd_pcm_sync_ptr) from [<c038aa6c>] (snd_pcm_common_ioctl1+0x428/0xe4c)
[<c038aa6c>] (snd_pcm_common_ioctl1) from [<c038b704>] (snd_pcm_playback_ioctl1+0x274/0x5d4)
[<c038b704>] (snd_pcm_playback_ioctl1) from [<c00a8b38>] (do_vfs_ioctl+0x468/0x650)
[<c00a8b38>] (do_vfs_ioctl) from [<c00a8d54>] (SyS_ioctl+0x34/0x5c)
[<c00a8d54>] (SyS_ioctl) from [<c0010060>] (ret_fast_syscall+0x0/0x3c)
Code: f5d1f05c f5d1f07c e8b151f8 e2522020 (e8a051f8)
---[ end trace 680c06373934b76e ]---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/