From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752355AbdK0Va1 (ORCPT ); Mon, 27 Nov 2017 16:30:27 -0500 Received: from scorn.kernelslacker.org ([45.56.101.199]:32816 "EHLO scorn.kernelslacker.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751443AbdK0VaZ (ORCPT ); Mon, 27 Nov 2017 16:30:25 -0500 Date: Mon, 27 Nov 2017 16:30:01 -0500 From: Dave Jones To: Fengguang Wu Cc: linux-pci@vger.kernel.org, Bjorn Helgaas , David Woodhouse , Wong Vee Khee , Bodong Wang , Emil Tantilov , Arvind Yadav , linux-kernel@vger.kernel.org, lkp@01.org Subject: Re: [trinity] WARNING: CPU: 0 PID: 515 at drivers/pci/pci-sysfs.c:1224 pci_mmap_resource+0xd6/0x10e Message-ID: <20171127213001.GA12537@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Fengguang Wu , linux-pci@vger.kernel.org, Bjorn Helgaas , David Woodhouse , Wong Vee Khee , Bodong Wang , Emil Tantilov , Arvind Yadav , linux-kernel@vger.kernel.org, lkp@01.org References: <20171124001139.bmuq6dkj63wuqzls@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171124001139.bmuq6dkj63wuqzls@wfg-t540p.sh.intel.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Note: SpamAssassin invocation failed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 24, 2017 at 08:11:39AM +0800, Fengguang Wu wrote: > 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 That's a root-only operation, where we allow the user to shoot themselves in the foot afaik. What you could do now that you're running an up to date trinity in 0day, is pass the --dropprivs flag to setuid to nobody in the child processes. Dave