From: Dave Jones <davej@codemonkey.org.uk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Wong Vee Khee <vee.khee.wong@ni.com>,
Bodong Wang <bodong@mellanox.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
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
Date: Mon, 27 Nov 2017 16:30:01 -0500 [thread overview]
Message-ID: <20171127213001.GA12537@codemonkey.org.uk> (raw)
In-Reply-To: <20171124001139.bmuq6dkj63wuqzls@wfg-t540p.sh.intel.com>
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
next prev parent reply other threads:[~2017-11-27 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 0:11 [trinity] WARNING: CPU: 0 PID: 515 at drivers/pci/pci-sysfs.c:1224 pci_mmap_resource+0xd6/0x10e Fengguang Wu
2017-11-27 21:30 ` Dave Jones [this message]
2017-11-28 12:21 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171127213001.GA12537@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=arvind.yadav.cs@gmail.com \
--cc=bhelgaas@google.com \
--cc=bodong@mellanox.com \
--cc=dwmw@amazon.co.uk \
--cc=emil.s.tantilov@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@01.org \
--cc=vee.khee.wong@ni.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox