[PATCH v3] nvmet: fix nvmet_execute_write_zeroes function

When trying to issue write_zeroes command against TARGET with a 4K block size, it ends up hitting the following condition at __blkdev_issue_zeroout: if ((sector | nr_sects) & bs_mask) return -EINVAL; Causing the command to always fail. Considering we need to add 1 to get the

[PATCH v3] nvmet: fix nvmet_execute_write_zeroes function

When trying to issue write_zeroes command against TARGET with a 4K block size, it ends up hitting the following condition at __blkdev_issue_zeroout: if ((sector | nr_sects) & bs_mask) return -EINVAL; Causing the command to always fail. Considering we need to add 1 to get the

Re: [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function

I'm terribly sorry, but the +1 actually needs to be outside the le16_to_cpu. The above will work on little-endian machines, but not big. No problem at all. Thank you for helping on this. I'm going to send a V3 with this change. -- Rodrigo R. Galvão Intern - Linux Technology Center - IBM

Re: [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function

I'm terribly sorry, but the +1 actually needs to be outside the le16_to_cpu. The above will work on little-endian machines, but not big. No problem at all. Thank you for helping on this. I'm going to send a V3 with this change. -- Rodrigo R. Galvão Intern - Linux Technology Center - IBM

[GIT] Networking

1) Fix RCU locking in xfrm_local_error(), from Taehee Yoo. 2) Fix return value assignments and thus error checking in iwl_mvm_start_ap_ibss(), from Johannes Berg. 3) Don't count header length twice in vti4, from Stefano Brivio. 4) Fix deadlock in rt6_age_examine_exception, from Eric

[GIT] Networking

1) Fix RCU locking in xfrm_local_error(), from Taehee Yoo. 2) Fix return value assignments and thus error checking in iwl_mvm_start_ap_ibss(), from Johannes Berg. 3) Don't count header length twice in vti4, from Stefano Brivio. 4) Fix deadlock in rt6_age_examine_exception, from Eric

Re: [net-next 0/2] Add promiscous mode support in k2g network driver

From: Murali Karicheri Date: Mon, 2 Apr 2018 12:17:17 -0400 > This patch adds support for promiscuous mode in network driver for K2G > SoC. This depends on v3 of my series at > https://www.spinics.net/lists/kernel/msg2765942.html The net-next tree is closed, please resubmit

Re: [net-next 0/2] Add promiscous mode support in k2g network driver

From: Murali Karicheri Date: Mon, 2 Apr 2018 12:17:17 -0400 > This patch adds support for promiscuous mode in network driver for K2G > SoC. This depends on v3 of my series at > https://www.spinics.net/lists/kernel/msg2765942.html The net-next tree is closed, please resubmit this series after

[GIT PULL] pstore updates for v4.17-rc1

Hi Linus, Please pull these pstore changes for v4.17-rc1. This cycle was almost entirely improvements to the pstore compression options, noted below. Thanks! -Kees The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51: Linux 4.16-rc2 (2018-02-18 17:29:42 -0800) are

[GIT PULL] pstore updates for v4.17-rc1

Hi Linus, Please pull these pstore changes for v4.17-rc1. This cycle was almost entirely improvements to the pstore compression options, noted below. Thanks! -Kees The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51: Linux 4.16-rc2 (2018-02-18 17:29:42 -0800) are

[GIT PULL] regmap updates for v4.17

The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae: Linux 4.16-rc5 (2018-03-11 17:25:09 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.17 for you to fetch changes up to

[GIT PULL] regmap updates for v4.17

The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae: Linux 4.16-rc5 (2018-03-11 17:25:09 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.17 for you to fetch changes up to

Re: [PATCH 12/15] dmaengine: pxa: make the filter function internal

://github.com/0day-ci/linux/commits/Robert-Jarzmik/ARM-pxa-switch-to-DMA-slave-maps/20180402-233029 config: i386-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones

Re: [PATCH 12/15] dmaengine: pxa: make the filter function internal

://github.com/0day-ci/linux/commits/Robert-Jarzmik/ARM-pxa-switch-to-DMA-slave-maps/20180402-233029 config: i386-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones

Re: Question regarding container affecting the host system mounts

On Mon, Apr 2, 2018 at 10:56 AM, Richard Weinberger wrote: > Ronak Desai, > > On Mon, Apr 2, 2018 at 5:40 PM, Ronak Desai > wrote: >> I am able to workaround this issue by marking the mount as unbinadable >> and clearing the flag

Re: Question regarding container affecting the host system mounts

On Mon, Apr 2, 2018 at 10:56 AM, Richard Weinberger wrote: > Ronak Desai, > > On Mon, Apr 2, 2018 at 5:40 PM, Ronak Desai > wrote: >> I am able to workaround this issue by marking the mount as unbinadable >> and clearing the flag (CL_COPY_UNBINDABLE) in "copy_tree" function in >> fs/namespace.c.

RE: [PATCH v5 05/14] PCI: Add pcie_print_link_status() to log link speed and whether it's limited

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Friday, March 30, 2018 2:05 PM > To: Tal Gilboa > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar

RE: [PATCH v5 05/14] PCI: Add pcie_print_link_status() to log link speed and whether it's limited

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Friday, March 30, 2018 2:05 PM > To: Tal Gilboa > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar ; Kirsher, Jeffrey T > ; everest-linux...@cavium.com; intel-wired- > l...@lists.osuosl.org;

Re: 4.16-rc2+git: pata_serverworks: hanging ata detection thread on HP DL380G3

Hello, On Fri, Mar 30, 2018 at 11:47:24AM +0300, Meelis Roos wrote: > Added CC-s, start of the thread is at > https://lkml.org/lkml/2018/2/26/165 > > > > > 4.16 git bootup on HP Proliant DL380 G3 pauses for a a minute or two > > > > and > > > > then continues with "blocked for more than 120

Re: 4.16-rc2+git: pata_serverworks: hanging ata detection thread on HP DL380G3

Hello, On Fri, Mar 30, 2018 at 11:47:24AM +0300, Meelis Roos wrote: > Added CC-s, start of the thread is at > https://lkml.org/lkml/2018/2/26/165 > > > > > 4.16 git bootup on HP Proliant DL380 G3 pauses for a a minute or two > > > > and > > > > then continues with "blocked for more than 120

[PATCH] tpm: moves the delay_msec increment after sleep in tpm_transmit()

Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to handle the TPM2_RC_RETRY error. The loop retries the command after sleeping for the specified time, which is incremented exponentially in every iteration. This patch fixes the initial sleep to be the default sleep time. Fixes:

[PATCH] tpm: moves the delay_msec increment after sleep in tpm_transmit()

Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to handle the TPM2_RC_RETRY error. The loop retries the command after sleeping for the specified time, which is incremented exponentially in every iteration. This patch fixes the initial sleep to be the default sleep time. Fixes:

Re: [PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

On 30 March 2018 at 16:54, Mike Kravetz wrote: > This is a fix for a regression in 32 bit kernels caused by an > invalid check for pgoff overflow in hugetlbfs mmap setup. The > check incorrectly specified that the size of a loff_t was the > same as the size of a long.

Re: [PATCH v2] hugetlbfs: fix bug in pgoff overflow checking

On 30 March 2018 at 16:54, Mike Kravetz wrote: > This is a fix for a regression in 32 bit kernels caused by an > invalid check for pgoff overflow in hugetlbfs mmap setup. The > check incorrectly specified that the size of a loff_t was the > same as the size of a long. The regression prevents

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 02, 2018 at 06:04:35PM +0200, Dmitry Vyukov wrote: > On Mon, Apr 2, 2018 at 5:33 PM, Paul E. McKenney > wrote: > > On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: > >> On Mon, 02 Apr 2018 02:20:02 -0700 > >> syzbot

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 02, 2018 at 06:04:35PM +0200, Dmitry Vyukov wrote: > On Mon, Apr 2, 2018 at 5:33 PM, Paul E. McKenney > wrote: > > On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: > >> On Mon, 02 Apr 2018 02:20:02 -0700 > >> syzbot wrote: > >> > >> > Hello, > >> > > >> > syzbot hit

Re: [PATCH] Fixed some style warnings and errors

On Mon, Apr 02, 2018 at 09:17:43PM +0600, Khan M Rashedun-Naby wrote: > @@ -820,14 +821,22 @@ static void init_amd(struct cpuinfo_x86 *c) > clear_cpu_cap(c, X86_FEATURE_MCE); > > switch (c->x86) { > - case 4:init_amd_k5(c); break; > - case 5:init_amd_k6(c);

Re: [PATCH] Fixed some style warnings and errors

On Mon, Apr 02, 2018 at 09:17:43PM +0600, Khan M Rashedun-Naby wrote: > @@ -820,14 +821,22 @@ static void init_amd(struct cpuinfo_x86 *c) > clear_cpu_cap(c, X86_FEATURE_MCE); > > switch (c->x86) { > - case 4:init_amd_k5(c); break; > - case 5:init_amd_k6(c);

[net-next 2/2] net: netcp: ethss: k2g: add promiscuous mode support

From: WingMan Kwok This patch adds support for promiscuous mode in k2g's network driver. When upper layer instructs to transition from non-promiscuous mode to promiscuous mode or vice versa K2G network driver needs to configure ALE accordingly so that in case of non-promiscuous

[net-next 2/2] net: netcp: ethss: k2g: add promiscuous mode support

From: WingMan Kwok This patch adds support for promiscuous mode in k2g's network driver. When upper layer instructs to transition from non-promiscuous mode to promiscuous mode or vice versa K2G network driver needs to configure ALE accordingly so that in case of non-promiscuous mode, ALE will

[net-next 0/2] Add promiscous mode support in k2g network driver

This patch adds support for promiscuous mode in network driver for K2G SoC. This depends on v3 of my series at https://www.spinics.net/lists/kernel/msg2765942.html I plan to fold this to the above series and submit again when the net-next merge windows opens. At this time, please review and let

[net-next 0/2] Add promiscous mode support in k2g network driver

This patch adds support for promiscuous mode in network driver for K2G SoC. This depends on v3 of my series at https://www.spinics.net/lists/kernel/msg2765942.html I plan to fold this to the above series and submit again when the net-next merge windows opens. At this time, please review and let

Re: [PATCH v8 42/42] ARM: dts: da850: Add clocks

On 04/02/2018 06:12 AM, Sekhar Nori wrote: On Friday 16 March 2018 10:50 PM, David Lechner wrote: On 03/15/2018 09:52 PM, David Lechner wrote: This adds clock provider nodes for da850 and wires them up to all of the devices. Signed-off-by: David Lechner --- ... This

Re: [PATCH v8 42/42] ARM: dts: da850: Add clocks

On 04/02/2018 06:12 AM, Sekhar Nori wrote: On Friday 16 March 2018 10:50 PM, David Lechner wrote: On 03/15/2018 09:52 PM, David Lechner wrote: This adds clock provider nodes for da850 and wires them up to all of the devices. Signed-off-by: David Lechner --- ... This is the mcasp0:

Re: [PATCH 002/109] kernel: use kernel_wait4() instead of sys_wait4()

On Thu, Mar 29, 2018 at 01:22:39PM +0200, Dominik Brodowski wrote: > All call sites of sys_wait4() set *rusage to NULL. Therefore, there is > no need for the copy_to_user() handling of *rusage, and we can use > kernel_wait4() directly. > > This patch is part of a series which removes in-kernel

[net-next 1/2] net: netcp: add api to support set rx mode in netcp modules

From: WingMan Kwok This patch adds an API to support setting rx mode in netcp modules. If a netcp module needs to be notified when upper layer transitions from one rx mode to another and react accordingly, such a module will implement the new API set_rx_mode added in this patch.

Re: [PATCH 002/109] kernel: use kernel_wait4() instead of sys_wait4()

On Thu, Mar 29, 2018 at 01:22:39PM +0200, Dominik Brodowski wrote: > All call sites of sys_wait4() set *rusage to NULL. Therefore, there is > no need for the copy_to_user() handling of *rusage, and we can use > kernel_wait4() directly. > > This patch is part of a series which removes in-kernel

[net-next 1/2] net: netcp: add api to support set rx mode in netcp modules

From: WingMan Kwok This patch adds an API to support setting rx mode in netcp modules. If a netcp module needs to be notified when upper layer transitions from one rx mode to another and react accordingly, such a module will implement the new API set_rx_mode added in this patch. Currently rx

[PATCH 1/5] x86/hyper-v: move struct hv_flush_pcpu{,ex} definitions to common header

Hyper-V TLB flush hypercalls definitions will be required for KVM so move them hyperv-tlfs.h. Structures also need to be renamed as '_pcpu' suffix is invalid for a general-purpose definition. Signed-off-by: Vitaly Kuznetsov --- arch/x86/hyperv/mmu.c | 40

[PATCH 1/5] x86/hyper-v: move struct hv_flush_pcpu{,ex} definitions to common header

Hyper-V TLB flush hypercalls definitions will be required for KVM so move them hyperv-tlfs.h. Structures also need to be renamed as '_pcpu' suffix is invalid for a general-purpose definition. Signed-off-by: Vitaly Kuznetsov --- arch/x86/hyperv/mmu.c | 40

[PATCH 4/5] KVM: x86: hyperv: simplistic HVCALL_FLUSH_VIRTUAL_ADDRESS_{LIST,SPACE}_EX implementation

Implement HvFlushVirtualAddress{List,Space}Ex hypercalls in a simplistic way: do full TLB flush with KVM_REQ_TLB_FLUSH and rely on kvm_vcpu_kick() kicking only vCPUs which are currently IN_GUEST_MODE. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 94

[PATCH 4/5] KVM: x86: hyperv: simplistic HVCALL_FLUSH_VIRTUAL_ADDRESS_{LIST,SPACE}_EX implementation

Implement HvFlushVirtualAddress{List,Space}Ex hypercalls in a simplistic way: do full TLB flush with KVM_REQ_TLB_FLUSH and rely on kvm_vcpu_kick() kicking only vCPUs which are currently IN_GUEST_MODE. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 94

[PATCH 0/5] KVM: x86: hyperv: PV TLB flush for Windows guests

This is both a new feature and a bugfix. Bugfix description: It was found that Windows 2016 guests on KVM crash when they have > 64 vCPUs, non-flat topology (>1 core/thread per socket; in case it has >64 sockets Windows just ignores vCPUs above 64) and Hyper-V enlightenments (any) are enabled.

[PATCH 0/5] KVM: x86: hyperv: PV TLB flush for Windows guests

This is both a new feature and a bugfix. Bugfix description: It was found that Windows 2016 guests on KVM crash when they have > 64 vCPUs, non-flat topology (>1 core/thread per socket; in case it has >64 sockets Windows just ignores vCPUs above 64) and Hyper-V enlightenments (any) are enabled.

[PATCH 2/5] KVM: x86: hyperv: use defines when parsing hypercall parameters

Avoid open-coding offsets for hypercall input parameters, we already have defines for them. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c

[PATCH 2/5] KVM: x86: hyperv: use defines when parsing hypercall parameters

Avoid open-coding offsets for hypercall input parameters, we already have defines for them. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c index

[PATCH 5/5] KVM: x86: hyperv: declare KVM_CAP_HYPERV_TLBFLUSH capability

We need a new capability to indicate support for the newly added HvFlushVirtualAddress{List,Space}{,Ex} hypercalls. Upon seeing this capability, userspace is supposed to announce PV TLB flush features by setting the appropriate CPUID bits (if needed). Signed-off-by: Vitaly Kuznetsov

[PATCH 5/5] KVM: x86: hyperv: declare KVM_CAP_HYPERV_TLBFLUSH capability

We need a new capability to indicate support for the newly added HvFlushVirtualAddress{List,Space}{,Ex} hypercalls. Upon seeing this capability, userspace is supposed to announce PV TLB flush features by setting the appropriate CPUID bits (if needed). Signed-off-by: Vitaly Kuznetsov ---

[PATCH 3/5] KVM: x86: hyperv: simplistic HVCALL_FLUSH_VIRTUAL_ADDRESS_{LIST,SPACE} implementation

Implement HvFlushVirtualAddress{List,Space} hypercalls in a simplistic way: do full TLB flush with KVM_REQ_TLB_FLUSH and rely on kvm_vcpu_kick() kicking only vCPUs which are currently IN_GUEST_MODE. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 54

[PATCH 3/5] KVM: x86: hyperv: simplistic HVCALL_FLUSH_VIRTUAL_ADDRESS_{LIST,SPACE} implementation

Implement HvFlushVirtualAddress{List,Space} hypercalls in a simplistic way: do full TLB flush with KVM_REQ_TLB_FLUSH and rely on kvm_vcpu_kick() kicking only vCPUs which are currently IN_GUEST_MODE. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kvm/hyperv.c | 54

Re: [GIT PULL] misc core kernel changes

On Sun, Apr 1, 2018 at 11:14 PM, Ingo Molnar wrote: > > - add membarriers to Documentation/features/ You had actually done this earlier already, so now there are two commits adding it. Oh well. Linus

Re: [GIT PULL] misc core kernel changes

On Sun, Apr 1, 2018 at 11:14 PM, Ingo Molnar wrote: > > - add membarriers to Documentation/features/ You had actually done this earlier already, so now there are two commits adding it. Oh well. Linus

Re: [v3,4/4] watchdog: add Gateworks System Controller support

On Fri, Mar 30, 2018 at 11:19 AM, Guenter Roeck wrote: > On Fri, Mar 30, 2018 at 10:49:38AM -0700, Tim Harvey wrote: >> On Thu, Mar 29, 2018 at 6:07 PM, Guenter Roeck wrote: >> > On Wed, Mar 28, 2018 at 08:14:03AM -0700, Tim Harvey wrote: >> >>

Re: [v3,4/4] watchdog: add Gateworks System Controller support

On Fri, Mar 30, 2018 at 11:19 AM, Guenter Roeck wrote: > On Fri, Mar 30, 2018 at 10:49:38AM -0700, Tim Harvey wrote: >> On Thu, Mar 29, 2018 at 6:07 PM, Guenter Roeck wrote: >> > On Wed, Mar 28, 2018 at 08:14:03AM -0700, Tim Harvey wrote: >> >> Signed-off-by: Tim Harvey >> >> --- >> >>

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 2, 2018 at 5:33 PM, Paul E. McKenney wrote: > On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: >> On Mon, 02 Apr 2018 02:20:02 -0700 >> syzbot wrote: >> >> > Hello, >> > >> > syzbot hit

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 2, 2018 at 5:33 PM, Paul E. McKenney wrote: > On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: >> On Mon, 02 Apr 2018 02:20:02 -0700 >> syzbot wrote: >> >> > Hello, >> > >> > syzbot hit the following crash on upstream commit >> >

Re: [GIT PULL] Andes(nds32) Port for Linux 4.17

On Sun, Apr 1, 2018 at 11:01 PM, Greentime Hu wrote: > > This tag contains the core nds32 Linux port(including interrupt controller > driver and timer driver), which has been through 7 rounds of review on mailing > list. Can I get an overview of the nds32 architecture (uses,

Re: [GIT PULL] Andes(nds32) Port for Linux 4.17

On Sun, Apr 1, 2018 at 11:01 PM, Greentime Hu wrote: > > This tag contains the core nds32 Linux port(including interrupt controller > driver and timer driver), which has been through 7 rounds of review on mailing > list. Can I get an overview of the nds32 architecture (uses, quirks, reasons for

RE: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth

> -Original Message- > From: Tal Gilboa [mailto:ta...@mellanox.com] > Sent: Monday, April 02, 2018 7:34 AM > To: Bjorn Helgaas > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar

RE: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth

> -Original Message- > From: Tal Gilboa [mailto:ta...@mellanox.com] > Sent: Monday, April 02, 2018 7:34 AM > To: Bjorn Helgaas > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar ; Kirsher, Jeffrey T > ; everest-linux...@cavium.com; intel-wired- > l...@lists.osuosl.org;

Re: call/normal switch was Re: omap4-droid4: voice call support was

* Dan Williams [180402 15:51]: > On Sun, 2018-04-01 at 10:30 -0700, Tony Lindgren wrote: > > * Tony Lindgren [180401 15:38]: > > Found it! Here's what I need to do over n_gsm: > > > > ngsm 1 "AT+CFUN=1" > > ngsm 1 "AT+CFUN?" > > ngsm 2 "AT+EACC=3,0"#

Re: call/normal switch was Re: omap4-droid4: voice call support was

* Dan Williams [180402 15:51]: > On Sun, 2018-04-01 at 10:30 -0700, Tony Lindgren wrote: > > * Tony Lindgren [180401 15:38]: > > Found it! Here's what I need to do over n_gsm: > > > > ngsm 1 "AT+CFUN=1" > > ngsm 1 "AT+CFUN?" > > ngsm 2 "AT+EACC=3,0"# enable mic > > ngsm 2 "AT+CLVL=4" #

Re: Question regarding container affecting the host system mounts

Ronak Desai, On Mon, Apr 2, 2018 at 5:40 PM, Ronak Desai wrote: > I am able to workaround this issue by marking the mount as unbinadable > and clearing the flag (CL_COPY_UNBINDABLE) in "copy_tree" function in > fs/namespace.c. This skips the unbindable mounts to

Re: Question regarding container affecting the host system mounts

Ronak Desai, On Mon, Apr 2, 2018 at 5:40 PM, Ronak Desai wrote: > I am able to workaround this issue by marking the mount as unbinadable > and clearing the flag (CL_COPY_UNBINDABLE) in "copy_tree" function in > fs/namespace.c. This skips the unbindable mounts to get cloned inside > the new

RE: [PATCH v5 12/14] fm10k: Report PCIe link properties with pcie_print_link_status()

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Friday, March 30, 2018 2:06 PM > To: Tal Gilboa > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar

RE: [PATCH v5 12/14] fm10k: Report PCIe link properties with pcie_print_link_status()

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Friday, March 30, 2018 2:06 PM > To: Tal Gilboa > Cc: Tariq Toukan ; Keller, Jacob E > ; Ariel Elior ; Ganesh > Goudar ; Kirsher, Jeffrey T > ; everest-linux...@cavium.com; intel-wired- > l...@lists.osuosl.org;

Re: [PATCH] tracing: Uninitialized variable in create_tracing_map_fields()

On Wed, 28 Mar 2018 09:04:40 -0500 Tom Zanussi wrote: > Yes, this should definitely be initialized to 0, thanks for the patch! > > Acked-by: Tom Zanussi Thanks, I applied it and will push to git after it has succeeded in testing. --

Re: [PATCH] tracing: Uninitialized variable in create_tracing_map_fields()

On Wed, 28 Mar 2018 09:04:40 -0500 Tom Zanussi wrote: > Yes, this should definitely be initialized to 0, thanks for the patch! > > Acked-by: Tom Zanussi Thanks, I applied it and will push to git after it has succeeded in testing. -- Steve

Re: call/normal switch was Re: omap4-droid4: voice call support was

On Sun, 2018-04-01 at 10:30 -0700, Tony Lindgren wrote: > * Tony Lindgren [180401 15:38]: > > * Pavel Machek [180401 13:20]: > > > On Sat 2018-03-31 16:43:14, Tony Lindgren wrote: > > > > * Pavel Machek [180331 19:56]: > > > > > On Sat 2018-03-31

Re: call/normal switch was Re: omap4-droid4: voice call support was

On Sun, 2018-04-01 at 10:30 -0700, Tony Lindgren wrote: > * Tony Lindgren [180401 15:38]: > > * Pavel Machek [180401 13:20]: > > > On Sat 2018-03-31 16:43:14, Tony Lindgren wrote: > > > > * Pavel Machek [180331 19:56]: > > > > > On Sat 2018-03-31 21:46:16, Pavel Machek wrote: > > > > > > On Sat

[PATCH] PCI/AER: add pcie TLP header information in the tracepoint

When a PCIe AER occurs, the TLP header information is printed in the kernel message but it is missing from the tracepoint. A userspace program can use this information in the tracepoint to better analyze problems. Example tracepoint output: aer_event: :01:00.0 PCIe Bus Error:

[PATCH] PCI/AER: add pcie TLP header information in the tracepoint

When a PCIe AER occurs, the TLP header information is printed in the kernel message but it is missing from the tracepoint. A userspace program can use this information in the tracepoint to better analyze problems. Example tracepoint output: aer_event: :01:00.0 PCIe Bus Error:

Re: [PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

Hi Viresh, On 04/02/2018 01:32 AM, Viresh Kumar wrote: > On 26-03-18, 16:52, Suman Anna wrote: >> Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when >> failure") has fixed a memory leak in the failure path, however >> kmemleak still keeps reporting a leak even on successful probes. >>

Re: [PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

Hi Viresh, On 04/02/2018 01:32 AM, Viresh Kumar wrote: > On 26-03-18, 16:52, Suman Anna wrote: >> Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when >> failure") has fixed a memory leak in the failure path, however >> kmemleak still keeps reporting a leak even on successful probes. >>

Re: [PATCH 1/2] Move kfree_call_rcu() to slab_common.c

.com/0day-ci/linux/commits/rao-shoaib-oracle-com/Move-kfree_rcu-out-of-rcu-code-and-use-kfree_bulk/20180402-135939 > base: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > rcu/next > reproduce: > # apt-get install sparse > make A

Re: [PATCH 1/2] Move kfree_call_rcu() to slab_common.c

.com/0day-ci/linux/commits/rao-shoaib-oracle-com/Move-kfree_rcu-out-of-rcu-code-and-use-kfree_bulk/20180402-135939 > base: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > rcu/next > reproduce: > # apt-get install sparse > make A

Re: Question regarding container affecting the host system mounts

I am able to workaround this issue by marking the mount as unbinadable and clearing the flag (CL_COPY_UNBINDABLE) in "copy_tree" function in fs/namespace.c. This skips the unbindable mounts to get cloned inside the new namespace. For my use-case this is acceptable. On Thu, Mar 29, 2018 at 3:50

Re: Question regarding container affecting the host system mounts

I am able to workaround this issue by marking the mount as unbinadable and clearing the flag (CL_COPY_UNBINDABLE) in "copy_tree" function in fs/namespace.c. This skips the unbindable mounts to get cloned inside the new namespace. For my use-case this is acceptable. On Thu, Mar 29, 2018 at 3:50

Re: [PATCH v9 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support

On Mon, Apr 2, 2018 at 10:13 AM, Paolo Pisati wrote: Hi Paolo, Thanks for making the changes I asked for. Except... is there a reason to not get state in machxo2_spi_state? It turns out the API will change again. I can do the fixup when that happens. Alan > This patch

Re: [PATCH v9 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support

On Mon, Apr 2, 2018 at 10:13 AM, Paolo Pisati wrote: Hi Paolo, Thanks for making the changes I asked for. Except... is there a reason to not get state in machxo2_spi_state? It turns out the API will change again. I can do the fixup when that happens. Alan > This patch adds support to the

Re: [PATCH] locking/hung_task: Show all hung tasks before panic

On Mon, Apr 02, 2018 at 11:12:04PM +0900, Tetsuo Handa wrote: > When we get a hung task it can often be valuable to see _all_ the hung > tasks on the system before calling panic(). > > Quoting from > https://syzkaller.appspot.com/text?tag=CrashReport=5412451675799552 >

Re: [PATCH] locking/hung_task: Show all hung tasks before panic

On Mon, Apr 02, 2018 at 11:12:04PM +0900, Tetsuo Handa wrote: > When we get a hung task it can often be valuable to see _all_ the hung > tasks on the system before calling panic(). > > Quoting from > https://syzkaller.appspot.com/text?tag=CrashReport=5412451675799552 >

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

- On Apr 1, 2018, at 12:13 PM, One Thousand Gnomes gno...@lxorguk.ukuu.org.uk wrote: > On Tue, 27 Mar 2018 12:05:23 -0400 > Mathieu Desnoyers wrote: > >> Expose a new system call allowing each thread to register one userspace >> memory area to be used as an

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

- On Apr 1, 2018, at 12:13 PM, One Thousand Gnomes gno...@lxorguk.ukuu.org.uk wrote: > On Tue, 27 Mar 2018 12:05:23 -0400 > Mathieu Desnoyers wrote: > >> Expose a new system call allowing each thread to register one userspace >> memory area to be used as an ABI between kernel and

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: > On Mon, 02 Apr 2018 02:20:02 -0700 > syzbot wrote: > > > Hello, > > > > syzbot hit the following crash on upstream commit > > 0adb32858b0bddf4ada5f364a84ed60b196dbcda (Sun

Re: INFO: task hung in perf_trace_event_unreg

On Mon, Apr 02, 2018 at 09:40:40AM -0400, Steven Rostedt wrote: > On Mon, 02 Apr 2018 02:20:02 -0700 > syzbot wrote: > > > Hello, > > > > syzbot hit the following crash on upstream commit > > 0adb32858b0bddf4ada5f364a84ed60b196dbcda (Sun Apr 1 21:20:27 2018 +) > > Linux 4.16 > > syzbot

Re: [PATCH] tracing: avoid string overflow

On Wed, 28 Mar 2018 16:09:10 +0200 Arnd Bergmann wrote: > 'err' is used as a NUL-terminated string, but using strncpy() with the length > equal to the buffer size may result in lack of the termination: > > kernel/trace/trace_events_hist.c: In function 'hist_err_event': >

Re: [PATCH] tracing: avoid string overflow

On Wed, 28 Mar 2018 16:09:10 +0200 Arnd Bergmann wrote: > 'err' is used as a NUL-terminated string, but using strncpy() with the length > equal to the buffer size may result in lack of the termination: > > kernel/trace/trace_events_hist.c: In function 'hist_err_event': >

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

On Mon, Apr 02, 2018 at 10:03:58AM -0500, Christopher Lameter wrote: > On Sun, 1 Apr 2018, Alan Cox wrote: > > > >Restartable sequences are atomic with respect to preemption > > >(making it atomic with respect to other threads running on the > > >same CPU), as well as

Re: [RFC PATCH for 4.17 02/21] rseq: Introduce restartable sequences system call (v12)

On Mon, Apr 02, 2018 at 10:03:58AM -0500, Christopher Lameter wrote: > On Sun, 1 Apr 2018, Alan Cox wrote: > > > >Restartable sequences are atomic with respect to preemption > > >(making it atomic with respect to other threads running on the > > >same CPU), as well as

Re: [PATCH 0/4] tracing: A few inter-event bugfixes

On Wed, 28 Mar 2018 15:10:52 -0500 Tom Zanussi wrote: > Hi Steven, > > Here are a few bugfixes that should be applied on top of the > 'Inter-event (e.g. latency) support v9' patchset. Thanks, I pulled them in and will send them out to git after testing has

Re: [PATCH 0/4] tracing: A few inter-event bugfixes

On Wed, 28 Mar 2018 15:10:52 -0500 Tom Zanussi wrote: > Hi Steven, > > Here are a few bugfixes that should be applied on top of the > 'Inter-event (e.g. latency) support v9' patchset. Thanks, I pulled them in and will send them out to git after testing has succeeded. -- Steve > > The first

[RFC] vhost: introduce mdev based hardware vhost backend

This patch introduces a mdev (mediated device) based hardware vhost backend. This backend is an abstraction of the various hardware vhost accelerators (potentially any device that uses virtio ring can be used as a vhost accelerator). Some generic mdev parent ops are provided for accelerator

[RFC] vhost: introduce mdev based hardware vhost backend

This patch introduces a mdev (mediated device) based hardware vhost backend. This backend is an abstraction of the various hardware vhost accelerators (potentially any device that uses virtio ring can be used as a vhost accelerator). Some generic mdev parent ops are provided for accelerator

Re: [alsa-devel][PATCH 1/3 v3] ASoC: TSCS42xx: Shorten lines and other cleanup

On Wed, Mar 28, 2018 at 10:08:22AM -0500, Steven Eckhoff wrote: > Shorten lines greater than 80 chars > Add const to struct snd_soc_component_driver I only seem to have patches 1 and 2 here (and they aren't threaded with each other which is a bit odd too). I seem to recall this has been

Re: [alsa-devel][PATCH 1/3 v3] ASoC: TSCS42xx: Shorten lines and other cleanup

On Wed, Mar 28, 2018 at 10:08:22AM -0500, Steven Eckhoff wrote: > Shorten lines greater than 80 chars > Add const to struct snd_soc_component_driver I only seem to have patches 1 and 2 here (and they aren't threaded with each other which is a bit odd too). I seem to recall this has been

Re: [PATCH] MAINTAINERS: vfio/platform: Update sub-maintainer

On Mon, 26 Mar 2018 13:42:02 -0600 Alex Williamson wrote: > Baptiste has changed positions and has not been active with > vfio-platform, replace with the current, de-facto sub-maintainer > Eric Auger. Also add Alvise Rigo as a designated reviewer. > > Cc: Eric Auger

Re: [PATCH] MAINTAINERS: vfio/platform: Update sub-maintainer

On Mon, 26 Mar 2018 13:42:02 -0600 Alex Williamson wrote: > Baptiste has changed positions and has not been active with > vfio-platform, replace with the current, de-facto sub-maintainer > Eric Auger. Also add Alvise Rigo as a designated reviewer. > > Cc: Eric Auger > Cc: Alvise Rigo >

Re: [PATCH] connector: add parent pid and tgid to coredump and exit events

Hi David, I don't see how it breaks UAPI. The point is that structures coredump_proc_event and exit_proc_event are members of *union* event_data, thus position of the existing data in the structure is unchanged. Furthermore, this change won't increase size of struct proc_event, because

Re: [PATCH] connector: add parent pid and tgid to coredump and exit events

Hi David, I don't see how it breaks UAPI. The point is that structures coredump_proc_event and exit_proc_event are members of *union* event_data, thus position of the existing data in the structure is unchanged. Furthermore, this change won't increase size of struct proc_event, because

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