Re: bpf: kernel BUG in htab_elem_free

On 11/03/2016 03:15 PM, Dmitry Vyukov wrote: On Wed, Nov 2, 2016 at 11:14 PM, Dmitry Vyukov wrote: Here we go. The following program triggers kernel BUG in htab_elem_free. On commit 0c183d92b20b5c84ca655b45ef57b3318b83eb9e (Oct 31). Run as "while true; do ./a.out; done".

Re: bpf: kernel BUG in htab_elem_free

On 11/03/2016 03:15 PM, Dmitry Vyukov wrote: On Wed, Nov 2, 2016 at 11:14 PM, Dmitry Vyukov wrote: Here we go. The following program triggers kernel BUG in htab_elem_free. On commit 0c183d92b20b5c84ca655b45ef57b3318b83eb9e (Oct 31). Run as "while true; do ./a.out; done". This one fixes it

[PATCHv2 0/4] Generic #pinctrl-cells and and pinctrl_parse_index_with_args

Hi all, Here a repost of some pinctrl changes to introduce #pinctrl-cells and a generic parser pinctrl_parse_index_with_args that the drivers can optionally use. Regards, Tony Changes from v1: - Update based on comments from Linus Walleij to not pass #pinctrl-cells as an argument and

[PATCHv2 0/4] Generic #pinctrl-cells and and pinctrl_parse_index_with_args

Hi all, Here a repost of some pinctrl changes to introduce #pinctrl-cells and a generic parser pinctrl_parse_index_with_args that the drivers can optionally use. Regards, Tony Changes from v1: - Update based on comments from Linus Walleij to not pass #pinctrl-cells as an argument and

Re: [PATCH] ASoC: sun4i-i2s: Implement capture support

On Thu, Nov 03, 2016 at 09:32:18AM -0600, Mark Brown wrote: > On Thu, Nov 03, 2016 at 11:20:48AM +0100, Maxime Ripard wrote: > > The i2s driver was only implementing playback for now. Implement capture to > > make sure that's not a limitation anymore. > > This doesn't apply against current code,

Re: [PATCH] ASoC: sun4i-i2s: Implement capture support

On Thu, Nov 03, 2016 at 09:32:18AM -0600, Mark Brown wrote: > On Thu, Nov 03, 2016 at 11:20:48AM +0100, Maxime Ripard wrote: > > The i2s driver was only implementing playback for now. Implement capture to > > make sure that's not a limitation anymore. > > This doesn't apply against current code,

[PATCH v2] ASoC: sun4i-i2s: Implement capture support

The i2s driver was only implementing playback for now. Implement capture to make sure that's not a limitation anymore. Signed-off-by: Maxime Ripard --- Changes from v1: - Rebased on top of asoc's topic/sunxi branch sound/soc/sunxi/sun4i-i2s.c | 52

[PATCH v2] ASoC: sun4i-i2s: Implement capture support

The i2s driver was only implementing playback for now. Implement capture to make sure that's not a limitation anymore. Signed-off-by: Maxime Ripard --- Changes from v1: - Rebased on top of asoc's topic/sunxi branch sound/soc/sunxi/sun4i-i2s.c | 52

[PATCH 2/4] pinctrl: single: Use generic parser and #pinctrl-cells for pinctrl-single,pins

We can now use generic parser. To support the legacy binding without #pinctrl-cells, add pcs_quirk_missing_pinctrl_cells() and warn about missing #pinctrl-cells. Let's also update the documentation for struct pcs_soc_data while at it as that seems to be out of date. Signed-off-by: Tony Lindgren

[PATCH 2/4] pinctrl: single: Use generic parser and #pinctrl-cells for pinctrl-single,pins

We can now use generic parser. To support the legacy binding without #pinctrl-cells, add pcs_quirk_missing_pinctrl_cells() and warn about missing #pinctrl-cells. Let's also update the documentation for struct pcs_soc_data while at it as that seems to be out of date. Signed-off-by: Tony Lindgren

[PATCH 4/4] ARM: dts: Add #pinctrl-cells for pinctrl-single instances

Drivers using pinctrl-single,pins have #pinctrl-cells = <1>, while pinctrl-single,bits need #pinctrl-cells = <2>. Note that this patch can be optionally applied separately from the driver changes as the driver supports also the legacy binding without #pinctrl-cells. Acked-by: Rob Herring

[PATCH 4/4] ARM: dts: Add #pinctrl-cells for pinctrl-single instances

Drivers using pinctrl-single,pins have #pinctrl-cells = <1>, while pinctrl-single,bits need #pinctrl-cells = <2>. Note that this patch can be optionally applied separately from the driver changes as the driver supports also the legacy binding without #pinctrl-cells. Acked-by: Rob Herring

Re: [PATCH v3 3/5] dt/bindings: Add a new property to DA8xx USB PHY

Hi, On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote: > The USB PHY is able to operate in OTG, host or peripheral. > Some board may be wired to work act only as host or peripheral. > In such case, the dr_mode property of controller must be set to > host or peripheral. But doing that

Re: [PATCH v3 3/5] dt/bindings: Add a new property to DA8xx USB PHY

Hi, On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote: > The USB PHY is able to operate in OTG, host or peripheral. > Some board may be wired to work act only as host or peripheral. > In such case, the dr_mode property of controller must be set to > host or peripheral. But doing that

Re: [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default

On 2016-11-03 09:22:28 [-0700], Paul E. McKenney wrote: > On Wed, Nov 02, 2016 at 05:30:02PM +0100, Sebastian Andrzej Siewior wrote: > > RCU_EXPEDITE_BOOT should speed up the boot process by enforcing > > synchronize_rcu_expedited() instead of synchronize_rcu() during the boot > > process. There

Re: [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default

On 2016-11-03 09:22:28 [-0700], Paul E. McKenney wrote: > On Wed, Nov 02, 2016 at 05:30:02PM +0100, Sebastian Andrzej Siewior wrote: > > RCU_EXPEDITE_BOOT should speed up the boot process by enforcing > > synchronize_rcu_expedited() instead of synchronize_rcu() during the boot > > process. There

[PATCH] Fix: disable sys_membarrier when nohz_full is enabled

Userspace applications should be allowed to expect the membarrier system call with MEMBARRIER_CMD_SHARED command to issue memory barriers on nohz_full CPUs, but synchronize_sched() does not take those into account. Given that we do not want unrelated processes to be able to affect real-time

[PATCH] Fix: disable sys_membarrier when nohz_full is enabled

Userspace applications should be allowed to expect the membarrier system call with MEMBARRIER_CMD_SHARED command to issue memory barriers on nohz_full CPUs, but synchronize_sched() does not take those into account. Given that we do not want unrelated processes to be able to affect real-time

[PATCH 1/2] f2fs: fix wrong i_atime recovery

From: Chao Yu Shouldn't update in-memory i_atime with on-disk i_mtime of inode when recovering inode. Shuoran found this bug which is hidden for a long time, honour is belong to him. Signed-off-by: Shuoran Liu Signed-off-by: Chao Yu

[PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

From: Chao Yu i_times of inode will be set with current system time which can be configured through 'date', so it's not safe to judge dnode block as garbage data depend on i_times. Now, we have used enhanced 'cp_ver + cp' crc method to verify valid dnode block, so I expect

[PATCH 1/2] f2fs: fix wrong i_atime recovery

From: Chao Yu Shouldn't update in-memory i_atime with on-disk i_mtime of inode when recovering inode. Shuoran found this bug which is hidden for a long time, honour is belong to him. Signed-off-by: Shuoran Liu Signed-off-by: Chao Yu --- fs/f2fs/recovery.c | 4 ++-- 1 file changed, 2

[PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

From: Chao Yu i_times of inode will be set with current system time which can be configured through 'date', so it's not safe to judge dnode block as garbage data depend on i_times. Now, we have used enhanced 'cp_ver + cp' crc method to verify valid dnode block, so I expect recoverying invalid

Re: [PATCH 2/2] Input: gpio_keys - Set ABS params when using axes

On Tue, Nov 01, 2016 at 11:25:04AM +0100, Paul Cercueil wrote: > The gpio-keys supports the EV_ABS event type, but does not actually > configure the input device to work with that mode. > > This patch configures the axis corresponding to button->code as being > in the range [-1,+1]. This makes it

Re: [PATCH 2/2] Input: gpio_keys - Set ABS params when using axes

On Tue, Nov 01, 2016 at 11:25:04AM +0100, Paul Cercueil wrote: > The gpio-keys supports the EV_ABS event type, but does not actually > configure the input device to work with that mode. > > This patch configures the axis corresponding to button->code as being > in the range [-1,+1]. This makes it

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On 11/3/2016 9:00 AM, Andreas Gruenbacher wrote: > On Thu, Nov 3, 2016 at 4:51 PM, Casey Schaufler > wrote: >> On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: >>> Casey, the first patch broke filesystems that support setxattr for some >>> xattrs >>> but not security

Re: [PATCH 16/25] ia64/salinfo: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allnoconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On 11/3/2016 9:00 AM, Andreas Gruenbacher wrote: > On Thu, Nov 3, 2016 at 4:51 PM, Casey Schaufler > wrote: >> On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: >>> Casey, the first patch broke filesystems that support setxattr for some >>> xattrs >>> but not security xattrs. Here's an updated

Re: [PATCH 16/25] ia64/salinfo: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allnoconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, Nov 03, 2016 at 12:11:55PM -0400, Lyude Paul wrote: > On Thu, 2016-11-03 at 12:11 -0400, Lyude Paul wrote: > > On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > > > > > > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > > > > > > > > > Weine's investigation on

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, Nov 03, 2016 at 12:11:55PM -0400, Lyude Paul wrote: > On Thu, 2016-11-03 at 12:11 -0400, Lyude Paul wrote: > > On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > > > > > > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > > > > > > > > > Weine's investigation on

Re: [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default

On Wed, Nov 02, 2016 at 05:30:02PM +0100, Sebastian Andrzej Siewior wrote: > RCU_EXPEDITE_BOOT should speed up the boot process by enforcing > synchronize_rcu_expedited() instead of synchronize_rcu() during the boot > process. There should be no reason why one does not want this and there > is no

Re: [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default

On Wed, Nov 02, 2016 at 05:30:02PM +0100, Sebastian Andrzej Siewior wrote: > RCU_EXPEDITE_BOOT should speed up the boot process by enforcing > synchronize_rcu_expedited() instead of synchronize_rcu() during the boot > process. There should be no reason why one does not want this and there > is no

Re: [PATCH 1/2] Input: gpio_keys - Also send release events for ABS codes

On Tue, Nov 01, 2016 at 11:25:03AM +0100, Paul Cercueil wrote: > Right now, the gpio-keys driver is mostly used with EV_KEY event types. > However, this driver (and its devicetree bindings) support specifying > a different input type, like EV_ABS, even though this doesn't work in > practice: "key

Re: [PATCH 1/2] Input: gpio_keys - Also send release events for ABS codes

On Tue, Nov 01, 2016 at 11:25:03AM +0100, Paul Cercueil wrote: > Right now, the gpio-keys driver is mostly used with EV_KEY event types. > However, this driver (and its devicetree bindings) support specifying > a different input type, like EV_ABS, even though this doesn't work in > practice: "key

stmmac: GMAC_RGSMIIIS reports bogus values

Hello, I'm seeing pretty strange issue with GMAC reporting a lot of link state changes based on bits in GMAC_RGSMIIIS. It looks like that: -->8--- Link is Down Link is Up - 10/Full Link is Down Link is Up - 10/Half Link is Down Link is Down Link is Up -

stmmac: GMAC_RGSMIIIS reports bogus values

Hello, I'm seeing pretty strange issue with GMAC reporting a lot of link state changes based on bits in GMAC_RGSMIIIS. It looks like that: -->8--- Link is Down Link is Up - 10/Full Link is Down Link is Up - 10/Half Link is Down Link is Down Link is Up -

Re: [kernel-hardening] [PATCH v2] module: extend 'rodata=off' boot cmdline parameter to module mappings

[Adding Jessica] On Fri, Oct 21, 2016 at 10:13:33AM +0900, AKASHI Takahiro wrote: > The current "rodata=off" parameter disables read-only kernel mappings > under CONFIG_DEBUG_RODATA: > commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter > to disable read-only kernel

Re: [kernel-hardening] [PATCH v2] module: extend 'rodata=off' boot cmdline parameter to module mappings

[Adding Jessica] On Fri, Oct 21, 2016 at 10:13:33AM +0900, AKASHI Takahiro wrote: > The current "rodata=off" parameter disables read-only kernel mappings > under CONFIG_DEBUG_RODATA: > commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter > to disable read-only kernel

[GIT PULL] KVM fixes for Linux 4.9-rc4

Linus, The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus for you to fetch changes up to

[GIT PULL] KVM fixes for Linux 4.9-rc4

Linus, The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus for you to fetch changes up to

[PATCH 1/1] mm: cma: check the max limit for cma allocation

CMA allocation request size is represented by size_t that gets truncated when same is passed as int to bitmap_find_next_zero_area_off. We observe that during fuzz testing when cma allocation request is too high, bitmap_find_next_zero_area_off still returns success due to the truncation. This

[PATCH 1/1] mm: cma: check the max limit for cma allocation

CMA allocation request size is represented by size_t that gets truncated when same is passed as int to bitmap_find_next_zero_area_off. We observe that during fuzz testing when cma allocation request is too high, bitmap_find_next_zero_area_off still returns success due to the truncation. This

Re: [PATCH 2/2] procfs/tasks: add a simple per-task procfs hidepid= field

On Thu, Nov 3, 2016 at 9:30 AM, Lafcadio Wluiki wrote: > (Third, rebased submission, since first two submissions yielded no replies.) > > This adds a new per-task hidepid= flag that is honored by procfs when > presenting /proc to the user, in addition to the existing hidepid=

Re: [PATCH 2/2] procfs/tasks: add a simple per-task procfs hidepid= field

On Thu, Nov 3, 2016 at 9:30 AM, Lafcadio Wluiki wrote: > (Third, rebased submission, since first two submissions yielded no replies.) > > This adds a new per-task hidepid= flag that is honored by procfs when > presenting /proc to the user, in addition to the existing hidepid= mount > option. So

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, 2016-11-03 at 12:11 -0400, Lyude Paul wrote: > On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > > > > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > > > > > > Weine's investigation on benchmarking the suspend/resume process pointed > > > out a lot of the time in

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, 2016-11-03 at 12:11 -0400, Lyude Paul wrote: > On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > > > > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > > > > > > Weine's investigation on benchmarking the suspend/resume process pointed > > > out a lot of the time in

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > Weine's investigation on benchmarking the suspend/resume process pointed > > out a lot of the time in suspend/resume is being spent reprobing. While > > the reprobing process is

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, 2016-11-03 at 16:02 +, Chris Wilson wrote: > On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > > > > Weine's investigation on benchmarking the suspend/resume process pointed > > out a lot of the time in suspend/resume is being spent reprobing. While > > the reprobing process is

[PATCH v2] tools/power/acpi: Remove direct kernel source include reference

ACPICA tools trickily uses integer types, and trickily includes kernel include directory directly, which breaks tools build for some cross compilers. This patch improves ACPICA tools build to make it a bit more robust in such situation by splitting include/acpi into a separate output directory.

[PATCH v2] tools/power/acpi: Remove direct kernel source include reference

ACPICA tools trickily uses integer types, and trickily includes kernel include directory directly, which breaks tools build for some cross compilers. This patch improves ACPICA tools build to make it a bit more robust in such situation by splitting include/acpi into a separate output directory.

Re: [Ksummit-discuss] Results: Linux Foundation Technical Advisory Board Election 2016

Hi Steven, On Thursday 03 Nov 2016 11:39:51 Steven Rostedt wrote: > The TAB elections are now complete. Thank you to all the candidates for > putting their names forward, and a big thank you to Grant Likely, Shuah > Khan, Jes Sorensen, H. Peter Anvin, Chris Mason and the Linux Foundation > staff

Re: [Ksummit-discuss] Results: Linux Foundation Technical Advisory Board Election 2016

Hi Steven, On Thursday 03 Nov 2016 11:39:51 Steven Rostedt wrote: > The TAB elections are now complete. Thank you to all the candidates for > putting their names forward, and a big thank you to Grant Likely, Shuah > Khan, Jes Sorensen, H. Peter Anvin, Chris Mason and the Linux Foundation > staff

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > Weine's investigation on benchmarking the suspend/resume process pointed > out a lot of the time in suspend/resume is being spent reprobing. While > the reprobing process is a lengthy one for good reason, we don't need to > hold up the

[PATCH v2 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

The davinci ohci driver name (currently "ohci") is too generic. To be consistent with other usb dirvers, append the "-da8xx" postfix to the name. Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 1/3] ARM: davinci: da8xx: Fix ohci device name

While the clk lookup table is making reference to "ohci" other subsystems (such as phy) are trying to match "ohci.0" Since there is a single ohci instance, instead of changing the clk name, change the dev id to -1, and add the "-da8xx" postfix to match the driver name that will also be changed in

[PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

The ohci device name has changed in the board configuraion files, hence, change the phy lookup table to match the new name. Signed-off-by: Axel Haslam --- drivers/phy/phy-da8xx-usb.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume

On Thu, Nov 03, 2016 at 11:42:37AM -0400, Lyude wrote: > Weine's investigation on benchmarking the suspend/resume process pointed > out a lot of the time in suspend/resume is being spent reprobing. While > the reprobing process is a lengthy one for good reason, we don't need to > hold up the

[PATCH v2 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

The davinci ohci driver name (currently "ohci") is too generic. To be consistent with other usb dirvers, append the "-da8xx" postfix to the name. Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 1/3] ARM: davinci: da8xx: Fix ohci device name

While the clk lookup table is making reference to "ohci" other subsystems (such as phy) are trying to match "ohci.0" Since there is a single ohci instance, instead of changing the clk name, change the dev id to -1, and add the "-da8xx" postfix to match the driver name that will also be changed in

[PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

The ohci device name has changed in the board configuraion files, hence, change the phy lookup table to match the new name. Signed-off-by: Axel Haslam --- drivers/phy/phy-da8xx-usb.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/phy/phy-da8xx-usb.c

[PATCH v2 0/3] davinci: ohci: fix usb ohci device name

The usb ohci clock match is not working because the usb clock is registered as "ohci" instead of "ohci.0" But since there is only a single ohci instance, lets pass -1 to the platform data id parameter and avoid the extra ".0" matching. while we are fixing this, rename the driver from "ohci" to

[PATCH v2 0/3] davinci: ohci: fix usb ohci device name

The usb ohci clock match is not working because the usb clock is registered as "ohci" instead of "ohci.0" But since there is only a single ohci instance, lets pass -1 to the platform data id parameter and avoid the extra ".0" matching. while we are fixing this, rename the driver from "ohci" to

[PATCH v8 3/4] x86/cpufeature: Add PHIR3MWAIT to CPU features

Add Intel Xeon Phi x200 (KnightsLanding) CPU feature - ring 3 MONITOR/MWAIT. Signed-off-by: Grzegorz Andrejczuk --- arch/x86/include/asm/cpufeatures.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/include/asm/cpufeatures.h

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On Thu, Nov 3, 2016 at 4:51 PM, Casey Schaufler wrote: > On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: >> Casey, the first patch broke filesystems that support setxattr for some >> xattrs >> but not security xattrs. Here's an updated patch; could you please test? > >

[PATCH v8 3/4] x86/cpufeature: Add PHIR3MWAIT to CPU features

Add Intel Xeon Phi x200 (KnightsLanding) CPU feature - ring 3 MONITOR/MWAIT. Signed-off-by: Grzegorz Andrejczuk --- arch/x86/include/asm/cpufeatures.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On Thu, Nov 3, 2016 at 4:51 PM, Casey Schaufler wrote: > On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: >> Casey, the first patch broke filesystems that support setxattr for some >> xattrs >> but not security xattrs. Here's an updated patch; could you please test? > > This patch does not fix

Re: [PATCH 2/5] KVM: x86: do not scan IRR twice on APICv vmentry

On 03/11/2016 14:53, Michael S. Tsirkin wrote: > > Nope, this breaks nested VMX exit on external interrupt. For now I'm > > testing only patch 1 and will push that one only to kvm/next. > > Do you know why? I don't see it yet. Nope, have not debugged it yet. Paolo

Re: [PATCH 2/5] KVM: x86: do not scan IRR twice on APICv vmentry

On 03/11/2016 14:53, Michael S. Tsirkin wrote: > > Nope, this breaks nested VMX exit on external interrupt. For now I'm > > testing only patch 1 and will push that one only to kvm/next. > > Do you know why? I don't see it yet. Nope, have not debugged it yet. Paolo

[PATCH v4 0/4] Add DT support for DA8xx

Changes in v2: * Remove unrelated changes in patch 3 * Rename the device node in patch 4 Changes in v3: * Fix few mistakes in DT binding sample * Only build the device table if DT is enabled Change in v4: * Fix a nit Alexandre Bailon (1): ARM: dts: da850: Add the usb otg device node Petr

[PATCH v4 0/4] Add DT support for DA8xx

Changes in v2: * Remove unrelated changes in patch 3 * Rename the device node in patch 4 Changes in v3: * Fix few mistakes in DT binding sample * Only build the device table if DT is enabled Change in v4: * Fix a nit Alexandre Bailon (1): ARM: dts: da850: Add the usb otg device node Petr

Re: [PATCH 2/5] KVM: x86: do not scan IRR twice on APICv vmentry

On 03/11/2016 16:03, Radim Krčmář wrote: > 2016-11-03 14:30+0100, Paolo Bonzini: >> On 26/10/2016 21:59, Radim Krčmář wrote: >>> 2016-10-14 20:21+0200, Paolo Bonzini: Calling apic_find_highest_irr results in IRR being scanned twice, once in vmx_sync_pir_from_irr and once in

[PATCH v4 3/4] usb: musb: da8xx: Add DT support for the DA8xx driver

From: Petr Kulhavy This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon Tested-by: David Lechner --- drivers/usb/musb/da8xx.c | 46

Re: [PATCH 2/5] KVM: x86: do not scan IRR twice on APICv vmentry

On 03/11/2016 16:03, Radim Krčmář wrote: > 2016-11-03 14:30+0100, Paolo Bonzini: >> On 26/10/2016 21:59, Radim Krčmář wrote: >>> 2016-10-14 20:21+0200, Paolo Bonzini: Calling apic_find_highest_irr results in IRR being scanned twice, once in vmx_sync_pir_from_irr and once in

[PATCH v4 3/4] usb: musb: da8xx: Add DT support for the DA8xx driver

From: Petr Kulhavy This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon Tested-by: David Lechner --- drivers/usb/musb/da8xx.c | 46 ++ 1 file changed, 46 insertions(+)

[PATCH v4 2/4] usb: musb: core: added helper function for parsing DT

From: Petr Kulhavy This adds the function musb_get_mode() to get the DT property "dr_mode" Signed-off-by: Petr Kulhavy Acked-by: Sergei Shtylyov Signed-off-by: Alexandre Bailon Tested-by: David Lechner

[PATCH v4 2/4] usb: musb: core: added helper function for parsing DT

From: Petr Kulhavy This adds the function musb_get_mode() to get the DT property "dr_mode" Signed-off-by: Petr Kulhavy Acked-by: Sergei Shtylyov Signed-off-by: Alexandre Bailon Tested-by: David Lechner Reviewed-by: Kevin Hilman --- drivers/usb/musb/musb_core.c | 19 +++

[PATCH v4 1/4] dt/bindings: Add binding for the DA8xx MUSB driver

From: Petr Kulhavy DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon Acked-by: Rob Herring --- .../devicetree/bindings/usb/da8xx-usb.txt

[PATCH v4 1/4] dt/bindings: Add binding for the DA8xx MUSB driver

From: Petr Kulhavy DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver. Signed-off-by: Petr Kulhavy Signed-off-by: Alexandre Bailon Acked-by: Rob Herring --- .../devicetree/bindings/usb/da8xx-usb.txt | 43 ++ 1 file changed, 43 insertions(+) create

[PATCH v4 4/4] ARM: dts: da850: Add the usb otg device node

This adds the device tree node for the usb otg controller present in the da850 family of SoC's. This also enables the otg usb controller for the lcdk board. Signed-off-by: Alexandre Bailon --- arch/arm/boot/dts/da850-lcdk.dts | 8 arch/arm/boot/dts/da850.dtsi

[PATCH v4 4/4] ARM: dts: da850: Add the usb otg device node

This adds the device tree node for the usb otg controller present in the da850 family of SoC's. This also enables the otg usb controller for the lcdk board. Signed-off-by: Alexandre Bailon --- arch/arm/boot/dts/da850-lcdk.dts | 8 arch/arm/boot/dts/da850.dtsi | 15 +++

Re: [PATCHv2 6/6] arm64: Add support for CONFIG_DEBUG_VIRTUAL

On Wed, Nov 02, 2016 at 06:05:38PM -0600, Laura Abbott wrote: > On 11/02/2016 05:06 PM, Mark Rutland wrote: > >On Wed, Nov 02, 2016 at 03:00:54PM -0600, Laura Abbott wrote: > >>+CFLAGS_physaddr.o := -DTEXT_OFFSET=$(TEXT_OFFSET) > >>+obj-$(CONFIG_DEBUG_VIRTUAL)+= physaddr.o > >>+

Re: [PATCHv2 6/6] arm64: Add support for CONFIG_DEBUG_VIRTUAL

On Wed, Nov 02, 2016 at 06:05:38PM -0600, Laura Abbott wrote: > On 11/02/2016 05:06 PM, Mark Rutland wrote: > >On Wed, Nov 02, 2016 at 03:00:54PM -0600, Laura Abbott wrote: > >>+CFLAGS_physaddr.o := -DTEXT_OFFSET=$(TEXT_OFFSET) > >>+obj-$(CONFIG_DEBUG_VIRTUAL)+= physaddr.o > >>+

Re: scripts/basic/fixdep: Complete error handling in print_cmdline()

Dne 2.11.2016 v 19:30 Masahiro Yamada napsal(a): > 2016-11-03 2:38 GMT+09:00 SF Markus Elfring : > + if (printf("cmd_%s := %s\n\n", target, cmdline) < 10) { Rather than scatter fragile magic numbers, like 10, throughout the code, if you're

Re: scripts/basic/fixdep: Complete error handling in print_cmdline()

Dne 2.11.2016 v 19:30 Masahiro Yamada napsal(a): > 2016-11-03 2:38 GMT+09:00 SF Markus Elfring : > + if (printf("cmd_%s := %s\n\n", target, cmdline) < 10) { Rather than scatter fragile magic numbers, like 10, throughout the code, if you're hell-bent on checking for printf

Re: [PATCH 2/6] pinctrl: rockchip: add support for rk1108

Am Donnerstag, 3. November 2016, 20:34:30 schrieb Andy Yan: > Add basic support for rk1108 soc > > Signed-off-by: Andy Yan nice when support for a new soc is that easy in a driver :-) There are two small issues below and with those fixed Reviewed-by: Heiko Stuebner

Re: [PATCH 2/6] pinctrl: rockchip: add support for rk1108

Am Donnerstag, 3. November 2016, 20:34:30 schrieb Andy Yan: > Add basic support for rk1108 soc > > Signed-off-by: Andy Yan nice when support for a new soc is that easy in a driver :-) There are two small issues below and with those fixed Reviewed-by: Heiko Stuebner > --- > >

Re: [PATCH 17/25] ia64/topology: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x

Re: [PATCH 17/25] ia64/topology: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x

Re: [RFC PATCH 2/3] rtc: Add Amlogic Virtual Wake RTC

On 11/03/2016 04:36 PM, Mark Rutland wrote: > On Thu, Nov 03, 2016 at 03:29:24PM +0100, Neil Armstrong wrote: >> The Amlogic Meson GX SoCs uses a special register to store the >> time in seconds to wakeup after a system suspend. > > Where does this register live, exactly? What IP block is it part

Re: [RFC PATCH 2/3] rtc: Add Amlogic Virtual Wake RTC

On 11/03/2016 04:36 PM, Mark Rutland wrote: > On Thu, Nov 03, 2016 at 03:29:24PM +0100, Neil Armstrong wrote: >> The Amlogic Meson GX SoCs uses a special register to store the >> time in seconds to wakeup after a system suspend. > > Where does this register live, exactly? What IP block is it part

Re: [Intel-wired-lan] [PATCH] e1000e: free IRQ when the link is up or down

On 11/3/2016 2:09 AM, Ruinskiy, Dima wrote: -Original Message- From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On Behalf Of Tyler Baicar Sent: Wednesday, 02 November, 2016 23:08 To: Kirsher, Jeffrey T; intel-wired-...@lists.osuosl.org; net...@vger.kernel.org;

Re: [Intel-wired-lan] [PATCH] e1000e: free IRQ when the link is up or down

On 11/3/2016 2:09 AM, Ruinskiy, Dima wrote: -Original Message- From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On Behalf Of Tyler Baicar Sent: Wednesday, 02 November, 2016 23:08 To: Kirsher, Jeffrey T; intel-wired-...@lists.osuosl.org; net...@vger.kernel.org;

Re: [PATCHv2 5/6] arm64: Use __pa_symbol for _end

On Wed, Nov 02, 2016 at 05:56:42PM -0600, Laura Abbott wrote: > On 11/02/2016 04:52 PM, Mark Rutland wrote: > >On Wed, Nov 02, 2016 at 03:00:53PM -0600, Laura Abbott wrote: > >> > >>__pa_symbol is technically the marco that should be used for kernel > >>symbols. Switch to this as a pre-requisite

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: > Casey, the first patch broke filesystems that support setxattr for some xattrs > but not security xattrs. Here's an updated patch; could you please test? This patch does not fix the problem. I am back to EOPTNOTSUP. > > Al, does this look

Re: [PATCHv2 5/6] arm64: Use __pa_symbol for _end

On Wed, Nov 02, 2016 at 05:56:42PM -0600, Laura Abbott wrote: > On 11/02/2016 04:52 PM, Mark Rutland wrote: > >On Wed, Nov 02, 2016 at 03:00:53PM -0600, Laura Abbott wrote: > >> > >>__pa_symbol is technically the marco that should be used for kernel > >>symbols. Switch to this as a pre-requisite

Re: [PATCH] xattr: Fix setting security xattrs on sockfs

On 11/3/2016 6:45 AM, Andreas Gruenbacher wrote: > Casey, the first patch broke filesystems that support setxattr for some xattrs > but not security xattrs. Here's an updated patch; could you please test? This patch does not fix the problem. I am back to EOPTNOTSUP. > > Al, does this look

Re: [PATCH 16/25] ia64/salinfo: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin

Re: [PATCH 16/25] ia64/salinfo: Convert to hotplug state machine

-Siewior/fs-buffer-Convert-to-hotplug-state-machine/20161103-230222 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin

Re: [PATCH 3/3] ovl: redirect on rename-dir

On Fri, Oct 28, 2016 at 6:15 PM, Al Viro wrote: > On Tue, Oct 25, 2016 at 09:34:47AM +0200, Miklos Szeredi wrote: >> Current code returns EXDEV when a directory would need to be copied up to >> move. We could copy up the directory tree in this case, but there's >>

Re: [PATCH 3/3] ovl: redirect on rename-dir

On Fri, Oct 28, 2016 at 6:15 PM, Al Viro wrote: > On Tue, Oct 25, 2016 at 09:34:47AM +0200, Miklos Szeredi wrote: >> Current code returns EXDEV when a directory would need to be copied up to >> move. We could copy up the directory tree in this case, but there's >> another solution: point to old

<    3   4   5   6   7   8   9   10   11   12   >