linux-next: Tree for Nov 7

Hi all, Changes since 20171106: The powerpc tree still had its build failure for which I applied a patch. The crypto tree lost its build failure. The akpm tree still had its build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 10912 10165 files changed

linux-next: Tree for Nov 7

Hi all, Changes since 20171106: The powerpc tree still had its build failure for which I applied a patch. The crypto tree lost its build failure. The akpm tree still had its build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 10912 10165 files changed

[PATCH v2 2/5] soc: qcom: Introduce QMI helpers

Drivers that needs to communicate with a remote QMI service all has to perform the operations of discovering the service, encoding and decoding the messages and operate the socket. This introduces an abstraction for these common operations, reducing most of the duplication in such cases.

[PATCH v2 5/5] samples: Introduce Qualcomm QMI sample client

Introduce a sample driver that register for server notifications and spawn clients for each available test service (service 15). The spawned clients implements the interface for encoding "ping" and "data" requests and decode the responses from the remote. Signed-off-by: Bjorn Andersson

[PATCH v2 2/5] soc: qcom: Introduce QMI helpers

Drivers that needs to communicate with a remote QMI service all has to perform the operations of discovering the service, encoding and decoding the messages and operate the socket. This introduces an abstraction for these common operations, reducing most of the duplication in such cases.

[PATCH v2 5/5] samples: Introduce Qualcomm QMI sample client

Introduce a sample driver that register for server notifications and spawn clients for each available test service (service 15). The spawned clients implements the interface for encoding "ping" and "data" requests and decode the responses from the remote. Signed-off-by: Bjorn Andersson ---

[PATCH v2 1/5] soc: qcom: Introduce QMI encoder/decoder

Add the helper library for encoding and decoding QMI encoded messages. The implementation is taken from lib/qmi_encdec.c of the Qualcomm kernel (msm-3.18). Modifications has been made to the public API, source buffers has been made const and the debug-logging part was omitted, for now.

[PATCH v2 3/5] remoteproc: Pass type of shutdown to subdev remove

remoteproc instances can be stopped either by invoking shutdown or by an attempt to recover from a crash. For some subdev types it's expected to clean up gracefully during a shutdown, but are unable to do so during a crash - so pass this information to the subdev remove functions. Signed-off-by:

[PATCH v2 4/5] remoteproc: qcom: Introduce sysmon

The sysmon client communicates either via a dedicated SMD/GLINK channel or via QMI encoded messages over IPCROUTER with remote processors in order to perform graceful shutdown and inform about other remote processors shutting down. Signed-off-by: Bjorn Andersson ---

[PATCH v2 1/5] soc: qcom: Introduce QMI encoder/decoder

Add the helper library for encoding and decoding QMI encoded messages. The implementation is taken from lib/qmi_encdec.c of the Qualcomm kernel (msm-3.18). Modifications has been made to the public API, source buffers has been made const and the debug-logging part was omitted, for now.

[PATCH v2 3/5] remoteproc: Pass type of shutdown to subdev remove

remoteproc instances can be stopped either by invoking shutdown or by an attempt to recover from a crash. For some subdev types it's expected to clean up gracefully during a shutdown, but are unable to do so during a crash - so pass this information to the subdev remove functions. Signed-off-by:

[PATCH v2 4/5] remoteproc: qcom: Introduce sysmon

The sysmon client communicates either via a dedicated SMD/GLINK channel or via QMI encoded messages over IPCROUTER with remote processors in order to perform graceful shutdown and inform about other remote processors shutting down. Signed-off-by: Bjorn Andersson --- Changes since v1: - New

[PATCH v2 0/5] In-kernel QMI helpers and sysmon

This series introduces a helper library for drivers that needs to implement clients or services in the kernel for communicating with QMI encoded messages. This is used by a set of drivers in order to implement control signaling that needs to happen between a driver and a service on a remote

[PATCH v2 0/5] In-kernel QMI helpers and sysmon

This series introduces a helper library for drivers that needs to implement clients or services in the kernel for communicating with QMI encoded messages. This is used by a set of drivers in order to implement control signaling that needs to happen between a driver and a service on a remote

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

On 2017-11-07 at 02:23:18 +0100, Rafael J. Wysocki wrote: > 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

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

On 2017-11-07 at 02:23:18 +0100, Rafael J. Wysocki wrote: > 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

Re: POWER: Unexpected fault when writing to brk-allocated memory

C'ing everyone who was on the x86 56-bit user virtual address patch. I think we need more time to discuss this behaviour, in light of the regression Florian uncovered. I would propose we turn off the 56-bit user virtual address support for x86 for 4.14, and powerpc would follow and turn off its

Re: POWER: Unexpected fault when writing to brk-allocated memory

C'ing everyone who was on the x86 56-bit user virtual address patch. I think we need more time to discuss this behaviour, in light of the regression Florian uncovered. I would propose we turn off the 56-bit user virtual address support for x86 for 4.14, and powerpc would follow and turn off its

Re: [PATCH v3 2/2] gpio: aspeed: Add support for reset tolerance

On Wed, Nov 1, 2017 at 2:34 PM, Andrew Jeffery wrote: > Use the new pinconf parameter for state persistence to expose the > associated capability of the Aspeed GPIO controller. > > Signed-off-by: Andrew Jeffery I took a look and checked the offsets against the

Re: [PATCH v3 2/2] gpio: aspeed: Add support for reset tolerance

On Wed, Nov 1, 2017 at 2:34 PM, Andrew Jeffery wrote: > Use the new pinconf parameter for state persistence to expose the > associated capability of the Aspeed GPIO controller. > > Signed-off-by: Andrew Jeffery I took a look and checked the offsets against the datasheet. LGTM. Reviewed-by:

RE: [PATCH v16 5/6] vfio: ABI for mdev display dma-buf operation

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, November 7, 2017 4:37 AM > To: Gerd Hoffmann > Cc: Zhang, Tina ; Tian, Kevin ; > Daniel Vetter ;

RE: [PATCH v16 5/6] vfio: ABI for mdev display dma-buf operation

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, November 7, 2017 4:37 AM > To: Gerd Hoffmann > Cc: Zhang, Tina ; Tian, Kevin ; > Daniel Vetter ; intel-...@lists.freedesktop.org; > joonas.lahti...@linux.intel.com;

[PATCH] qrtr: Move to postcore_initcall

Registering qrtr with module_init makes the ability of typical platform code to create AF_QIPCRTR socket during probe a matter of link order luck. Moving qrtr to postcore_initcall() avoids this. Signed-off-by: Bjorn Andersson --- net/qrtr/qrtr.c | 2 +- 1 file

[PATCH] qrtr: Move to postcore_initcall

Registering qrtr with module_init makes the ability of typical platform code to create AF_QIPCRTR socket during probe a matter of link order luck. Moving qrtr to postcore_initcall() avoids this. Signed-off-by: Bjorn Andersson --- net/qrtr/qrtr.c | 2 +- 1 file changed, 1 insertion(+), 1

[rbtree_test_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]

Hi Davidlohr, Here's a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 103.655201] xz_dec_test: module loaded [ 103.655994] xz_dec_test: Create a device node with 'mknod xz_dec_test c 249 0' and write .xz files to it. [ 103.796051] atomic64_test: passed for i386+ platform with

[rbtree_test_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]

Hi Davidlohr, Here's a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 103.655201] xz_dec_test: module loaded [ 103.655994] xz_dec_test: Create a device node with 'mknod xz_dec_test c 249 0' and write .xz files to it. [ 103.796051] atomic64_test: passed for i386+ platform with

[PATCH] documentation: update list of available compiled-in fonts

From: Randy Dunlap Update list of available compiled-in fonts in lib/fonts/: add 6x10 and drop RomanLarge (which was reverted 12 years ago). Signed-off-by: Randy Dunlap Cc: Geert Uytterhoeven --- Documentation/fb/fbcon.txt |

[PATCH] documentation: update list of available compiled-in fonts

From: Randy Dunlap Update list of available compiled-in fonts in lib/fonts/: add 6x10 and drop RomanLarge (which was reverted 12 years ago). Signed-off-by: Randy Dunlap Cc: Geert Uytterhoeven --- Documentation/fb/fbcon.txt |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---

[test_drm_mm_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]

Hi Chris, Here's a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 134.914567] console [ttyS0] enabled [ 134.943214] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 134.974836] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [

[test_drm_mm_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]

Hi Chris, Here's a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 134.914567] console [ttyS0] enabled [ 134.943214] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 134.974836] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [

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

On 2017-11-07 at 02:27:05 +0100, Rafael J. Wysocki wrote: > 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

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

On 2017-11-07 at 02:27:05 +0100, Rafael J. Wysocki wrote: > 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

[interval_tree_test_init] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]

Hi Davidlohr, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 265.102312] xz_dec_test: module loaded [ 265.111774] xz_dec_test: Create a device node with 'mknod xz_dec_test c 246 0' and write .xz files to it. [ 265.160320] atomic64_test: passed for x86-64 platform with

[interval_tree_test_init] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]

Hi Davidlohr, Here is a warning in v4.14-rc8 -- it's not necessarily a new bug. [ 265.102312] xz_dec_test: module loaded [ 265.111774] xz_dec_test: Create a device node with 'mknod xz_dec_test c 246 0' and write .xz files to it. [ 265.160320] atomic64_test: passed for x86-64 platform with

Re: [PATCH 1/2] printk: Relocate wake_klogd check close to the end of console_unlock()

On (11/02/17 06:51), Tejun Heo wrote: > We mark for waking up klogd whenever we see a new message sequence in > the main loop. However, the actual wakeup is always at the end of the > function and we can easily test for the wakeup condition when we do > the final should-we-repeat check. > > Move

Re: [PATCH 1/2] printk: Relocate wake_klogd check close to the end of console_unlock()

On (11/02/17 06:51), Tejun Heo wrote: > We mark for waking up klogd whenever we see a new message sequence in > the main loop. However, the actual wakeup is always at the end of the > function and we can easily test for the wakeup condition when we do > the final should-we-repeat check. > > Move

[sock_def_readable] WARNING: bad unlock balance detected!

FYI, this warning shows up in both v4.14-rc8 and v4.13: [ 144.578809] br-lan: port 1(eth0) entered disabled state [ 144.581360] device eth0 left promiscuous mode [ 144.582699] br-lan: port 1(eth0) entered disabled state [ 144.685012] [ 144.685370] = [

[sock_def_readable] WARNING: bad unlock balance detected!

FYI, this warning shows up in both v4.14-rc8 and v4.13: [ 144.578809] br-lan: port 1(eth0) entered disabled state [ 144.581360] device eth0 left promiscuous mode [ 144.582699] br-lan: port 1(eth0) entered disabled state [ 144.685012] [ 144.685370] = [

Re: [PATCH 4.4 28/40] drm/msm/dsi: Set msm_dsi->encoders before initializing bridge

Hi Greg, On 11/06/2017 03:15 PM, Greg Kroah-Hartman wrote: 4.4-stable review patch. If anyone has any objections, please let me know. This patch isn't needed on 4.4 or the 4.9 stable branches. This was required only after drm_bridge API was changed with the commit: (3bb80f2495) drm: bridge:

Re: [PATCH 4.4 28/40] drm/msm/dsi: Set msm_dsi->encoders before initializing bridge

Hi Greg, On 11/06/2017 03:15 PM, Greg Kroah-Hartman wrote: 4.4-stable review patch. If anyone has any objections, please let me know. This patch isn't needed on 4.4 or the 4.9 stable branches. This was required only after drm_bridge API was changed with the commit: (3bb80f2495) drm: bridge:

Re: [PATCH 0/4] scsi: qla2xxx: Convert timers to use timer_setup()

On Mon, 2017-11-06 at 19:58 +, Madhani, Himanshu wrote: > On Nov 5, 2017, at 4:18 PM, Bart Van Assche wrote: > > The qla2xxx driver does not crash if apply these four patches on kernel > > v4.14-rc8 and load the qla2xxx driver on my test setup. Point-to-point > > mode

Re: [PATCH 0/4] scsi: qla2xxx: Convert timers to use timer_setup()

On Mon, 2017-11-06 at 19:58 +, Madhani, Himanshu wrote: > On Nov 5, 2017, at 4:18 PM, Bart Van Assche wrote: > > The qla2xxx driver does not crash if apply these four patches on kernel > > v4.14-rc8 and load the qla2xxx driver on my test setup. Point-to-point > > mode seems broken again but I

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

Sorry, misunderstanding, because I think when sync == true, FG_GC does not check has_not_enough_free_secs, so maybe it does not have to do any gc at all. For example, if there are 100 segments for f2fs, and 20 segments are full or valid blocks over fggc_threshold, then it is correct to fail in

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

Sorry, misunderstanding, because I think when sync == true, FG_GC does not check has_not_enough_free_secs, so maybe it does not have to do any gc at all. For example, if there are 100 segments for f2fs, and 20 segments are full or valid blocks over fggc_threshold, then it is correct to fail in

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

CC locking people. On Tue, Nov 07, 2017 at 02:33:28AM +, Al Viro wrote: 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

Re: [PATCH] mpt3sas: fix dma_addr_t casts

Arnd, > After taking a closer look, I found that the problem is that the new > code mixes up pointers and dma_addr_t values unnecessarily. > > This changes it to use the correct types consistently, which lets us > get rid of a lot of type casts in the process. I'm also renaming some > variables

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

CC locking people. On Tue, Nov 07, 2017 at 02:33:28AM +, Al Viro wrote: 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

Re: [PATCH] mpt3sas: fix dma_addr_t casts

Arnd, > After taking a closer look, I found that the problem is that the new > code mixes up pointers and dma_addr_t values unnecessarily. > > This changes it to use the correct types consistently, which lets us > get rid of a lot of type casts in the process. I'm also renaming some > variables

Re: [PATCH v2] scsi: be2iscsi: Use kasprintf

Jitendra, >> Use kasprintf instead of combination of kmalloc and sprintf. >> Also, remove BEISCSI_MSI_NAME macro used to specify size of string as >> kasprintf handles size computations. >> >> Signed-off-by: Himanshu Jha > Reviewed-by: Jitendra Bhivare

Re: [PATCH v2] scsi: be2iscsi: Use kasprintf

Jitendra, >> Use kasprintf instead of combination of kmalloc and sprintf. >> Also, remove BEISCSI_MSI_NAME macro used to specify size of string as >> kasprintf handles size computations. >> >> Signed-off-by: Himanshu Jha > Reviewed-by: Jitendra Bhivare Applied to 4.15/scsi-queue. -- Martin

Re: [PATCH] ASoC: intel: initialize return value properly

On Mon, Nov 06, 2017 at 02:30:36PM +0100, Arnd Bergmann wrote: > When CONFIG_SND_SOC_HDAC_HDMI is disabled, we can run into an > uninitialized variable: > > sound/soc/intel/skylake/skl.c: In function 'skl_resume': > sound/soc/intel/skylake/skl.c:326:6: error: 'ret' may be used uninitialized > in

Re: [PATCH] ASoC: intel: initialize return value properly

On Mon, Nov 06, 2017 at 02:30:36PM +0100, Arnd Bergmann wrote: > When CONFIG_SND_SOC_HDAC_HDMI is disabled, we can run into an > uninitialized variable: > > sound/soc/intel/skylake/skl.c: In function 'skl_resume': > sound/soc/intel/skylake/skl.c:326:6: error: 'ret' may be used uninitialized > in

Re: [RFC PATCH] mm, oom_reaper: gather each vma to prevent leaking TLB entry

On 2017/11/6 19:57, Michal Hocko wrote: On Mon 06-11-17 19:03:34, Wangnan (F) wrote: On 2017/11/6 18:40, Michal Hocko wrote: On Mon 06-11-17 17:59:54, Wangnan (F) wrote: On 2017/11/6 16:52, Michal Hocko wrote: On Mon 06-11-17 15:04:40, Bob Liu wrote: On Mon, Nov 6, 2017 at 11:36 AM, Wang

Re: [RFC PATCH] mm, oom_reaper: gather each vma to prevent leaking TLB entry

On 2017/11/6 19:57, Michal Hocko wrote: On Mon 06-11-17 19:03:34, Wangnan (F) wrote: On 2017/11/6 18:40, Michal Hocko wrote: On Mon 06-11-17 17:59:54, Wangnan (F) wrote: On 2017/11/6 16:52, Michal Hocko wrote: On Mon 06-11-17 15:04:40, Bob Liu wrote: On Mon, Nov 6, 2017 at 11:36 AM, Wang

Re: [PATCH v3] kbuild: fix linker feature test macros when cross compiling with Clang

2017-11-07 3:47 GMT+09:00 Nick Desaulniers : > I was not seeing my linker flags getting added when using ld-option when > cross compiling with Clang. Upon investigation, this seems to be due to > a difference in how GCC vs Clang handle cross compilation. > > GCC is

Re: [PATCH v3] kbuild: fix linker feature test macros when cross compiling with Clang

2017-11-07 3:47 GMT+09:00 Nick Desaulniers : > I was not seeing my linker flags getting added when using ld-option when > cross compiling with Clang. Upon investigation, this seems to be due to > a difference in how GCC vs Clang handle cross compilation. > > GCC is configured at build time to

Re: [PATCH v2] uvc: Add D3DFMT_L8 support

Hi Nicolas, Thank you for the patch. On Monday, 6 November 2017 22:13:28 EET Nicolas Dufresne wrote: > Microsoft HoloLense UVC sensor uses D3DFMT instead of FOURCC when > exposing formats. This adds support for D3DFMT_L8 as exposed from > the Acer Windows Mixed Reality Headset. > >

Re: [PATCH v2] uvc: Add D3DFMT_L8 support

Hi Nicolas, Thank you for the patch. On Monday, 6 November 2017 22:13:28 EET Nicolas Dufresne wrote: > Microsoft HoloLense UVC sensor uses D3DFMT instead of FOURCC when > exposing formats. This adds support for D3DFMT_L8 as exposed from > the Acer Windows Mixed Reality Headset. > >

Re: [PATCH] storvsc: Avoid excessive host scan on controller change

Long, > When there are multiple disks attached to the same SCSI controller, > the host may send several VSTOR_OPERATION_REMOVE_DEVICE or > VSTOR_OPERATION_ENUMERATE_BUS messages in a row, to indicate there is > a change on the SCSI controller. In response, storvsc rescans the SCSI > host.

Re: [PATCH] storvsc: Avoid excessive host scan on controller change

Long, > When there are multiple disks attached to the same SCSI controller, > the host may send several VSTOR_OPERATION_REMOVE_DEVICE or > VSTOR_OPERATION_ENUMERATE_BUS messages in a row, to indicate there is > a change on the SCSI controller. In response, storvsc rescans the SCSI > host.

Re: [PATCH 3.16 153/294] dm: convert DM printk macros to pr_ macros

On Mon, Nov 06 2017 at 10:19pm -0500, Joe Perches wrote: > On Mon, 2017-11-06 at 23:03 +, Ben Hutchings wrote: > > 3.16.50-rc1 review patch. If anyone has any objections, please let me know. > > Why include this? It's a simplification, not a bug fix. Logical reason is

Re: [PATCH 3.16 153/294] dm: convert DM printk macros to pr_ macros

On Mon, Nov 06 2017 at 10:19pm -0500, Joe Perches wrote: > On Mon, 2017-11-06 at 23:03 +, Ben Hutchings wrote: > > 3.16.50-rc1 review patch. If anyone has any objections, please let me know. > > Why include this? It's a simplification, not a bug fix. Logical reason is it serves as a

Re: [f2fs-dev] [PATCH] f2fs: keep scanning until enough free nids are acquired

Hi, I merged this patch after fixing some broken format. Could you please check your email configuration? Thanks, On 11/07, Fan Li wrote: > In current version, after scan_free_nid_bits, the scan is over if > nid_cnt[FREE_NID] != 0. > In most cases, there are still free nids in the free list

Re: [f2fs-dev] [PATCH] f2fs: keep scanning until enough free nids are acquired

Hi, I merged this patch after fixing some broken format. Could you please check your email configuration? Thanks, On 11/07, Fan Li wrote: > In current version, after scan_free_nid_bits, the scan is over if > nid_cnt[FREE_NID] != 0. > In most cases, there are still free nids in the free list

Re: [ata_scsi_offline_dev] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:238

Linus, > But it does seem to be a new regression in 4.14, caused by commit > 8a97712e5314 ("scsi: make 'state' device attribute pollable"), because > that's what added the sysfs_notify() call to scsi_device_set_state(), > which made that spinlock be a problem. > > That commit came in through the

Re: [ata_scsi_offline_dev] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:238

Linus, > But it does seem to be a new regression in 4.14, caused by commit > 8a97712e5314 ("scsi: make 'state' device attribute pollable"), because > that's what added the sysfs_notify() call to scsi_device_set_state(), > which made that spinlock be a problem. > > That commit came in through the

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

On Mon, Nov 06, 2017 at 07:01:58PM -0500, Boris Lukashev wrote: > On Mon, Nov 6, 2017 at 6:39 PM, Serge E. Hallyn wrote: > > Quoting Boris Lukashev (blukas...@sempervictus.com): > >> On Mon, Nov 6, 2017 at 5:14 PM, Serge E. Hallyn wrote: > >> > Quoting Daniel

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

On Mon, Nov 06, 2017 at 07:01:58PM -0500, Boris Lukashev wrote: > On Mon, Nov 6, 2017 at 6:39 PM, Serge E. Hallyn wrote: > > Quoting Boris Lukashev (blukas...@sempervictus.com): > >> On Mon, Nov 6, 2017 at 5:14 PM, Serge E. Hallyn wrote: > >> > Quoting Daniel Micay (danielmi...@gmail.com): > >>

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

On 11/07, Yunlong Song wrote: > Because I find that some out-of-free problem is caused by the failure > of get victim target. For example, chao has pointed out that he has > found out a bug when adding this bug_on last week. That's NOT what I asked. Why not checking FG_GC all the time like this?

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

On 11/07, Yunlong Song wrote: > Because I find that some out-of-free problem is caused by the failure > of get victim target. For example, chao has pointed out that he has > found out a bug when adding this bug_on last week. That's NOT what I asked. Why not checking FG_GC all the time like this?

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

On Mon, Nov 06, 2017 at 09:16:03PM -0500, Daniel Micay wrote: > 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

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

On Mon, Nov 06, 2017 at 09:16:03PM -0500, Daniel Micay wrote: > 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

Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng

Hi Jason, On 6 November 2017 at 07:57, Jason Gunthorpe wrote: > On Sun, Nov 05, 2017 at 01:05:06PM +0200, Jarkko Sakkinen wrote: > >> I asked to create a series for a reason. Now this doesn't apply because I >> don't have an ancestor in my git history. > > It would be unusual for

Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng

Hi Jason, On 6 November 2017 at 07:57, Jason Gunthorpe wrote: > On Sun, Nov 05, 2017 at 01:05:06PM +0200, Jarkko Sakkinen wrote: > >> I asked to create a series for a reason. Now this doesn't apply because I >> don't have an ancestor in my git history. > > It would be unusual for me to put your

Re: [PATCH 3.16 153/294] dm: convert DM printk macros to pr_ macros

On Mon, 2017-11-06 at 23:03 +, Ben Hutchings wrote: > 3.16.50-rc1 review patch. If anyone has any objections, please let me know. Why include this? It's a simplification, not a bug fix. > -- > > From: Joe Perches > > commit

Re: [PATCH 3.16 153/294] dm: convert DM printk macros to pr_ macros

On Mon, 2017-11-06 at 23:03 +, Ben Hutchings wrote: > 3.16.50-rc1 review patch. If anyone has any objections, please let me know. Why include this? It's a simplification, not a bug fix. > -- > > From: Joe Perches > > commit d2c3c8dcb5987b8352e82089c79a41b6e17e28d2

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

Because I find that some out-of-free problem is caused by the failure of get victim target. For example, chao has pointed out that he has found out a bug when adding this bug_on last week. On 2017/11/7 10:40, Jaegeuk Kim wrote: On 11/06, Jaegeuk Kim wrote: On 11/06, Yunlong Song wrote: Agree.

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

Because I find that some out-of-free problem is caused by the failure of get victim target. For example, chao has pointed out that he has found out a bug when adding this bug_on last week. On 2017/11/7 10:40, Jaegeuk Kim wrote: On 11/06, Jaegeuk Kim wrote: On 11/06, Yunlong Song wrote: Agree.

Re: AXP803 I2C support / AXP devicetree-bindings

On Tue, Nov 7, 2017 at 6:39 AM, Martin Blumenstingl wrote: > Hello, > > recently I discovered that there are some X-Powers AXP chips that > support both, Allwinner's own "RSB" as well as the I2C ("TWSI" in the > datasheet) busses. > > one chip that supports

Re: AXP803 I2C support / AXP devicetree-bindings

On Tue, Nov 7, 2017 at 6:39 AM, Martin Blumenstingl wrote: > Hello, > > recently I discovered that there are some X-Powers AXP chips that > support both, Allwinner's own "RSB" as well as the I2C ("TWSI" in the > datasheet) busses. > > one chip that supports both interfaces is the AXP803 > the

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

I test it in an old kernel and find it hangs in gc process, maybe it is a bug of old kernel. On 2017/11/7 10:49, Jaegeuk Kim wrote: On 11/07, Yunlong Song wrote: 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

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

I test it in an old kernel and find it hangs in gc process, maybe it is a bug of old kernel. On 2017/11/7 10:49, Jaegeuk Kim wrote: On 11/07, Yunlong Song wrote: 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

hello dear

I have the feeling that this piece of email will reach you in a perfect state of mind and in a better healthy condition, Despite we just know each other through internet, but understand that internet is like a global connective one village. My name is Miss Makena Jelani. I am 21 years old, I am

hello dear

I have the feeling that this piece of email will reach you in a perfect state of mind and in a better healthy condition, Despite we just know each other through internet, but understand that internet is like a global connective one village. My name is Miss Makena Jelani. I am 21 years old, I am

[PATCH] slub: Fix sysfs duplicate filename creation when slub_debug=O

From: Miles Chen When slub_debug=O is set. It is possible to clear debug flags for an "unmergeable" slab cache in kmem_cache_open(). It makes the "unmergeable" cache became "mergeable" in sysfs_slab_add(). These caches will generate their "unique IDs" by

[PATCH] slub: Fix sysfs duplicate filename creation when slub_debug=O

From: Miles Chen When slub_debug=O is set. It is possible to clear debug flags for an "unmergeable" slab cache in kmem_cache_open(). It makes the "unmergeable" cache became "mergeable" in sysfs_slab_add(). These caches will generate their "unique IDs" by create_unique_id(), but it is possible

[f2fs-dev] [PATCH] f2fs: keep scanning until enough free nids are acquired

In current version, after scan_free_nid_bits, the scan is over if nid_cnt[FREE_NID] != 0. In most cases, there are still free nids in the free list during the scan, and scan_free_nid_bits usually can't increase nid_cnt[FREE_NID]. It causes that __build_free_nids is called many times without

[f2fs-dev] [PATCH] f2fs: keep scanning until enough free nids are acquired

In current version, after scan_free_nid_bits, the scan is over if nid_cnt[FREE_NID] != 0. In most cases, there are still free nids in the free list during the scan, and scan_free_nid_bits usually can't increase nid_cnt[FREE_NID]. It causes that __build_free_nids is called many times without

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

On Tue, Nov 07, 2017 at 02:40:37AM +, Mathieu Desnoyers wrote: > - 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,

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

On Tue, Nov 07, 2017 at 02:40:37AM +, Mathieu Desnoyers wrote: > - 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,

Re: [PATCH 1/3] iommu/vt-d: Missing checks for pasid tables if allocation fails

Hi, On 11/07/2017 04:13 AM, Alex Williamson wrote: > On Thu, 19 Oct 2017 08:39:14 +0800 > Lu Baolu wrote: > >> intel_svm_alloc_pasid_tables() might return an error but never be >> checked by the callers. Later when intel_svm_bind_mm() is called, >> there are no checks

Re: [PATCH 1/3] iommu/vt-d: Missing checks for pasid tables if allocation fails

Hi, On 11/07/2017 04:13 AM, Alex Williamson wrote: > On Thu, 19 Oct 2017 08:39:14 +0800 > Lu Baolu wrote: > >> intel_svm_alloc_pasid_tables() might return an error but never be >> checked by the callers. Later when intel_svm_bind_mm() is called, >> there are no checks for valid pasid tables

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

On 11/07, Yunlong Song wrote: > 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

[PATCH] ARM: dts: add phy-reset property for rk3066a-rayeager emac

The ethernet phy of rk3066a-rayeager has a reset pin, it controlled by GPIO1_D6, this pin should be pull down then pull up to reset the phy. Add a phy-reset property in emac, make the phy can be reset when emac power on. Signed-off-by: Chris Zhong ---

[PATCH] ARM: dts: add phy-reset property for rk3066a-rayeager emac

The ethernet phy of rk3066a-rayeager has a reset pin, it controlled by GPIO1_D6, this pin should be pull down then pull up to reset the phy. Add a phy-reset property in emac, make the phy can be reset when emac power on. Signed-off-by: Chris Zhong --- arch/arm/boot/dts/rk3066a-rayeager.dts | 2

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

On 11/07, Yunlong Song wrote: > 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

Re: [PATCH for-next 2/4] RDMA/hns: Add IOMMU enable support in hip08

On 2017/11/1 20:26, Robin Murphy wrote: > On 01/11/17 07:46, Wei Hu (Xavier) wrote: >> >> On 2017/10/12 20:59, Robin Murphy wrote: >>> On 12/10/17 13:31, Wei Hu (Xavier) wrote: On 2017/10/1 0:10, Leon Romanovsky wrote: > On Sat, Sep 30, 2017 at 05:28:59PM +0800, Wei Hu (Xavier) wrote:

Re: [PATCH for-next 2/4] RDMA/hns: Add IOMMU enable support in hip08

On 2017/11/1 20:26, Robin Murphy wrote: > On 01/11/17 07:46, Wei Hu (Xavier) wrote: >> >> On 2017/10/12 20:59, Robin Murphy wrote: >>> On 12/10/17 13:31, Wei Hu (Xavier) wrote: On 2017/10/1 0:10, Leon Romanovsky wrote: > On Sat, Sep 30, 2017 at 05:28:59PM +0800, Wei Hu (Xavier) wrote:

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

On 2017/11/7 10:24, Jaegeuk Kim wrote: > 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

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

On 2017/11/7 10:24, Jaegeuk Kim wrote: > 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

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