linux-kernel - [trinity] WARNING: CPU: 0 PID: 515 at drivers/pci/pci-sysfs.c:1224 pci_mmap

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]

Message-ID: <20171124001139.bmuq6dkj63wuqzls@wfg-t540p.sh.intel.com>
Date:   Fri, 24 Nov 2017 08:11:39 +0800
From:   Fengguang Wu <fengguang.wu@...el.com>
To:     Dave Jones <davej@...emonkey.org.uk>, linux-pci@...r.kernel.org
Cc:     Bjorn Helgaas <bhelgaas@...gle.com>,
        David Woodhouse <dwmw@...zon.co.uk>,
        Wong Vee Khee <vee.khee.wong@...com>,
        Bodong Wang <bodong@...lanox.com>,
        Emil Tantilov <emil.s.tantilov@...el.com>,
        Arvind Yadav <arvind.yadav.cs@...il.com>,
        linux-kernel@...r.kernel.org, lkp@...org
Subject: [trinity] WARNING: CPU: 0 PID: 515 at drivers/pci/pci-sysfs.c:1224
 pci_mmap_resource+0xd6/0x10e

Hello,

FYI this happens in mainline kernel 4.14.0-12995-g0c86a6b.
It at least dates back to v4.9 .

I wonder where can we avoid this warning, by improving trinity (or how
we use it), or the pci subsystem?

[main] Added 42 filenames from /dev
[main] Added 13651 filenames from /proc
[main] Added 11163 filenames from /sys
[   19.452176] ------------[ cut here ]------------
[   19.452938] process "trinity-main" tried to map 0x00004000 bytes at page 0x00000001 on 0000:00:06.0 BAR 4 (start 0x        fe008000, size 0x            4000)
[   19.454804] WARNING: CPU: 0 PID: 515 at drivers/pci/pci-sysfs.c:1224 pci_mmap_resource+0xd6/0x10e
[   19.456192] Modules linked in:
[   19.456671] CPU: 0 PID: 515 Comm: trinity-main Not tainted 4.14.0-12995-g0c86a6b #26
[   19.457739] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[   19.458840] task: cc536d80 task.stack: ccdac000
[   19.459465] EIP: pci_mmap_resource+0xd6/0x10e
[   19.460157] EFLAGS: 00010296 CPU: 0
[   19.460662] EAX: 00000091 EBX: cc536d80 ECX: 00000003 EDX: 3d5ff8cb
[   19.461461] ESI: cc7c8900 EDI: 00000004 EBP: ccdade5c ESP: ccdade20
[   19.462231]  DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068
[   19.462956] CR0: 80050033 CR2: 0a1130a0 CR3: 0c652000 CR4: 00140690
[   19.463778] DR0: b6cf4000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[   19.464635] DR6: ffff0ff0 DR7: 00000600
[   19.465186] Call Trace:
[   19.465584]  pci_mmap_resource_uc+0x17/0x19:
						pci_mmap_resource_uc at drivers/pci/pci-sysfs.c:1237
[   19.473271]  sysfs_kf_bin_mmap+0x20/0x27:
						sysfs_kf_bin_mmap at fs/sysfs/file.c:173
[   19.473836]  kernfs_fop_mmap+0x5d/0xc2:
						kernfs_fop_mmap at fs/kernfs/file.c:494
[   19.474391]  mmap_region+0x215/0x365:
						mmap_region at mm/mmap.c:1706
[   19.474922]  do_mmap+0x261/0x2b7:
						do_mmap at mm/mmap.c:1484
[   19.475420]  vm_mmap_pgoff+0x55/0x85:
						do_mmap_pgoff at include/linux/mm.h:2203
						 (inlined by) vm_mmap_pgoff at mm/util.c:333
[   19.476015]  SYSC_mmap_pgoff+0x108/0x124:
						SYSC_mmap_pgoff at mm/mmap.c:1535
[   19.476859]  ? rcu_read_unlock+0x1d/0x1f:
						rcu_read_unlock at include/linux/rcupdate.h:688
						
						rcu_read_unlock+0x1d/0x1f:
						rcu_read_unlock at include/linux/rcupdate.h:688
						
[   19.477468]  SyS_mmap_pgoff+0x1f/0x21
[   19.477979]  do_int80_syscall_32+0x49/0x5b:
						do_syscall_32_irqs_on at arch/x86/entry/common.c:327
						 (inlined by) do_int80_syscall_32 at arch/x86/entry/common.c:341
[   19.478541]  entry_INT80_32+0x31/0x31:
						restore_all at arch/x86/entry/entry_32.S:539
[   19.479061] EIP: 0x809af42
[   19.479465] EFLAGS: 00000202 CPU: 0
[   19.479983] EAX: ffffffda EBX: 00000000 ECX: 00004000 EDX: 00000003
[   19.480813] ESI: 00000002 EDI: 0000009c EBP: 00000001 ESP: bfa847d8
[   19.481671]  DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
[   19.482382] Code: 03 ff 75 f0 ff 75 ec 51 52 57 50 8b 46 04 2b 06 8b 1d 30 b9 9b c1 8d 93 d4 03 00 00 ff 76 4c 50 52 68 b6 a1 8e c1 e8 29 35 d1 ff <0f> ff b8 ea ff ff ff 83 c4 28 eb 24 89 f8 ff 75 08 89 f1 c1 e0
[   19.484906] ---[ end trace f644b8832412607a ]---
01 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 00 00 00 3a 28 9b 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

It occurs in 1 out of 2 boots.  Attached the full dmesg and kconfig.

Thanks,
Fengguang

View attachment "dmesg-yocto-ivb41-75:20171122010352:i386-randconfig-n0-201747:4.14.0-12995-g0c86a6b:26" of type "text/plain" (93061 bytes)

View attachment ".config" of type "text/plain" (123244 bytes)