Re: [PATCH] habanalabs: use %px instead of %p in error print

On Wed, Mar 6, 2019 at 9:42 PM Oded Gabbay wrote: > > On Thu, Mar 7, 2019 at 5:46 AM Kees Cook wrote: > > > > On Sat, Mar 2, 2019 at 1:43 AM Oded Gabbay wrote: > > > > > > When parsing the address of an internal command buffer, the driver prints > > > an error if the buffer's address is not in t

Re: [PATCH] habanalabs: use %px instead of %p in error print

On Thu, Mar 7, 2019 at 5:46 AM Kees Cook wrote: > > On Sat, Mar 2, 2019 at 1:43 AM Oded Gabbay wrote: > > > > When parsing the address of an internal command buffer, the driver prints > > an error if the buffer's address is not in the range of the device's DRAM > > or SRAM memory address space. >

Re: [PATCH] habanalabs: use %px instead of %p in error print

On Sat, Mar 2, 2019 at 1:43 AM Oded Gabbay wrote: > > When parsing the address of an internal command buffer, the driver prints > an error if the buffer's address is not in the range of the device's DRAM > or SRAM memory address space. > > Use %px to print the real address that the user gave the d

[PATCH] habanalabs: use %px instead of %p in error print

When parsing the address of an internal command buffer, the driver prints an error if the buffer's address is not in the range of the device's DRAM or SRAM memory address space. Use %px to print the real address that the user gave the driver and not a hashed value, so the user will get a clue rega