From: Jason Gunthorpe Subject: Re: [PATCH v1 iproute2-next 2/3] rdma: print driver resource attributes Date: Tue, 15 May 2018 09:14:32 -0600 Message-ID: <20180515151432.GF5615@ziepe.ca> References: <1a0d146dffb17449aa6d8a6b6d06e865e69226de.1525709213.git.swise@opengridcomputing.com> <20180514204125.GM21531@ziepe.ca> <20180515085411.GT10381@mtr-leonro.mtl.com> <00fe01d3ec4f$44a6f400$cdf4dc00$@opengridcomputing.com> <20180515135335.GA5615@ziepe.ca> <012201d3ec59$69242fa0$3b6c8ee0$@opengridcomputing.com> <20180515144420.GB5615@ziepe.ca> <015b01d3ec5d$b1db4f90$1591eeb0$@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <015b01d3ec5d$b1db4f90$1591eeb0$@opengridcomputing.com> Sender: netdev-owner@vger.kernel.org To: Steve Wise Cc: 'Leon Romanovsky' , dsahern@gmail.com, stephen@networkplumber.org, netdev@vger.kernel.org, linux-rdma@vger.kernel.org List-Id: linux-rdma@vger.kernel.org On Tue, May 15, 2018 at 10:02:08AM -0500, Steve Wise wrote: > > On Tue, May 15, 2018 at 09:31:27AM -0500, Steve Wise wrote: > > > > cap net admin is not high enough privledge to see unhashed kernel > > > > pointers. CAP_RAW_IO? Or follow what printk does? > > > > > > > > > > Do you mean CAP_NET_RAW? Here's the comments for it: > > > > Nope.. > > > > > Func restricted_pointer() from lib/vsprintf.c uses CAP_SYSLOG. The > > comment for CAP_SYSLOG: > > > > Yikes, yes, that is probably the required logic here, including the > > kptr_restrict = 0 thing > > > > Let's defer the ktpr_restrict issue for now; I want to finish the initial > work this cycle, and adding that will likely take too much time. I'll use > CAP_SYSLOG and add a FIXME comment. Ok? Lets just drop wr_id instead... Jason