Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 11/06, Jaegeuk Kim wrote: > On 11/06, Yunlong Song wrote: > > Agree. > > > > On 2017/11/3 11:44, Jaegeuk Kim wrote: > > > On 10/13, Yunlong Song wrote: > > > > This can help us to debug on some corner case. > > > > > > > > Signed-off-by: Yunlong Song > > > >

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 11/06, Jaegeuk Kim wrote: > On 11/06, Yunlong Song wrote: > > Agree. > > > > On 2017/11/3 11:44, Jaegeuk Kim wrote: > > > On 10/13, Yunlong Song wrote: > > > > This can help us to debug on some corner case. > > > > > > > > Signed-off-by: Yunlong Song > > > > Signed-off-by: Chao Yu > > > >

Re: [RFC PATCH v2 for 4.15 08/14] Provide cpu_opv system call

- On Nov 6, 2017, at 9:07 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Mon, Nov 06, 2017 at 03:56:38PM -0500, Mathieu Desnoyers wrote: > [...] >> +static int cpu_op_pin_pages(unsigned long addr, unsigned long len, >> +struct page ***pinned_pages_ptr, size_t *nr_pinned, >> +

Re: [RFC PATCH v2 for 4.15 08/14] Provide cpu_opv system call

- On Nov 6, 2017, at 9:07 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Mon, Nov 06, 2017 at 03:56:38PM -0500, Mathieu Desnoyers wrote: > [...] >> +static int cpu_op_pin_pages(unsigned long addr, unsigned long len, >> +struct page ***pinned_pages_ptr, size_t *nr_pinned, >> +

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 11/06, Yunlong Song wrote: > Agree. > > On 2017/11/3 11:44, Jaegeuk Kim wrote: > > On 10/13, Yunlong Song wrote: > > > This can help us to debug on some corner case. > > > > > > Signed-off-by: Yunlong Song > > > Signed-off-by: Chao Yu > > > --- >

Re: [PATCH v2] f2fs: add bug_on when f2fs_gc even fails to get one victim

On 11/06, Yunlong Song wrote: > Agree. > > On 2017/11/3 11:44, Jaegeuk Kim wrote: > > On 10/13, Yunlong Song wrote: > > > This can help us to debug on some corner case. > > > > > > Signed-off-by: Yunlong Song > > > Signed-off-by: Chao Yu > > > --- > > > fs/f2fs/gc.c | 6 +- > > > 1 file

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

This patch tries its best to collect prefree segments and make it free to be used in the commit process, or it will use up free segments since prefree segments can not be used during commit process. As for your suggestion, I do consider that in an initial patch which does not send out, but I

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

This patch tries its best to collect prefree segments and make it free to be used in the commit process, or it will use up free segments since prefree segments can not be used during commit process. As for your suggestion, I do consider that in an initial patch which does not send out, but I

[PATCH 2/2] USB: serial: Change DbC debug device binding ID

The product ID for "Linux USB GDB Target device" has been changed. Change the driver binding table accordingly. This patch should be back-ported to kernels as old as v4.12, that contain the commit 57fb47279a04 ("usb/serial: Add DBC debug device support to usb_debug"). Cc:

[PATCH 2/2] USB: serial: Change DbC debug device binding ID

The product ID for "Linux USB GDB Target device" has been changed. Change the driver binding table accordingly. This patch should be back-ported to kernels as old as v4.12, that contain the commit 57fb47279a04 ("usb/serial: Add DBC debug device support to usb_debug"). Cc: # v4.12+ Cc: Johan

[PATCH 1/2] USB: early: Use new USB product ID and strings for DbC device

The DbC register set defines an interface for system software to specify the vendor id and product id for the debug device. These two values will be presented by the debug device in its device descriptor idVendor and idProduct fields. The current used product ID is a place holder. We now have a

[PATCH 1/2] USB: early: Use new USB product ID and strings for DbC device

The DbC register set defines an interface for system software to specify the vendor id and product id for the debug device. These two values will be presented by the debug device in its device descriptor idVendor and idProduct fields. The current used product ID is a place holder. We now have a

[PATCH] lockdep: Add missing declaration of 'pr_cont()'

An annoying compile warning due to missing declaration is shown below: In file included from lockdep.c:27:0: ../../../kernel/locking/lockdep.c: In function 'print_unlock_imbalance_bug' : ../../../kernel/locking/lockdep.c:3544:2: warning: implicit declaration of function 'pr_cont'

[PATCH] lockdep: Add missing declaration of 'pr_cont()'

An annoying compile warning due to missing declaration is shown below: In file included from lockdep.c:27:0: ../../../kernel/locking/lockdep.c: In function 'print_unlock_imbalance_bug' : ../../../kernel/locking/lockdep.c:3544:2: warning: implicit declaration of function 'pr_cont'

Re: [d_alloc_parallel] WARNING: bad unlock balance detected!

On Tue, Nov 07, 2017 at 10:01:13AM +0800, Fengguang Wu wrote: > Hi, > > Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. Why is it a bug at all? > [ 428.512005] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: RX > LKP: HOSTNAME vm-lkp-wsx03-openwrt-i386-8,

Re: [d_alloc_parallel] WARNING: bad unlock balance detected!

On Tue, Nov 07, 2017 at 10:01:13AM +0800, Fengguang Wu wrote: > Hi, > > Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. Why is it a bug at all? > [ 428.512005] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: RX > LKP: HOSTNAME vm-lkp-wsx03-openwrt-i386-8,

Re: [PATCH v3 2/3] usb: xhci: Add DbC support in xHCI driver

Hi, On 11/06/2017 04:00 PM, Greg Kroah-Hartman wrote: > On Mon, Nov 06, 2017 at 08:35:41AM +0800, Lu Baolu wrote: >> Hi, >> >> On 11/03/2017 02:27 PM, Greg Kroah-Hartman wrote: >>> On Fri, Nov 03, 2017 at 08:45:46AM +0800, Lu Baolu wrote: Hi, On 11/03/2017 12:51 AM, Greg

Re: [PATCH v3 2/3] usb: xhci: Add DbC support in xHCI driver

Hi, On 11/06/2017 04:00 PM, Greg Kroah-Hartman wrote: > On Mon, Nov 06, 2017 at 08:35:41AM +0800, Lu Baolu wrote: >> Hi, >> >> On 11/03/2017 02:27 PM, Greg Kroah-Hartman wrote: >>> On Fri, Nov 03, 2017 at 08:45:46AM +0800, Lu Baolu wrote: Hi, On 11/03/2017 12:51 AM, Greg

Re: [RFC -mm] mm, userfaultfd, THP: Avoid waiting when PMD under THP migration

On 6 Nov 2017, at 15:35, Andrea Arcangeli wrote: > On Mon, Nov 06, 2017 at 10:53:48AM -0500, Zi Yan wrote: >> Thanks for clarifying it. We both agree that !pmd_present(), which means >> PMD migration entry, does not get into userfaultfd_must_wait(), >> then there seems to be no issue with current

Re: [RFC -mm] mm, userfaultfd, THP: Avoid waiting when PMD under THP migration

On 6 Nov 2017, at 15:35, Andrea Arcangeli wrote: > On Mon, Nov 06, 2017 at 10:53:48AM -0500, Zi Yan wrote: >> Thanks for clarifying it. We both agree that !pmd_present(), which means >> PMD migration entry, does not get into userfaultfd_must_wait(), >> then there seems to be no issue with current

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 11/07, Chao Yu wrote: > On 2017/11/7 9:55, Jaegeuk Kim wrote: > > On 11/06, Yunlong Song wrote: > >> f2fs_balance_fs only actives once in the commit_inmem_pages, but there > >> are more than one page to commit, so all the other pages will miss the > >> check. This will lead to out-of-free

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 11/07, Chao Yu wrote: > On 2017/11/7 9:55, Jaegeuk Kim wrote: > > On 11/06, Yunlong Song wrote: > >> f2fs_balance_fs only actives once in the commit_inmem_pages, but there > >> are more than one page to commit, so all the other pages will miss the > >> check. This will lead to out-of-free

Re: [RFC PATCH v10 for 4.15 01/14] Restartable sequences system call

- On Nov 6, 2017, at 8:24 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Mon, Nov 06, 2017 at 03:56:31PM -0500, Mathieu Desnoyers wrote: > [...] >> + >> +/* >> + * struct rseq is aligned on 4 * 8 bytes to ensure it is always >> + * contained within a single cache-line. >> + * >> + * A single

Re: [RFC PATCH v10 for 4.15 01/14] Restartable sequences system call

- On Nov 6, 2017, at 8:24 PM, Boqun Feng boqun.f...@gmail.com wrote: > On Mon, Nov 06, 2017 at 03:56:31PM -0500, Mathieu Desnoyers wrote: > [...] >> + >> +/* >> + * struct rseq is aligned on 4 * 8 bytes to ensure it is always >> + * contained within a single cache-line. >> + * >> + * A single

Re: Regression still in next for drop migrate type checks

t; > failure in hands. The fix has been posted [1] and Andrew has picked it > > > up few days ago. Could you try to apply that patch? It will show up in > > > linux-next as soon as Andrew releases mmotm. > > > > Yes thanks I can confirm that next-20171106 works for me. So as far as > > I'm concerned, we're good to go. > > Can I assume your Tested-by? Yes sounds like it already got added. Regards, Tony

Re: Regression still in next for drop migrate type checks

arly is not suitable for "wider testing" ;) > > > > > > This is the first time I hear about the regression. Joonsoo has pointed > > > out that there might be a problem but he didn't have any specific > > > failure in hands. The fix has been posted [1] a

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 2017/11/7 9:55, Jaegeuk Kim wrote: > On 11/06, Yunlong Song wrote: >> f2fs_balance_fs only actives once in the commit_inmem_pages, but there >> are more than one page to commit, so all the other pages will miss the >> check. This will lead to out-of-free problem when commit a very large >>

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 2017/11/7 9:55, Jaegeuk Kim wrote: > On 11/06, Yunlong Song wrote: >> f2fs_balance_fs only actives once in the commit_inmem_pages, but there >> are more than one page to commit, so all the other pages will miss the >> check. This will lead to out-of-free problem when commit a very large >>

Re: [kernel-hardening] Re: [PATCH resend 2/2] userns: control capabilities of some user namespaces

On Mon, 2017-11-06 at 16:14 -0600, Serge E. Hallyn wrote: > Quoting Daniel Micay (danielmi...@gmail.com): > > Substantial added attack surface will never go away as a problem. > > There > > aren't a finite number of vulnerabilities to be found. > > There's varying levels of usefulness and

Re: [kernel-hardening] Re: [PATCH resend 2/2] userns: control capabilities of some user namespaces

On Mon, 2017-11-06 at 16:14 -0600, Serge E. Hallyn wrote: > Quoting Daniel Micay (danielmi...@gmail.com): > > Substantial added attack surface will never go away as a problem. > > There > > aren't a finite number of vulnerabilities to be found. > > There's varying levels of usefulness and

Re: [PATCH v4] arm64: support __int128 on gcc 5+

Hi Will, On Tue, Nov 7, 2017 at 11:13 AM, Will Deacon wrote: > So I pushed a fixup patch on top of for-next/core, but I suggest we > temporarily revert the- DCONFIG_ARCH_SUPPORTS_INT128 option if any other > issues crop up. The fixup looks good to me. If there are

Re: [PATCH v4] arm64: support __int128 on gcc 5+

Hi Will, On Tue, Nov 7, 2017 at 11:13 AM, Will Deacon wrote: > So I pushed a fixup patch on top of for-next/core, but I suggest we > temporarily revert the- DCONFIG_ARCH_SUPPORTS_INT128 option if any other > issues crop up. The fixup looks good to me. If there are additional problems, I'm

Re: [PATCH v4] arm64: support __int128 on gcc 5+

On Mon, Nov 06, 2017 at 03:59:18PM +, Catalin Marinas wrote: > On Mon, Nov 06, 2017 at 10:31:51AM +0100, Jason A. Donenfeld wrote: > > Versions of gcc prior to gcc 5 emitted a __multi3 function call when > > dealing with TI types, resulting in failures when trying to link to > > libgcc, and

Re: [PATCH v4] arm64: support __int128 on gcc 5+

On Mon, Nov 06, 2017 at 03:59:18PM +, Catalin Marinas wrote: > On Mon, Nov 06, 2017 at 10:31:51AM +0100, Jason A. Donenfeld wrote: > > Versions of gcc prior to gcc 5 emitted a __multi3 function call when > > dealing with TI types, resulting in failures when trying to link to > > libgcc, and

Re: [RFC PATCH v2 for 4.15 08/14] Provide cpu_opv system call

On Mon, Nov 06, 2017 at 03:56:38PM -0500, Mathieu Desnoyers wrote: [...] > +static int cpu_op_pin_pages(unsigned long addr, unsigned long len, > + struct page ***pinned_pages_ptr, size_t *nr_pinned, > + int write) > +{ > + struct page *pages[2]; > + int ret,

Re: [RFC PATCH v2 for 4.15 08/14] Provide cpu_opv system call

On Mon, Nov 06, 2017 at 03:56:38PM -0500, Mathieu Desnoyers wrote: [...] > +static int cpu_op_pin_pages(unsigned long addr, unsigned long len, > + struct page ***pinned_pages_ptr, size_t *nr_pinned, > + int write) > +{ > + struct page *pages[2]; > + int ret,

[PATCH v3] usb:xhci fix panic in xhci_free_virt_devices_depth_first

From: Yu Chen Check vdev->real_port 0 to avoid panic [9.261347] [] xhci_free_virt_devices_depth_first+0x58/0x108 [9.261352] [] xhci_mem_cleanup+0x1bc/0x570 [9.261355] [] xhci_stop+0x140/0x1c8 [9.261365] [] usb_remove_hcd+0xfc/0x1d0 [9.261369] []

[PATCH v3] usb:xhci fix panic in xhci_free_virt_devices_depth_first

From: Yu Chen Check vdev->real_port 0 to avoid panic [9.261347] [] xhci_free_virt_devices_depth_first+0x58/0x108 [9.261352] [] xhci_mem_cleanup+0x1bc/0x570 [9.261355] [] xhci_stop+0x140/0x1c8 [9.261365] [] usb_remove_hcd+0xfc/0x1d0 [9.261369] [] xhci_plat_remove+0x6c/0xa8 [

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hi Tejun, On (11/06/17 16:22), Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > > > would you be

Re: [PATCH 0/1] USB Audio Device Class 3.0 Gadget support

On Tue, Nov 7, 2017 at 3:52 AM, Ruslan Bilovol wrote: > Hi, > > This patch adds USB Audio Device Class 3.0 [1] function > support to gadget subsystem. > I didn't add UAC3 support to legacy gadget as it will > make preprocessor configuration too complex (UAC3 device >

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hi Tejun, On (11/06/17 16:22), Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > > > would you be

Re: [PATCH 0/1] USB Audio Device Class 3.0 Gadget support

On Tue, Nov 7, 2017 at 3:52 AM, Ruslan Bilovol wrote: > Hi, > > This patch adds USB Audio Device Class 3.0 [1] function > support to gadget subsystem. > I didn't add UAC3 support to legacy gadget as it will > make preprocessor configuration too complex (UAC3 device > must have two configurations

[PATCH 1/1] ALSA: usb: initial USB Audio Device Class 3.0 support

Recently released USB Audio Class 3.0 specification introduces many significant changes comparing to previous versions, like - new Power Domains, support for LPM/L1 - new Cluster descriptor - changed layout of all class-specific descriptors - new High Capability descriptors - New

[PATCH 0/1] USB Audio Device Class 3.0 support

Hi Takashi, This patch adds initial USB Audio Device Class 3.0 [1] support to the ALSA that we discussed at ELCE. The patch was tested with UAC3 gadget [2] that I posted to USB mailing list before. It is good for working with BADD device which implements such topologies like BAIF (Basic Audio

[PATCH 1/1] ALSA: usb: initial USB Audio Device Class 3.0 support

Recently released USB Audio Class 3.0 specification introduces many significant changes comparing to previous versions, like - new Power Domains, support for LPM/L1 - new Cluster descriptor - changed layout of all class-specific descriptors - new High Capability descriptors - New

[PATCH 0/1] USB Audio Device Class 3.0 support

Hi Takashi, This patch adds initial USB Audio Device Class 3.0 [1] support to the ALSA that we discussed at ELCE. The patch was tested with UAC3 gadget [2] that I posted to USB mailing list before. It is good for working with BADD device which implements such topologies like BAIF (Basic Audio

[d_alloc_parallel] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 428.512005] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX LKP: HOSTNAME vm-lkp-wsx03-openwrt-i386-8, MAC , kernel 4.14.0-rc8 158, serial console /dev/ttyS0 [ 429.798345] Kernel tests: Boot OK! [

[d_alloc_parallel] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 428.512005] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX LKP: HOSTNAME vm-lkp-wsx03-openwrt-i386-8, MAC , kernel 4.14.0-rc8 158, serial console /dev/ttyS0 [ 429.798345] Kernel tests: Boot OK! [

[copy_namespaces] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 266.395343] rcu-torture: rcu_torture_fakewriter task started [ 266.396862] rcu-torture: Creating rcu_torture_reader task [ 266.416970] rcu-torture: Creating rcu_torture_stats task [ 266.458705] [ 266.459151]

[copy_namespaces] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 266.395343] rcu-torture: rcu_torture_fakewriter task started [ 266.396862] rcu-torture: Creating rcu_torture_reader task [ 266.416970] rcu-torture: Creating rcu_torture_stats task [ 266.458705] [ 266.459151]

Re: [PATCH v2] usb:xhci fix panic in xhci_free_virt_devices_depth_first

On 2017/11/6 22:00, Mathias Nyman wrote: > On 06.11.2017 14:36, Chen Yu wrote: >> >> >> On 2017/11/6 19:32, Greg KH wrote: A simple process is as below: xhci_plat_probe() | usb_add_hcd()xhci_plat_remove() |

Re: [PATCH v2] usb:xhci fix panic in xhci_free_virt_devices_depth_first

On 2017/11/6 22:00, Mathias Nyman wrote: > On 06.11.2017 14:36, Chen Yu wrote: >> >> >> On 2017/11/6 19:32, Greg KH wrote: A simple process is as below: xhci_plat_probe() | usb_add_hcd()xhci_plat_remove() |

[load_elf_binary] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 66.941105] 8021q: adding VLAN 0 to HW filter on device eth0 [ 67.243706] 8021q: adding VLAN 0 to HW filter on device eth0 LKP: HOSTNAME vm-lkp-nex04-openwrt-ia32-4, MAC , kernel 4.14.0-rc8 158, serial console

[load_elf_binary] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 66.941105] 8021q: adding VLAN 0 to HW filter on device eth0 [ 67.243706] 8021q: adding VLAN 0 to HW filter on device eth0 LKP: HOSTNAME vm-lkp-nex04-openwrt-ia32-4, MAC , kernel 4.14.0-rc8 158, serial console

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 11/06, Yunlong Song wrote: > f2fs_balance_fs only actives once in the commit_inmem_pages, but there > are more than one page to commit, so all the other pages will miss the > check. This will lead to out-of-free problem when commit a very large > file. However, we cannot do f2fs_balance_fs for

Re: [PATCH v3] f2fs: fix out-of-free problem caused by atomic write

On 11/06, Yunlong Song wrote: > f2fs_balance_fs only actives once in the commit_inmem_pages, but there > are more than one page to commit, so all the other pages will miss the > check. This will lead to out-of-free problem when commit a very large > file. However, we cannot do f2fs_balance_fs for

[gcov_enable_events] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 29.314270] rcu-perf: rcu_perf_writer task started [ 29.329146] audit: initializing netlink subsys (disabled) [ 29.337989] audit: type=2000 audit(1510004207.289:1): state=initialized audit_enabled=0 res=1 [

[gcov_enable_events] WARNING: bad unlock balance detected!

Hi, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 29.314270] rcu-perf: rcu_perf_writer task started [ 29.329146] audit: initializing netlink subsys (disabled) [ 29.337989] audit: type=2000 audit(1510004207.289:1): state=initialized audit_enabled=0 res=1 [

[PATCH 1/1] usb: gadget: add USB Audio Device Class 3.0 gadget support

Recently released USB Audio Class 3.0 specification introduces many significant changes comparing to previous versions, like - new Power Domains, support for LPM/L1 - new Cluster descriptor - changed layout of all class-specific descriptors - new High Capability descriptors - New

[PATCH 1/1] usb: gadget: add USB Audio Device Class 3.0 gadget support

Recently released USB Audio Class 3.0 specification introduces many significant changes comparing to previous versions, like - new Power Domains, support for LPM/L1 - new Cluster descriptor - changed layout of all class-specific descriptors - new High Capability descriptors - New

[PATCH 0/1] USB Audio Device Class 3.0 Gadget support

Hi, This patch adds USB Audio Device Class 3.0 [1] function support to gadget subsystem. I didn't add UAC3 support to legacy gadget as it will make preprocessor configuration too complex (UAC3 device must have two configurations for backward compatibility, first is UAC1/2 and second is UAC3), yet

[PATCH 0/1] USB Audio Device Class 3.0 Gadget support

Hi, This patch adds USB Audio Device Class 3.0 [1] function support to gadget subsystem. I didn't add UAC3 support to legacy gadget as it will make preprocessor configuration too complex (UAC3 device must have two configurations for backward compatibility, first is UAC1/2 and second is UAC3), yet

Re: [PATCH v2 0/9] memfd: add sealing to hugetlb-backed memory

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Hi, > > Recently, Mike Kravetz added hugetlbfs support to memfd. However, he > didn't add sealing support. One of the reasons to use memfd is to have > shared memory sealing when doing IPC or sharing memory with another > process with some extra

Re: [PATCH v2 0/9] memfd: add sealing to hugetlb-backed memory

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Hi, > > Recently, Mike Kravetz added hugetlbfs support to memfd. However, he > didn't add sealing support. One of the reasons to use memfd is to have > shared memory sealing when doing IPC or sharing memory with another > process with some extra

[apic_ap_setup] WARNING: suspicious RCU usage

Hi, Here is a warning in 4.14-rc8 -- it's not necessarily a new bug. [ 112.658399] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 112.669928] kvm-clock: cpu 1, msr 0:3544e041, secondary cpu clock [ 112.670585] masked ExtINT on CPU#1 [[ 112.671160] [ 112.671161]

Re: [PATCH net-next 01/11] net: dsa: constify cpu_dp member of dsa_port

On 11/06/2017 01:11 PM, Vivien Didelot wrote: > A DSA port has a dedicated CPU port assigned to it, stored in the cpu_dp > member. It is not meant to be modified by a port, thus make it const. > > Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli

[apic_ap_setup] WARNING: suspicious RCU usage

Hi, Here is a warning in 4.14-rc8 -- it's not necessarily a new bug. [ 112.658399] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 112.669928] kvm-clock: cpu 1, msr 0:3544e041, secondary cpu clock [ 112.670585] masked ExtINT on CPU#1 [[ 112.671160] [ 112.671161]

Re: [PATCH net-next 01/11] net: dsa: constify cpu_dp member of dsa_port

On 11/06/2017 01:11 PM, Vivien Didelot wrote: > A DSA port has a dedicated CPU port assigned to it, stored in the cpu_dp > member. It is not meant to be modified by a port, thus make it const. > > Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH v2 9/9] memfd-test: run fuse test on hugetlb backend memory

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Suggested-by: Mike Kravetz > Signed-off-by: Marc-André Lureau > --- > tools/testing/selftests/memfd/fuse_test.c | 30 > ++ >

Re: [PATCH v2 9/9] memfd-test: run fuse test on hugetlb backend memory

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Suggested-by: Mike Kravetz > Signed-off-by: Marc-André Lureau > --- > tools/testing/selftests/memfd/fuse_test.c | 30 > ++ > tools/testing/selftests/memfd/run_fuse_test.sh | 2 +- >

Re: [PATCH v3] printk: Add console owner and waiter logic to load balance console writes

On (11/06/17 21:06), Tetsuo Handa wrote: > I tried your patch with warn_alloc() torture. It did not cause lockups. > But I felt that possibility of failing to flush last second messages (such > as SysRq-c or SysRq-b) to consoles has increased. Is this psychological? do I understand it correctly

Re: [PATCH v3] printk: Add console owner and waiter logic to load balance console writes

On (11/06/17 21:06), Tetsuo Handa wrote: > I tried your patch with warn_alloc() torture. It did not cause lockups. > But I felt that possibility of failing to flush last second messages (such > as SysRq-c or SysRq-b) to consoles has increased. Is this psychological? do I understand it correctly

Re: Re: [PATCH] ksm : use checksum and memcmp for rb_tree

Sorry, re-send this email because of the Delivery failed message (to linux-kernel) On 2017-10-30 오후 10:22, Timofey Titovets wrote: 2017-10-30 15:03 GMT+03:00 Kyeongdon Kim : > The current ksm is using memcmp to insert and search 'rb_tree'. > It does cause very expensive

Re: Re: [PATCH] ksm : use checksum and memcmp for rb_tree

Sorry, re-send this email because of the Delivery failed message (to linux-kernel) On 2017-10-30 오후 10:22, Timofey Titovets wrote: 2017-10-30 15:03 GMT+03:00 Kyeongdon Kim : > The current ksm is using memcmp to insert and search 'rb_tree'. > It does cause very expensive computation cost. > In

[apparmor_mmap_file] WARNING: bad unlock balance detected!

t 1 zonelists, mobility grouping on. Total pages: 106550 [0.00] Kernel command line: ip=vm-lkp-nhm-dp1-openwrt-ia32-6::dhcp root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-lkp-nhm-dp1-openwrt-ia32-6/trinity-300s-openwrt-i386-2016-03-16.cgz-39dae59d66acd86d1de24294bd2f343fd5e7a625-20171

[apparmor_mmap_file] WARNING: bad unlock balance detected!

t 1 zonelists, mobility grouping on. Total pages: 106550 [0.00] Kernel command line: ip=vm-lkp-nhm-dp1-openwrt-ia32-6::dhcp root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-lkp-nhm-dp1-openwrt-ia32-6/trinity-300s-openwrt-i386-2016-03-16.cgz-39dae59d66acd86d1de24294bd2f343fd5e7a625-20171

Re: [PATCH v2 8/9] memfd-test: move common code to a shared unit

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > The memfd & fuse tests will share more common code in the following > commits to test hugetlb support. > > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz >

Re: [PATCH v2 8/9] memfd-test: move common code to a shared unit

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > The memfd & fuse tests will share more common code in the following > commits to test hugetlb support. > > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz > --- > tools/testing/selftests/memfd/Makefile | 5

Re: [PATCH v2 7/9] memfd-test: add 'memfd-hugetlb:' prefix when testing hugetlbfs

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Suggested-by: Mike Kravetz > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz > --- > tools/testing/selftests/memfd/memfd_test.c | 26

Re: [PATCH v2 7/9] memfd-test: add 'memfd-hugetlb:' prefix when testing hugetlbfs

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Suggested-by: Mike Kravetz > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz > --- > tools/testing/selftests/memfd/memfd_test.c | 26 -- > 1 file changed, 16 insertions(+), 10 deletions(-)

[PATCH 3.2 007/147] usb: renesas_usbhs: fixup resume method for autonomy mode

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Kuninori Morimoto commit 5b50d3b52601651ef3183cfb33d03cf486180e48 upstream. If renesas_usbhs is probed as autonomy mode, phy reset should be called after

[PATCH 3.2 007/147] usb: renesas_usbhs: fixup resume method for autonomy mode

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Kuninori Morimoto commit 5b50d3b52601651ef3183cfb33d03cf486180e48 upstream. If renesas_usbhs is probed as autonomy mode, phy reset should be called after power resumed, and manual cold-plug

[PATCH 3.2 019/147] IB/ipoib: Prevent setting negative values to max_nonsrq_conn_qp

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Vesker commit 11f74b40359b19f760964e71d04882a6caf530cc upstream. Don't allow negative values to max_nonsrq_conn_qp. There is no functional impact on a negative value

[PATCH 3.2 019/147] IB/ipoib: Prevent setting negative values to max_nonsrq_conn_qp

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Vesker commit 11f74b40359b19f760964e71d04882a6caf530cc upstream. Don't allow negative values to max_nonsrq_conn_qp. There is no functional impact on a negative value but it is logicically

[PATCH v3 2/2] PM / QoS: Fix device resume latency framework

From: Rafael J. Wysocki The special value of 0 for device resume latency PM QoS means "no restriction", but there are two problems with that. First, device resume latency PM QoS requests with 0 as the value are always put in front of requests with positive values in

[PATCH v3 2/2] PM / QoS: Fix device resume latency framework

From: Rafael J. Wysocki The special value of 0 for device resume latency PM QoS means "no restriction", but there are two problems with that. First, device resume latency PM QoS requests with 0 as the value are always put in front of requests with positive values in the priority lists used

[PATCH 3.2 011/147] x86/acpi: Prevent out of bound access caused by broken ACPI tables

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Seunghun Han commit dad5ab0db8deac535d03e3fe3d8f2892173fa6a4 upstream. The bus_irq argument of mp_override_legacy_irq() is used as the index into the isa_irq_to_gsi[]

Re: [PATCH v2 6/9] memfd-tests: test hugetlbfs sealing

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Remove most of the special-casing of hugetlbfs now that sealing > is supported. > > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz > --- >

[PATCH 3.2 011/147] x86/acpi: Prevent out of bound access caused by broken ACPI tables

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Seunghun Han commit dad5ab0db8deac535d03e3fe3d8f2892173fa6a4 upstream. The bus_irq argument of mp_override_legacy_irq() is used as the index into the isa_irq_to_gsi[] array. The bus_irq

Re: [PATCH v2 6/9] memfd-tests: test hugetlbfs sealing

On 11/06/2017 06:39 AM, Marc-André Lureau wrote: > Remove most of the special-casing of hugetlbfs now that sealing > is supported. > > Signed-off-by: Marc-André Lureau Reviewed-by: Mike Kravetz -- Mike Kravetz > --- > tools/testing/selftests/memfd/memfd_test.c | 150 >

[PATCH v3 1/2] PM / domains: Rework governor code to be more consistent

From: Rafael J. Wysocki The genpd governor currently uses negative PM QoS values to indicate the "no suspend" condition and 0 as "no restriction", but it doesn't use them consistently. Moreover, it tries to refresh QoS values for already suspended devices in a quite

[PATCH v3 1/2] PM / domains: Rework governor code to be more consistent

From: Rafael J. Wysocki The genpd governor currently uses negative PM QoS values to indicate the "no suspend" condition and 0 as "no restriction", but it doesn't use them consistently. Moreover, it tries to refresh QoS values for already suspended devices in a quite questionable way. For the

[PATCH 3.2 127/147] staging: cxt1e1: remove unnecessary function, VMETRO_TRACE

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit ce8386da7488c998969288355111996c2c23c892 upstream. VMETRO_TRACE isn't called from anywhere. So delete it. Signed-off-by: SeongJae Park

[PATCH 3.2 127/147] staging: cxt1e1: remove unnecessary function, VMETRO_TRACE

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit ce8386da7488c998969288355111996c2c23c892 upstream. VMETRO_TRACE isn't called from anywhere. So delete it. Signed-off-by: SeongJae Park Reviewed-by: Dan Carpenter

[PATCH 3.2 010/147] mount: copy the port field into the cloned nfs_server structure.

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Steve Dickson commit 89a6814d9b665b196aa3a102f96b6dc7e8cb669e upstream. Doing this copy eliminates the "port=0" entry in the /proc/mounts entries Fixes:

[PATCH 3.2 010/147] mount: copy the port field into the cloned nfs_server structure.

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Steve Dickson commit 89a6814d9b665b196aa3a102f96b6dc7e8cb669e upstream. Doing this copy eliminates the "port=0" entry in the /proc/mounts entries Fixes:

[PATCH 3.2 000/147] 3.2.95-rc1 review

This is the start of the stable review cycle for the 3.2.95 release. There are 147 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Fri Nov 08 18:00:00 UTC 2017. Anything

[PATCH 3.2 000/147] 3.2.95-rc1 review

This is the start of the stable review cycle for the 3.2.95 release. There are 147 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Fri Nov 08 18:00:00 UTC 2017. Anything

[PATCH 3.2 003/147] staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 105967ad68d2eb1a041bc041f9cf96af2a653b65 upstream. gcc-7 points out an older regression: drivers/staging/iio/resolver/ad2s1210.c: In function

[PATCH 3.2 135/147] mct_u232: Fix use of uninitialized pointer in mct_u323_startup()

3.2.95-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings My backport of commit 4e9a0b05257f "USB: mct_u232: add sanity checking in probe" incorrectly added a dev_err() call using port->dev before 'port' was

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