Re: [PATCH v2 3/3] kvm: svm: Use the hardware provided GPA instead of page walk

Hi Paolo, On 12/13/2016 11:09 AM, Paolo Bonzini wrote: On 12/12/2016 18:51, Brijesh Singh wrote: As per the AMD BKDG [1] Section 2.7.1, we should not be using any of these instruction for MMIO access, the behavior is undefined. The question is, do we really need to add logic to detect the

Re: [PATCH v2 3/3] kvm: svm: Use the hardware provided GPA instead of page walk

Hi Paolo, On 12/13/2016 11:09 AM, Paolo Bonzini wrote: On 12/12/2016 18:51, Brijesh Singh wrote: As per the AMD BKDG [1] Section 2.7.1, we should not be using any of these instruction for MMIO access, the behavior is undefined. The question is, do we really need to add logic to detect the

Re: [RFC] block: check partition alignment

> To prevent partitions that are not aligned to the physical blocksize > of a device check for the alignment in the blkpg_ioctl. We'd also need to reject this when reading partitions from disk, right? > + /* check if partition is aligned to blocksize */ > +

Re: [RFC] block: check partition alignment

> To prevent partitions that are not aligned to the physical blocksize > of a device check for the alignment in the blkpg_ioctl. We'd also need to reject this when reading partitions from disk, right? > + /* check if partition is aligned to blocksize */ > +

Re: [PATCH] arch: x86: kernel: fixed unused label issue

On Wed, Dec 14, 2016 at 11:15:13AM +, Piotr Gregor wrote: > The patch_default label is only used from within > case PARAVIRT_PATCH(pv_lock_ops.queued_spin_unlock) > and > case PARAVIRT_PATCH(pv_lock_ops.vcpu_is_preempted) > i.e. when #if defined(CONFIG_PARAVIRT_SPINLOCKS) is true.

Re: [PATCH] arch: x86: kernel: fixed unused label issue

On Wed, Dec 14, 2016 at 11:15:13AM +, Piotr Gregor wrote: > The patch_default label is only used from within > case PARAVIRT_PATCH(pv_lock_ops.queued_spin_unlock) > and > case PARAVIRT_PATCH(pv_lock_ops.vcpu_is_preempted) > i.e. when #if defined(CONFIG_PARAVIRT_SPINLOCKS) is true.

Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report

On Wednesday 14 December 2016 09:22 PM, Eric W. Biederman wrote: Peter Zijlstra writes: On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote: I would just make the identifier a structure containing the device number and the inode number. It didn't look

Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report

On Wednesday 14 December 2016 09:22 PM, Eric W. Biederman wrote: Peter Zijlstra writes: On Wed, Dec 14, 2016 at 08:56:43AM +1300, Eric W. Biederman wrote: I would just make the identifier a structure containing the device number and the inode number. It didn't look like perf required the

Re: [PATCH v2 3/3] power: supply: bq24735-charger: allow chargers to share the ac-detect gpio

[of course I forgot to actually add gpio people, let's try again] On Wed, Dec 14, 2016 at 05:59:21PM +0100, Sebastian Reichel wrote: > Hi, > > On Wed, Dec 14, 2016 at 12:56:45AM +0100, Peter Rosin wrote: > > If several parallel bq24735 chargers have their ac-detect gpios wired > > together (or

Re: [PATCH v2 3/3] power: supply: bq24735-charger: allow chargers to share the ac-detect gpio

[of course I forgot to actually add gpio people, let's try again] On Wed, Dec 14, 2016 at 05:59:21PM +0100, Sebastian Reichel wrote: > Hi, > > On Wed, Dec 14, 2016 at 12:56:45AM +0100, Peter Rosin wrote: > > If several parallel bq24735 chargers have their ac-detect gpios wired > > together (or

Re: [PATCH v2 3/3] power: supply: bq24735-charger: allow chargers to share the ac-detect gpio

Hi, On Wed, Dec 14, 2016 at 12:56:45AM +0100, Peter Rosin wrote: > If several parallel bq24735 chargers have their ac-detect gpios wired > together (or if only one of the parallel bq24735 chargers have its > ac-detect pin wired to a gpio, and the others are assumed to react the > same), then all

Re: [PATCH v2 3/3] power: supply: bq24735-charger: allow chargers to share the ac-detect gpio

Hi, On Wed, Dec 14, 2016 at 12:56:45AM +0100, Peter Rosin wrote: > If several parallel bq24735 chargers have their ac-detect gpios wired > together (or if only one of the parallel bq24735 chargers have its > ac-detect pin wired to a gpio, and the others are assumed to react the > same), then all

Re: [PATCH] keys/encrypted: Fix two crypto-on-the-stack bugs

On Tue, Dec 13, 2016 at 08:40:00AM -0800, Andy Lutomirski wrote: > But I think this is rather silly. Joerg, Linus, etc: would it be okay > to change lib/dma-debug.c to allow DMA *from* rodata? Yeah, this would be fine for DMA_TO_DEVICE mappings. At least I can't think of a reason right now to

Re: [PATCH] keys/encrypted: Fix two crypto-on-the-stack bugs

On Tue, Dec 13, 2016 at 08:40:00AM -0800, Andy Lutomirski wrote: > But I think this is rather silly. Joerg, Linus, etc: would it be okay > to change lib/dma-debug.c to allow DMA *from* rodata? Yeah, this would be fine for DMA_TO_DEVICE mappings. At least I can't think of a reason right now to

Re: [PATCH v2 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id

On 14/12/2016 17:15, David Hildenbrand wrote: > >> kvm_for_each_vcpu(i, vcpu, kvm) >> if (kvm_apic_present(vcpu)) >> -max_id = max(max_id, kvm_apic_id(vcpu->arch.apic)); >> +max_id = max(max_id, kvm_x2apic_id(vcpu->arch.apic)); >> >> new =

Re: [PATCH v2 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id

On 14/12/2016 17:15, David Hildenbrand wrote: > >> kvm_for_each_vcpu(i, vcpu, kvm) >> if (kvm_apic_present(vcpu)) >> -max_id = max(max_id, kvm_apic_id(vcpu->arch.apic)); >> +max_id = max(max_id, kvm_x2apic_id(vcpu->arch.apic)); >> >> new =

Re: [PATCH v13 1/3] drm: Move locking into drm_debugfs_crtc_crc_add

On 14 December 2016 at 13:34, Tomeu Vizoso wrote: > There's no reason any more for callers of this function to take the lock > themselves, so just move the lock to the function to avoid confusion and > bugs when more callers are contributed. > > Signed-off-by: Tomeu

Re: [PATCH v13 1/3] drm: Move locking into drm_debugfs_crtc_crc_add

On 14 December 2016 at 13:34, Tomeu Vizoso wrote: > There's no reason any more for callers of this function to take the lock > themselves, so just move the lock to the function to avoid confusion and > bugs when more callers are contributed. > > Signed-off-by: Tomeu Vizoso Reviewed-by: Emil

Re: [PATCH 1/2] devicetree: power: add bindings for GPIO-driven power switches

2016-12-13 20:27 GMT+01:00 Rob Herring : > On Sun, Dec 11, 2016 at 11:21:44PM +0100, Bartosz Golaszewski wrote: >> Some boards are equipped with simple, GPIO-driven power load switches. >> An example of such ICs is the TI tps229* series. > > How is this different than a GPIO

Re: [PATCH 1/2] devicetree: power: add bindings for GPIO-driven power switches

2016-12-13 20:27 GMT+01:00 Rob Herring : > On Sun, Dec 11, 2016 at 11:21:44PM +0100, Bartosz Golaszewski wrote: >> Some boards are equipped with simple, GPIO-driven power load switches. >> An example of such ICs is the TI tps229* series. > > How is this different than a GPIO regulator? The input

[RFC] perf/x86/intel: Account interrupts for PEBS errors

hi, I'm hitting soft lockup generated by fuzzer, where the perf hangs in remote_install path like: NMI watchdog: BUG: soft lockup - CPU#22 stuck for 22s! [perf_fuzzer:5816] task: 880273148000 task.stack: c90002d58000 RIP: 0010:[] [] smp_call_function_single+0xe2/0x140 RSP:

[RFC] perf/x86/intel: Account interrupts for PEBS errors

hi, I'm hitting soft lockup generated by fuzzer, where the perf hangs in remote_install path like: NMI watchdog: BUG: soft lockup - CPU#22 stuck for 22s! [perf_fuzzer:5816] task: 880273148000 task.stack: c90002d58000 RIP: 0010:[] [] smp_call_function_single+0xe2/0x140 RSP:

Re: [PATCH] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Wed, Dec 14, 2016 at 03:47:57PM +0100, Pali Rohár wrote: > Signed-off-by: Pali Rohár > --- > drivers/usb/musb/musb_debugfs.c | 44 > +-- > 1 file changed, 28 insertions(+), 16 deletions(-) I don't accept patches without any

Re: [PATCH] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Wed, Dec 14, 2016 at 03:47:57PM +0100, Pali Rohár wrote: > Signed-off-by: Pali Rohár > --- > drivers/usb/musb/musb_debugfs.c | 44 > +-- > 1 file changed, 28 insertions(+), 16 deletions(-) I don't accept patches without any changelog information, nor

RE: [PATCH 2/2] FPGA: Add TS-7300 FPGA manager

On Monday, December 12, 2016 9:02 AM, Alan Tull wrote: > On Sun, 11 Dec 2016, Florian Fainelli wrote: >> Add support for loading bitstreams on the Altera Cyclone II FPGA >> populated on the TS-7300 board. This is done through the configuration >> and data registers offered through a memory

RE: [PATCH 2/2] FPGA: Add TS-7300 FPGA manager

On Monday, December 12, 2016 9:02 AM, Alan Tull wrote: > On Sun, 11 Dec 2016, Florian Fainelli wrote: >> Add support for loading bitstreams on the Altera Cyclone II FPGA >> populated on the TS-7300 board. This is done through the configuration >> and data registers offered through a memory

Re: [PATCH linux v1 0/4] Seven segment display support

On Wed, Dec 14, 2016 at 02:12:41PM +0100, Neil Armstrong wrote: > On 12/14/2016 01:56 PM, Greg KH wrote: > > On Wed, Dec 14, 2016 at 01:45:30PM +0100, Thomas Petazzoni wrote: > >> Hello, > >> > >> On Tue, 13 Dec 2016 23:55:00 -0800, Jaghathiswari Rankappagounder > >> Natarajan wrote: > >> > >>>

Re: [PATCH linux v1 0/4] Seven segment display support

On Wed, Dec 14, 2016 at 02:12:41PM +0100, Neil Armstrong wrote: > On 12/14/2016 01:56 PM, Greg KH wrote: > > On Wed, Dec 14, 2016 at 01:45:30PM +0100, Thomas Petazzoni wrote: > >> Hello, > >> > >> On Tue, 13 Dec 2016 23:55:00 -0800, Jaghathiswari Rankappagounder > >> Natarajan wrote: > >> > >>>

Re: [PATCH] HID: add Asus macrokey support for Asus "Republic of Gamers" laptop

On Wed, Dec 14, 2016 at 6:20 PM, Jiri Kosina wrote: > On Mon, 12 Dec 2016, Chris Chiu wrote: > > [ ... snip ... ] >> +static const struct hid_device_id asus_rog_devices[] = { >> + { HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK, >> USB_DEVICE_ID_ASUSTEK_ROG_MACROKEY1) }, >> + {

Re: [PATCH] HID: add Asus macrokey support for Asus "Republic of Gamers" laptop

On Wed, Dec 14, 2016 at 6:20 PM, Jiri Kosina wrote: > On Mon, 12 Dec 2016, Chris Chiu wrote: > > [ ... snip ... ] >> +static const struct hid_device_id asus_rog_devices[] = { >> + { HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK, >> USB_DEVICE_ID_ASUSTEK_ROG_MACROKEY1) }, >> + {

Re: [PATCH] MIPS: NI 169445 board support

On Wed, Dec 14, 2016 at 10:32 AM, Nathan Sullivan wrote: > On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote: >> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote: >> > Support the National Instruments 169445 board. >> > >> > Signed-off-by: Nathan

Re: [PATCH] MIPS: NI 169445 board support

On Wed, Dec 14, 2016 at 10:32 AM, Nathan Sullivan wrote: > On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote: >> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote: >> > Support the National Instruments 169445 board. >> > >> > Signed-off-by: Nathan Sullivan >> > --- >> >

Re: Fw: [lkp-developer] [sched,rcu] cf7a2dca60: [No primary change] +186% will-it-scale.time.involuntary_context_switches

On Wed, Dec 14, 2016 at 05:15:41PM +0100, Michal Hocko wrote: > On Wed 14-12-16 03:06:09, Paul E. McKenney wrote: > > On Wed, Dec 14, 2016 at 10:54:25AM +0100, Michal Hocko wrote: > > > On Tue 13-12-16 07:14:08, Paul E. McKenney wrote: > > > > Just FYI for the moment... > > > > > > > > So even

Re: Fw: [lkp-developer] [sched,rcu] cf7a2dca60: [No primary change] +186% will-it-scale.time.involuntary_context_switches

On Wed, Dec 14, 2016 at 05:15:41PM +0100, Michal Hocko wrote: > On Wed 14-12-16 03:06:09, Paul E. McKenney wrote: > > On Wed, Dec 14, 2016 at 10:54:25AM +0100, Michal Hocko wrote: > > > On Tue 13-12-16 07:14:08, Paul E. McKenney wrote: > > > > Just FYI for the moment... > > > > > > > > So even

RE: [PATCH] drivers: staging: comedi: fix function prototypes

On December 14, 2016 6:42 AM, Piotr Gregor wrote: > Add names of parameters to function prototypes in comedi PCI. > Checkpatch reports now no errors. > > Signed-off-by: Piotr Gregor > --- > drivers/staging/comedi/comedi_pci.h | 18 ++ > 1 file changed, 10

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Tue, Dec 13, 2016 at 12:12 AM, Andrew Jeffery wrote: > On Mon, 2016-12-12 at 10:27 -0600, Rob Herring wrote: >> On Tue, Dec 06, 2016 at 02:11:49PM +1100, Andrew Jeffery wrote: >> > The System Control Unit IP block in the Aspeed SoCs is typically where >> > the pinmux

RE: [PATCH] drivers: staging: comedi: fix function prototypes

On December 14, 2016 6:42 AM, Piotr Gregor wrote: > Add names of parameters to function prototypes in comedi PCI. > Checkpatch reports now no errors. > > Signed-off-by: Piotr Gregor > --- > drivers/staging/comedi/comedi_pci.h | 18 ++ > 1 file changed, 10 insertions(+), 8

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Tue, Dec 13, 2016 at 12:12 AM, Andrew Jeffery wrote: > On Mon, 2016-12-12 at 10:27 -0600, Rob Herring wrote: >> On Tue, Dec 06, 2016 at 02:11:49PM +1100, Andrew Jeffery wrote: >> > The System Control Unit IP block in the Aspeed SoCs is typically where >> > the pinmux configuration is found,

[RFC] block: check partition alignment

Partitions that are not aligned to the blocksize of a device may cause invalid I/O requests because the blocklayer cares only about alignment within the partition when building requests on partitions. device |4096|4096|4096| partition offset 512byte

[RFC] block: check partition alignment

Partitions that are not aligned to the blocksize of a device may cause invalid I/O requests because the blocklayer cares only about alignment within the partition when building requests on partitions. device |4096|4096|4096| partition offset 512byte

Re: [PATCH 0/2] Add maintainers to the admin guide

Em Wed, 14 Dec 2016 08:14:44 -0800 Joe Perches escreveu: > On Tue, 2016-12-13 at 07:38 -0200, Mauro Carvalho Chehab wrote: > > Em Mon, 12 Dec 2016 12:56:50 -0800 > > Joe Perches escreveu: > > > Does the boxing with the === blocks align properly? > > >

Re: [PATCH 0/2] Add maintainers to the admin guide

Em Wed, 14 Dec 2016 08:14:44 -0800 Joe Perches escreveu: > On Tue, 2016-12-13 at 07:38 -0200, Mauro Carvalho Chehab wrote: > > Em Mon, 12 Dec 2016 12:56:50 -0800 > > Joe Perches escreveu: > > > Does the boxing with the === blocks align properly? > > > It it really useful? Is there

Re: [PATCH v2 1/3] power: supply: bq24735-charger: simplify register update to stop charging

Hi, On Wed, Dec 14, 2016 at 12:56:43AM +0100, Peter Rosin wrote: > Providing value bits outside of the mask is pointless. > > Signed-off-by: Peter Rosin > --- > drivers/power/supply/bq24735-charger.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git

Re: [RFC 07/10] kmod: use simplified rate limit printk

On Wed, 2016-12-14 at 17:23 +0100, Petr Mladek wrote: > On Thu 2016-12-08 11:49:01, Luis R. Rodriguez wrote: > > Just use the simplified rate limit printk when the max modprobe > > limit is reached, while at it throw out a bone should the error > > be triggered. [] > > diff --git a/kernel/kmod.c

Re: [PATCH v2 1/3] power: supply: bq24735-charger: simplify register update to stop charging

Hi, On Wed, Dec 14, 2016 at 12:56:43AM +0100, Peter Rosin wrote: > Providing value bits outside of the mask is pointless. > > Signed-off-by: Peter Rosin > --- > drivers/power/supply/bq24735-charger.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git

Re: [RFC 07/10] kmod: use simplified rate limit printk

On Wed, 2016-12-14 at 17:23 +0100, Petr Mladek wrote: > On Thu 2016-12-08 11:49:01, Luis R. Rodriguez wrote: > > Just use the simplified rate limit printk when the max modprobe > > limit is reached, while at it throw out a bone should the error > > be triggered. [] > > diff --git a/kernel/kmod.c

Re: usb/gadget: warning in ep_write_iter/__alloc_pages_nodemask

On Wed, 14 Dec 2016, Michal Hocko wrote: > On Tue 13-12-16 08:33:34, Alan Stern wrote: > > On Tue, 13 Dec 2016, Michal Hocko wrote: > > > > > > > That being said, what ep_write_iter does sounds quite stupit. It just > > > > > allocates a large continuous buffer which seems to be under user > > >

Re: usb/gadget: warning in ep_write_iter/__alloc_pages_nodemask

On Wed, 14 Dec 2016, Michal Hocko wrote: > On Tue 13-12-16 08:33:34, Alan Stern wrote: > > On Tue, 13 Dec 2016, Michal Hocko wrote: > > > > > > > That being said, what ep_write_iter does sounds quite stupit. It just > > > > > allocates a large continuous buffer which seems to be under user > > >

RE: [PATCH v3 1/2] ARM: ep93xx: Register ts73xx-fpga manager driver for TS-7300

On Tuesday, December 13, 2016 7:36 PM, Florian Fainelli wrote: > > Register the TS-7300 FPGA manager device drivers which allows us to load > bitstreams into the on-board Altera Cyclone II FPGA. > > Signed-off-by: Florian Fainelli > --- > arch/arm/mach-ep93xx/ts72xx.c | 26

RE: [PATCH v3 1/2] ARM: ep93xx: Register ts73xx-fpga manager driver for TS-7300

On Tuesday, December 13, 2016 7:36 PM, Florian Fainelli wrote: > > Register the TS-7300 FPGA manager device drivers which allows us to load > bitstreams into the on-board Altera Cyclone II FPGA. > > Signed-off-by: Florian Fainelli > --- > arch/arm/mach-ep93xx/ts72xx.c | 26

Re: [PATCH 4/3] random: use siphash24 instead of md5 for get_random_int/long

On Wed, Dec 14, 2016 at 04:10:37AM +0100, Jason A. Donenfeld wrote: > This duplicates the current algorithm for get_random_int/long, but uses > siphash24 instead. This comes with several benefits. It's certainly > faster and more cryptographically secure than MD5. This patch also > hashes the pid,

Re: [PATCH 4/3] random: use siphash24 instead of md5 for get_random_int/long

On Wed, Dec 14, 2016 at 04:10:37AM +0100, Jason A. Donenfeld wrote: > This duplicates the current algorithm for get_random_int/long, but uses > siphash24 instead. This comes with several benefits. It's certainly > faster and more cryptographically secure than MD5. This patch also > hashes the pid,

Re: [PATCH 1/1] arm64: Correcting format specifier for printing 64 bit addresses

On 06/12/2016 17:11, Christoffer Dall wrote: > + kvm_err("Unsupported guest CP%d access at: %08lx\n", > + cp, *vcpu_pc(vcpu)); > + else > + kvm_err("Unsupported guest CP%d access at: %016lx\n", > + cp, *vcpu_pc(vcpu)); > > It

Re: [PATCH 1/1] arm64: Correcting format specifier for printing 64 bit addresses

On 06/12/2016 17:11, Christoffer Dall wrote: > + kvm_err("Unsupported guest CP%d access at: %08lx\n", > + cp, *vcpu_pc(vcpu)); > + else > + kvm_err("Unsupported guest CP%d access at: %016lx\n", > + cp, *vcpu_pc(vcpu)); > > It

Re: [PATCH] MIPS: NI 169445 board support

On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote: > On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote: > > Support the National Instruments 169445 board. > > > > Signed-off-by: Nathan Sullivan > > --- > > "gpio: mmio: add support for NI 169445

Re: [PATCH] MIPS: NI 169445 board support

On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote: > On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote: > > Support the National Instruments 169445 board. > > > > Signed-off-by: Nathan Sullivan > > --- > > "gpio: mmio: add support for NI 169445 NAND GPIO" and > >

Re: [v1] net:ethernet:cavium:octeon:octeon_mgmt: Handle return NULL error from devm_ioremap

Sorry for build failure. I have send new changes. Which does not this failure. Thanks -Arvind On Wednesday 14 December 2016 08:10 PM, kbuild test robot wrote: Hi Arvind, [auto build test ERROR on net-next/master] [also build test ERROR on v4.9 next-20161214] [if your patch is applied

Re: [v1] net:ethernet:cavium:octeon:octeon_mgmt: Handle return NULL error from devm_ioremap

Sorry for build failure. I have send new changes. Which does not this failure. Thanks -Arvind On Wednesday 14 December 2016 08:10 PM, kbuild test robot wrote: Hi Arvind, [auto build test ERROR on net-next/master] [also build test ERROR on v4.9 next-20161214] [if your patch is applied

Re: linux-next: Tree for Dec 14

On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any material for v4.11 to your linux-next included > branches until after v4.10-rc1 has been released. > > Changes since 20161213: > > The vfs-miklos tree gained a conflict against

Re: linux-next: Tree for Dec 14

On Tue, Dec 13, 2016 at 11:22 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any material for v4.11 to your linux-next included > branches until after v4.10-rc1 has been released. > > Changes since 20161213: > > The vfs-miklos tree gained a conflict against the ubifs tree. > > The

[v2] net:ethernet:cavium:octeon:octeon_mgmt: Handle return NULL error from devm_ioremap

Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. This error check will avoid NULL pointer dereference. Signed-off-by: Arvind Yadav --- drivers/net/ethernet/cavium/octeon/octeon_mgmt.c | 6 ++ 1 file changed, 6

Re: [PATCH] qedr: return -EINVAL if pd is null and avoid null ptr dereference

On 10/18/2016 2:39 PM, Colin King wrote: > From: Colin Ian King > > Currently, if pd is null then we hit a null pointer derference > on accessing pd->pd_id. Instead of just printing an error message > we should also return -EINVAL immediately. > > Signed-off-by: Colin

[v2] net:ethernet:cavium:octeon:octeon_mgmt: Handle return NULL error from devm_ioremap

Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. This error check will avoid NULL pointer dereference. Signed-off-by: Arvind Yadav --- drivers/net/ethernet/cavium/octeon/octeon_mgmt.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [PATCH] qedr: return -EINVAL if pd is null and avoid null ptr dereference

On 10/18/2016 2:39 PM, Colin King wrote: > From: Colin Ian King > > Currently, if pd is null then we hit a null pointer derference > on accessing pd->pd_id. Instead of just printing an error message > we should also return -EINVAL immediately. > > Signed-off-by: Colin Ian King Applied,

Re: [PATCH v2] keys/encrypted: Fix two crypto-on-the-stack bugs

On Wed, Dec 14, 2016 at 12:37 AM, David Howells wrote: > Andy Lutomirski wrote: > >> > - sg_set_buf(_out[1], pad, sizeof pad); >> > + sg_set_buf(_out[1], empty_zero_page, 16); >> >> My fix here is obviously bogus (I meant to use

Re: [PATCH v2] keys/encrypted: Fix two crypto-on-the-stack bugs

On Wed, Dec 14, 2016 at 12:37 AM, David Howells wrote: > Andy Lutomirski wrote: > >> > - sg_set_buf(_out[1], pad, sizeof pad); >> > + sg_set_buf(_out[1], empty_zero_page, 16); >> >> My fix here is obviously bogus (I meant to use ZERO_PAGE(0)), but what >> exactly is the code trying

Re: [PATCH v2 04/11] Documentation: DT: binding: axp20x_usb_power: add axp223 compatible

On Fri, Dec 9, 2016 at 7:04 PM, Quentin Schulz wrote: > This adds the "x-powers,axp223-usb-power-supply" to the list of > compatibles for AXP20X VBUS power supply driver. > > Signed-off-by: Quentin Schulz > --- > > v2: > -

Re: [PATCH v2 04/11] Documentation: DT: binding: axp20x_usb_power: add axp223 compatible

On Fri, Dec 9, 2016 at 7:04 PM, Quentin Schulz wrote: > This adds the "x-powers,axp223-usb-power-supply" to the list of > compatibles for AXP20X VBUS power supply driver. > > Signed-off-by: Quentin Schulz > --- > > v2: > - adding small explanation on AXP223 variation compared to the AXP221, > >

Re: [RFC 07/10] kmod: use simplified rate limit printk

On Thu 2016-12-08 11:49:01, Luis R. Rodriguez wrote: > Just use the simplified rate limit printk when the max modprobe > limit is reached, while at it throw out a bone should the error > be triggered. > > Signed-off-by: Luis R. Rodriguez > --- > kernel/kmod.c | 10 ++

Re: [RFC 07/10] kmod: use simplified rate limit printk

On Thu 2016-12-08 11:49:01, Luis R. Rodriguez wrote: > Just use the simplified rate limit printk when the max modprobe > limit is reached, while at it throw out a bone should the error > be triggered. > > Signed-off-by: Luis R. Rodriguez > --- > kernel/kmod.c | 10 ++ > 1 file changed,

[PATCH V2 3/4] arch/powerpc: Implement Optprobes

Detour buffer contains instructions to create an in memory pt_regs. After the execution of the pre-handler, a call is made for instruction emulation. The NIP is determined in advanced through dummy instruction emulation and a branch instruction is created to the NIP at the end of the trampoline.

[PATCH V2 1/4] powerpc: asm/ppc-opcode.h: introduce __PPC_SH64()

From: "Naveen N. Rao" Introduce __PPC_SH64() as a 64-bit variant to encode shift field in some of the shift and rotate instructions operating on double-words. Convert some of the BPF instruction macros to use the same. Signed-off-by: Naveen N. Rao

[PATCH V2 2/4] powerpc: add helper to check if offset is within rel branch range

From: "Naveen N. Rao" Signed-off-by: Naveen N. Rao Signed-off-by: Anju T Sudhakar --- arch/powerpc/include/asm/code-patching.h | 1 + arch/powerpc/lib/code-patching.c | 24

[PATCH V2 2/4] powerpc: add helper to check if offset is within rel branch range

From: "Naveen N. Rao" Signed-off-by: Naveen N. Rao Signed-off-by: Anju T Sudhakar --- arch/powerpc/include/asm/code-patching.h | 1 + arch/powerpc/lib/code-patching.c | 24 +++- 2 files changed, 24 insertions(+), 1 deletion(-) diff --git

[PATCH V2 3/4] arch/powerpc: Implement Optprobes

Detour buffer contains instructions to create an in memory pt_regs. After the execution of the pre-handler, a call is made for instruction emulation. The NIP is determined in advanced through dummy instruction emulation and a branch instruction is created to the NIP at the end of the trampoline.

[PATCH V2 1/4] powerpc: asm/ppc-opcode.h: introduce __PPC_SH64()

From: "Naveen N. Rao" Introduce __PPC_SH64() as a 64-bit variant to encode shift field in some of the shift and rotate instructions operating on double-words. Convert some of the BPF instruction macros to use the same. Signed-off-by: Naveen N. Rao --- arch/powerpc/include/asm/ppc-opcode.h |

[PATCH V2 0/4] OPTPROBES for powerpc

This is the V2 patchset of the kprobes jump optimization (a.k.a OPTPROBES)for powerpc. Kprobe being an inevitable tool for kernel developers, enhancing the performance of kprobe has got much importance. Currently kprobes inserts a trap instruction to probe a running kernel. Jump optimization

[PATCH V2 4/4] arch/powerpc: Optimize kprobe in kretprobe_trampoline

Kprobe placed on the kretprobe_trampoline during boot time can be optimized, since the instruction at probe point is a 'nop'. Signed-off-by: Anju T Sudhakar --- arch/powerpc/kernel/kprobes.c | 8 arch/powerpc/kernel/optprobes.c | 7 +++ 2 files changed,

Re: usb/gadget: warning in ep_write_iter/__alloc_pages_nodemask

On Wed 14-12-16 11:13:11, Alan Stern wrote: > On Wed, 14 Dec 2016, Michal Hocko wrote: > > > On Tue 13-12-16 08:33:34, Alan Stern wrote: > > > On Tue, 13 Dec 2016, Michal Hocko wrote: [...] > > > > Well, my point was that it is not really hard to imagine to deplete > > > > larger contiguous

[PATCH V2 0/4] OPTPROBES for powerpc

This is the V2 patchset of the kprobes jump optimization (a.k.a OPTPROBES)for powerpc. Kprobe being an inevitable tool for kernel developers, enhancing the performance of kprobe has got much importance. Currently kprobes inserts a trap instruction to probe a running kernel. Jump optimization

[PATCH V2 4/4] arch/powerpc: Optimize kprobe in kretprobe_trampoline

Kprobe placed on the kretprobe_trampoline during boot time can be optimized, since the instruction at probe point is a 'nop'. Signed-off-by: Anju T Sudhakar --- arch/powerpc/kernel/kprobes.c | 8 arch/powerpc/kernel/optprobes.c | 7 +++ 2 files changed, 11 insertions(+), 4

Re: usb/gadget: warning in ep_write_iter/__alloc_pages_nodemask

On Wed 14-12-16 11:13:11, Alan Stern wrote: > On Wed, 14 Dec 2016, Michal Hocko wrote: > > > On Tue 13-12-16 08:33:34, Alan Stern wrote: > > > On Tue, 13 Dec 2016, Michal Hocko wrote: [...] > > > > Well, my point was that it is not really hard to imagine to deplete > > > > larger contiguous

[PATCH v3 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting cells. The protocol is quite simple and using GPIOs: One GPIO is used as clock (SCK) while another GPIO is read (DOUT) The raw value read from the chip is delivered. To get a weight one needs to subtract the zero

[PATCH v3 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting cells. The protocol is quite simple and using GPIOs: One GPIO is used as clock (SCK) while another GPIO is read (DOUT) The raw value read from the chip is delivered. To get a weight one needs to subtract the zero

Re: [PATCH v2 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id

kvm_for_each_vcpu(i, vcpu, kvm) if (kvm_apic_present(vcpu)) - max_id = max(max_id, kvm_apic_id(vcpu->arch.apic)); + max_id = max(max_id, kvm_x2apic_id(vcpu->arch.apic)); new = kvm_kvzalloc(sizeof(struct kvm_apic_map) +

Re: [PATCH v2 2/4] KVM: x86: replace kvm_apic_id with kvm_{x,x2}apic_id

kvm_for_each_vcpu(i, vcpu, kvm) if (kvm_apic_present(vcpu)) - max_id = max(max_id, kvm_apic_id(vcpu->arch.apic)); + max_id = max(max_id, kvm_x2apic_id(vcpu->arch.apic)); new = kvm_kvzalloc(sizeof(struct kvm_apic_map) +

Re: [RFC/PATCH] tracing: show total NMI time in hwlat tracer

[ added the forgotten LKML ;-) ] On Wed, 14 Dec 2016 09:53:01 -0500 Steven Rostedt wrote: > On Wed, 14 Dec 2016 16:13:51 +0900 > Namhyung Kim wrote: > > > Hi Steve, > > > > While looking at the code I found the below. I'm not sure the current > >

Re: [PATCH] spi: SPI_FSL_DSPI should depend on HAS_DMA

On Wed, Dec 14, 2016 at 03:40:43PM +0100, Geert Uytterhoeven wrote: > On Wed, Dec 14, 2016 at 3:37 PM, Mark Brown wrote: > > On Wed, Dec 14, 2016 at 01:28:05PM +0100, Geert Uytterhoeven wrote: > > Honestly I think we should just fix the architectures that don't support > >

Re: Fw: [lkp-developer] [sched,rcu] cf7a2dca60: [No primary change] +186% will-it-scale.time.involuntary_context_switches

On Wed 14-12-16 03:06:09, Paul E. McKenney wrote: > On Wed, Dec 14, 2016 at 10:54:25AM +0100, Michal Hocko wrote: > > On Tue 13-12-16 07:14:08, Paul E. McKenney wrote: > > > Just FYI for the moment... > > > > > > So even with the slowed-down checking, making cond_resched() do what > > >

[PATCH v3 1/2] iio: adc: hx711: Add DT binding for avia,hx711

Add DT bindings for avia,hx711 Add vendor avia to vendor list Signed-off-by: Andreas Klinger --- Documentation/devicetree/bindings/iio/adc/avia-hx711.txt | 16 Documentation/devicetree/bindings/vendor-prefixes.txt| 1 + 2 files changed, 17 insertions(+)

Re: [PATCH] spi: SPI_FSL_DSPI should depend on HAS_DMA

On Wed, Dec 14, 2016 at 03:40:43PM +0100, Geert Uytterhoeven wrote: > On Wed, Dec 14, 2016 at 3:37 PM, Mark Brown wrote: > > On Wed, Dec 14, 2016 at 01:28:05PM +0100, Geert Uytterhoeven wrote: > > Honestly I think we should just fix the architectures that don't support > > DMA to provide compile

Re: Fw: [lkp-developer] [sched,rcu] cf7a2dca60: [No primary change] +186% will-it-scale.time.involuntary_context_switches

On Wed 14-12-16 03:06:09, Paul E. McKenney wrote: > On Wed, Dec 14, 2016 at 10:54:25AM +0100, Michal Hocko wrote: > > On Tue 13-12-16 07:14:08, Paul E. McKenney wrote: > > > Just FYI for the moment... > > > > > > So even with the slowed-down checking, making cond_resched() do what > > >

[PATCH v3 1/2] iio: adc: hx711: Add DT binding for avia,hx711

Add DT bindings for avia,hx711 Add vendor avia to vendor list Signed-off-by: Andreas Klinger --- Documentation/devicetree/bindings/iio/adc/avia-hx711.txt | 16 Documentation/devicetree/bindings/vendor-prefixes.txt| 1 + 2 files changed, 17 insertions(+) create mode 100644

Re: [RFC/PATCH] tracing: show total NMI time in hwlat tracer

[ added the forgotten LKML ;-) ] On Wed, 14 Dec 2016 09:53:01 -0500 Steven Rostedt wrote: > On Wed, 14 Dec 2016 16:13:51 +0900 > Namhyung Kim wrote: > > > Hi Steve, > > > > While looking at the code I found the below. I'm not sure the current > > code is correct but it seems that

[PATCH v3 0/2] iio: adc: hx711: Add IIO driver for AVIA HX711 ADC

This series adds IIO driver support for the AVIA HX711 ADC which is mostly used in weighting cells. The first patch adds the new DT binding for which a new vendor avia was also added. The second patch is the simple IIO driver implemented as ADC. The protocol is specific to this device and

[PATCH v3 0/2] iio: adc: hx711: Add IIO driver for AVIA HX711 ADC

This series adds IIO driver support for the AVIA HX711 ADC which is mostly used in weighting cells. The first patch adds the new DT binding for which a new vendor avia was also added. The second patch is the simple IIO driver implemented as ADC. The protocol is specific to this device and

Re: [PATCH 0/2] Add maintainers to the admin guide

On Tue, 2016-12-13 at 07:38 -0200, Mauro Carvalho Chehab wrote: > Em Mon, 12 Dec 2016 12:56:50 -0800 > Joe Perches escreveu: > > Does the boxing with the === blocks align properly? > > It it really useful? Is there another/better way? > > Do you mean those? > >

Re: [PATCH 0/2] Add maintainers to the admin guide

On Tue, 2016-12-13 at 07:38 -0200, Mauro Carvalho Chehab wrote: > Em Mon, 12 Dec 2016 12:56:50 -0800 > Joe Perches escreveu: > > Does the boxing with the === blocks align properly? > > It it really useful? Is there another/better way? > > Do you mean those? > >

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

Hi, On Wednesday, December 14, 2016 11:40:08 AM Javier Martinez Canillas wrote: > Hello Bartlomiej, > > On 12/14/2016 11:25 AM, Bartlomiej Zolnierkiewicz wrote: > > > > Hi, > > > > On Wednesday, December 14, 2016 11:06:45 AM Javier Martinez Canillas wrote: > >> > >> Hello Bartlomiej, > >> >

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

Hi, On Wednesday, December 14, 2016 11:40:08 AM Javier Martinez Canillas wrote: > Hello Bartlomiej, > > On 12/14/2016 11:25 AM, Bartlomiej Zolnierkiewicz wrote: > > > > Hi, > > > > On Wednesday, December 14, 2016 11:06:45 AM Javier Martinez Canillas wrote: > >> > >> Hello Bartlomiej, > >> >

<    6   7   8   9   10   11   12   13   14   15   >