Re: [PATCH v3] arm64: v8.4: Support for new floating point multiplication instructions

On Fri, Jan 05, 2018 at 09:22:54AM +0800, gengdongjiu wrote: > Hi will/catalin > > On 2017/12/13 18:09, Suzuki K Poulose wrote: > > On 13/12/17 10:13, Dongjiu Geng wrote: > >> ARM v8.4 extensions add new neon instructions for performing a > >> multiplication of each FP16 element of one vector

Re: [PATCH v3] arm64: v8.4: Support for new floating point multiplication instructions

On Fri, Jan 05, 2018 at 09:22:54AM +0800, gengdongjiu wrote: > Hi will/catalin > > On 2017/12/13 18:09, Suzuki K Poulose wrote: > > On 13/12/17 10:13, Dongjiu Geng wrote: > >> ARM v8.4 extensions add new neon instructions for performing a > >> multiplication of each FP16 element of one vector

Re: [PATCH 4.4 00/37] 4.4.110-stable review

On Thu, Jan 04, 2018 at 03:00:29PM -0700, Shuah Khan wrote: > On 01/03/2018 01:11 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.110 release. > > There are 37 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.4 00/37] 4.4.110-stable review

On Thu, Jan 04, 2018 at 03:00:29PM -0700, Shuah Khan wrote: > On 01/03/2018 01:11 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.110 release. > > There are 37 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.14 00/14] 4.14.12-stable review

On Thu, Jan 04, 2018 at 04:12:31PM -0800, Kevin Hilman wrote: > kernelci.org bot writes: > > > stable-rc/linux-4.14.y boot: 118 boots: 4 failed, 113 passed with 1 offline > > (v4.14.11-15-g732141e47ee6) > > > > Full Boot Summary: > >

Re: [PATCH 4.14 00/14] 4.14.12-stable review

On Thu, Jan 04, 2018 at 04:12:31PM -0800, Kevin Hilman wrote: > kernelci.org bot writes: > > > stable-rc/linux-4.14.y boot: 118 boots: 4 failed, 113 passed with 1 offline > > (v4.14.11-15-g732141e47ee6) > > > > Full Boot Summary: > >

Re: [PATCH] tty: fix data race in n_tty_receive_buf_common

Hi Alan, Can you make that code available otherwise it's impossible to see what the problem might be.   https://source.codeaurora.org/quic/la/kernel/msm-4.9/tree/drivers/tty/serial?h=msm-4.9  As discussed , there not seems a problem as we are getting print request even when port seems to

Re: [PATCH] tty: fix data race in n_tty_receive_buf_common

Hi Alan, Can you make that code available otherwise it's impossible to see what the problem might be.   https://source.codeaurora.org/quic/la/kernel/msm-4.9/tree/drivers/tty/serial?h=msm-4.9  As discussed , there not seems a problem as we are getting print request even when port seems to

Crypto Fixes for 4.15

Hi Linus: This push fixes the following issues: - Racy use of ctx->rcvused in af_alg. - algif_aead crash in chacha20poly1305. - Freeing bogus pointer in pcrypt. - Build error on MIPS in mpi. - Memory leak in inside-secure. - Memory overwrite in inside-secure. - NULL pointer dereference in

Crypto Fixes for 4.15

Hi Linus: This push fixes the following issues: - Racy use of ctx->rcvused in af_alg. - algif_aead crash in chacha20poly1305. - Freeing bogus pointer in pcrypt. - Build error on MIPS in mpi. - Memory leak in inside-secure. - Memory overwrite in inside-secure. - NULL pointer dereference in

Re: [GIT PULL 2/3] SOC: Keystone SOC update for 4.16

On Wed, Dec 27, 2017 at 06:07:51PM -0800, Santosh Shilimkar wrote: > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) > > are available in the git repository at: > >

Re: [GIT PULL] arm64: dts: uniphier: UniPhier DT updates (64bit) for v4.16

On Fri, Dec 29, 2017 at 10:35:38PM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Here are UniPhier DT (64bit) updates for the v4.16 merge window. > Please pull! > > > The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36: > > Linux 4.15-rc3 (2017-12-10 17:56:26

Re: [GIT PULL 2/3] SOC: Keystone SOC update for 4.16

On Wed, Dec 27, 2017 at 06:07:51PM -0800, Santosh Shilimkar wrote: > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) > > are available in the git repository at: > >

Re: [GIT PULL] arm64: dts: uniphier: UniPhier DT updates (64bit) for v4.16

On Fri, Dec 29, 2017 at 10:35:38PM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Here are UniPhier DT (64bit) updates for the v4.16 merge window. > Please pull! > > > The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36: > > Linux 4.15-rc3 (2017-12-10 17:56:26

Re: [GIT PULL] ARM: at91: drivers for 4.16

On Sun, Dec 31, 2017 at 04:34:42PM +0100, Alexandre Belloni wrote: > Arnd, Olof, > > A single harmless change for this pull request. I hope you'll enjoy this > New Year's Eve. > > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26

Re: [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.16

Hi! On Fri, Dec 29, 2017 at 10:32:24PM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Here are UniPhier DT (32bit) updates for the v4.16 merge window. > Please pull! > > > The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36: > > Linux 4.15-rc3 (2017-12-10

Re: [GIT PULL] ARM: at91: drivers for 4.16

On Sun, Dec 31, 2017 at 04:34:42PM +0100, Alexandre Belloni wrote: > Arnd, Olof, > > A single harmless change for this pull request. I hope you'll enjoy this > New Year's Eve. > > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26

Re: [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.16

Hi! On Fri, Dec 29, 2017 at 10:32:24PM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Here are UniPhier DT (32bit) updates for the v4.16 merge window. > Please pull! > > > The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36: > > Linux 4.15-rc3 (2017-12-10

Re: [GIT PULL 3/3] ARM: Keystone config update for 4.16

On Wed, Dec 27, 2017 at 06:07:52PM -0800, Santosh Shilimkar wrote: > Also had patch to sync up multi-v7 config but because of conflicts > in next, have to drop it. Will send that post merge window separately > > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > >

Re: [GIT PULL] ARM: at91: DT for 4.16

On Sun, Dec 31, 2017 at 04:11:27PM +0100, Alexandre Belloni wrote: > Arnd, Olof, > > This is the at91 DT pull request. The bulk of it is the switch to the > new TCB bindings that were acked a long time ago. These changes are > compatible with the current driver and taking them now will allow for

Re: [GIT PULL 3/3] ARM: Keystone config update for 4.16

On Wed, Dec 27, 2017 at 06:07:52PM -0800, Santosh Shilimkar wrote: > Also had patch to sync up multi-v7 config but because of conflicts > in next, have to drop it. Will send that post merge window separately > > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > >

Re: [GIT PULL] ARM: at91: DT for 4.16

On Sun, Dec 31, 2017 at 04:11:27PM +0100, Alexandre Belloni wrote: > Arnd, Olof, > > This is the at91 DT pull request. The bulk of it is the switch to the > new TCB bindings that were acked a long time ago. These changes are > compatible with the current driver and taking them now will allow for

Re: [GIT PULL 1/3] ARM: Keystone DTS for 4.16

On Wed, Dec 27, 2017 at 06:07:50PM -0800, Santosh Shilimkar wrote: > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) > > are available in the git repository at: > >

Re: [GIT PULL 1/3] ARM: Keystone DTS for 4.16

On Wed, Dec 27, 2017 at 06:07:50PM -0800, Santosh Shilimkar wrote: > The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: > > Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) > > are available in the git repository at: > >

[PATCH V3] nvme-pci: fix NULL pointer reference in nvme_alloc_ns

When the io queues setup or tagset allocation failed, ctrl.tagset is NULL. But the scan work will still be queued and executed, then panic comes up due to NULL pointer reference of ctrl.tagset. To fix this, add a new ctrl state NVME_CTRL_ADMIN_ONLY to inidcate only admin queue is live. When non

[PATCH V3] nvme-pci: fix NULL pointer reference in nvme_alloc_ns

When the io queues setup or tagset allocation failed, ctrl.tagset is NULL. But the scan work will still be queued and executed, then panic comes up due to NULL pointer reference of ctrl.tagset. To fix this, add a new ctrl state NVME_CTRL_ADMIN_ONLY to inidcate only admin queue is live. When non

Re: [PATCH net-next] net: tracepoint: adding new tracepoint arguments in inet_sock_set_state

> On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote: > > sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments. > Then we can conveniently use these two arguments to do the filter. > > Suggested-by: Brendan Gregg > Signed-off-by:

Re: [PATCH net-next] net: tracepoint: adding new tracepoint arguments in inet_sock_set_state

> On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote: > > sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments. > Then we can conveniently use these two arguments to do the filter. > > Suggested-by: Brendan Gregg > Signed-off-by: Yafang Shao > --- > include/trace/events/sock.h |

[PATCH -next] um: vector: fix missing unlock on error in vector_net_open()

Add the missing unlock before return from function vector_net_open() in the error handling case. Fixes: ad1f62ab2bd4 ("High Performance UML Vector Network Driver") Signed-off-by: Wei Yongjun --- arch/um/drivers/vector_kern.c | 4 +++- 1 file changed, 3 insertions(+), 1

[PATCH -next] um: vector: fix missing unlock on error in vector_net_open()

Add the missing unlock before return from function vector_net_open() in the error handling case. Fixes: ad1f62ab2bd4 ("High Performance UML Vector Network Driver") Signed-off-by: Wei Yongjun --- arch/um/drivers/vector_kern.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: Avoid speculative indirect calls in kernel

On Thu, Jan 04, 2018 at 10:57:19PM -0800, Dave Hansen wrote: > On 01/04/2018 10:49 PM, Willy Tarreau wrote: > > On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: > >> On Thu, 4 Jan 2018, Jon Masters wrote: > >>> P.S. I've an internal document where I've been tracking "nice to haves"

Re: Avoid speculative indirect calls in kernel

On Thu, Jan 04, 2018 at 10:57:19PM -0800, Dave Hansen wrote: > On 01/04/2018 10:49 PM, Willy Tarreau wrote: > > On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: > >> On Thu, 4 Jan 2018, Jon Masters wrote: > >>> P.S. I've an internal document where I've been tracking "nice to haves"

Re: [PATCH] of: Use SPDX license tag for DT files

On Fri, Jan 5, 2018 at 12:05 AM, Rob Herring wrote: > Convert remaining DT files to use SPDX-License-Identifier tags. > > Cc: Benjamin Herrenschmidt > Cc: Guennadi Liakhovetski > Cc: Paul Mackerras > Cc:

Re: [PATCH] of: Use SPDX license tag for DT files

On Fri, Jan 5, 2018 at 12:05 AM, Rob Herring wrote: > Convert remaining DT files to use SPDX-License-Identifier tags. > > Cc: Benjamin Herrenschmidt > Cc: Guennadi Liakhovetski > Cc: Paul Mackerras > Cc: Pantelis Antoniou > Signed-off-by: Rob Herring > --- > drivers/of/Kconfig

Re: [f2fs-dev] [PATCH 1/2] f2fs: show precise # of blocks that user/root can use

NACK man statfs shows: struct statfs { ... fsblkcnt_t f_bfree; /* free blocks in fs */ fsblkcnt_t f_bavail; /* free blocks available to unprivileged user */ ... } f_bfree is free blocks in fs, so buf->bfree should be buf->f_bfree =

Re: [f2fs-dev] [PATCH 1/2] f2fs: show precise # of blocks that user/root can use

NACK man statfs shows: struct statfs { ... fsblkcnt_t f_bfree; /* free blocks in fs */ fsblkcnt_t f_bavail; /* free blocks available to unprivileged user */ ... } f_bfree is free blocks in fs, so buf->bfree should be buf->f_bfree =

Re: [PATCH] [v3] x86/doc: add PTI description

On 01/04/18 21:38, Dave Hansen wrote: > +Page Table Management > += > + > +When PTI is enabled, the kernel manages two sets of page tables. > +The first set is very similar to the single set which is present in > +kernels without PTI. This includes a complete mapping of

Re: [PATCH] [v3] x86/doc: add PTI description

On 01/04/18 21:38, Dave Hansen wrote: > +Page Table Management > += > + > +When PTI is enabled, the kernel manages two sets of page tables. > +The first set is very similar to the single set which is present in > +kernels without PTI. This includes a complete mapping of

Re: Avoid speculative indirect calls in kernel

On 01/04/2018 10:49 PM, Willy Tarreau wrote: > On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: >> On Thu, 4 Jan 2018, Jon Masters wrote: >>> P.S. I've an internal document where I've been tracking "nice to haves" >>> for later, and one of them is whether it makes sense to tag

Re: Avoid speculative indirect calls in kernel

On 01/04/2018 10:49 PM, Willy Tarreau wrote: > On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: >> On Thu, 4 Jan 2018, Jon Masters wrote: >>> P.S. I've an internal document where I've been tracking "nice to haves" >>> for later, and one of them is whether it makes sense to tag

Re: Avoid speculative indirect calls in kernel

On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: > On Thu, 4 Jan 2018, Jon Masters wrote: > > P.S. I've an internal document where I've been tracking "nice to haves" > > for later, and one of them is whether it makes sense to tag binaries as > > "trusted" (e.g. extended attribute,

Re: Avoid speculative indirect calls in kernel

On Fri, Jan 05, 2018 at 01:54:13AM +0100, Thomas Gleixner wrote: > On Thu, 4 Jan 2018, Jon Masters wrote: > > P.S. I've an internal document where I've been tracking "nice to haves" > > for later, and one of them is whether it makes sense to tag binaries as > > "trusted" (e.g. extended attribute,

Re: [PATCH 04/12] pci-p2p: Clear ACS P2P flags for all client devices

On Thu, Jan 04, 2018 at 08:33:00PM -0700, Alex Williamson wrote: > On Thu, 4 Jan 2018 17:00:47 -0700 > Logan Gunthorpe wrote: > > > On 04/01/18 03:35 PM, Alex Williamson wrote: > > > Yep, flipping these ACS bits invalidates any IOMMU groups that depend > > > on the isolation

Re: [PATCH 04/12] pci-p2p: Clear ACS P2P flags for all client devices

On Thu, Jan 04, 2018 at 08:33:00PM -0700, Alex Williamson wrote: > On Thu, 4 Jan 2018 17:00:47 -0700 > Logan Gunthorpe wrote: > > > On 04/01/18 03:35 PM, Alex Williamson wrote: > > > Yep, flipping these ACS bits invalidates any IOMMU groups that depend > > > on the isolation of that downstream

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

On Thu, 2018-01-04 at 16:07 -0800, Matthew Wilcox wrote: > On Thu, Jan 04, 2018 at 03:47:32PM -0800, Paul E. McKenney wrote: > > I was under the impression that typeof did not actually evaluate its > > argument, but rather only returned its type. And there are a few macros > > with this pattern

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

On Thu, 2018-01-04 at 16:07 -0800, Matthew Wilcox wrote: > On Thu, Jan 04, 2018 at 03:47:32PM -0800, Paul E. McKenney wrote: > > I was under the impression that typeof did not actually evaluate its > > argument, but rather only returned its type. And there are a few macros > > with this pattern

Re: mmotm 2018-01-04-16-19 uploaded

On 01/05/2018 05:50 AM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2018-01-04-16-19 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of

Re: mmotm 2018-01-04-16-19 uploaded

On 01/05/2018 05:50 AM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2018-01-04-16-19 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of

[PATCH net-next] net: tracepoint: adding new tracepoint arguments in inet_sock_set_state

sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments. Then we can conveniently use these two arguments to do the filter. Suggested-by: Brendan Gregg Signed-off-by: Yafang Shao --- include/trace/events/sock.h | 24

[PATCH net-next] net: tracepoint: adding new tracepoint arguments in inet_sock_set_state

sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments. Then we can conveniently use these two arguments to do the filter. Suggested-by: Brendan Gregg Signed-off-by: Yafang Shao --- include/trace/events/sock.h | 24 ++-- net/ipv4/af_inet.c | 6

Re: [Ocfs2-devel] [PATCH v2] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

Hi Andrew, Happy new year. Could you help to pick up this patch, which is used to fix a old patch 1cce4df04f37. If we have not this patch, some multiple node test cases will trigger softlockup problems, also make HA communication daemon (e.g. corosync) timeout and the node will has to be

Re: [Ocfs2-devel] [PATCH v2] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

Hi Andrew, Happy new year. Could you help to pick up this patch, which is used to fix a old patch 1cce4df04f37. If we have not this patch, some multiple node test cases will trigger softlockup problems, also make HA communication daemon (e.g. corosync) timeout and the node will has to be

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

On 01/04/2018 10:16 PM, Yisheng Xie wrote: > BTW, we have just reported a bug caused by kaiser[1], which looks like > caused by SMEP. Could you please help to have a look? > > [1] https://lkml.org/lkml/2018/1/5/3 Please report that to your kernel vendor. Your EFI page tables have the NX bit set

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

On 01/04/2018 10:16 PM, Yisheng Xie wrote: > BTW, we have just reported a bug caused by kaiser[1], which looks like > caused by SMEP. Could you please help to have a look? > > [1] https://lkml.org/lkml/2018/1/5/3 Please report that to your kernel vendor. Your EFI page tables have the NX bit set

[PATCH] f2fs: implement cgroup writeback supprot

Cgroup writeback requires explicit support from the filesystem. f2fs's data and node writeback IOs go through __write_data_page, which sets fio for submiting IOs. So, we add io_wbc for fio, associate bios with blkcg by invoking wbc_init_bio() and account IOs issuing by wbc_account_io(). In

[PATCH] f2fs: implement cgroup writeback supprot

Cgroup writeback requires explicit support from the filesystem. f2fs's data and node writeback IOs go through __write_data_page, which sets fio for submiting IOs. So, we add io_wbc for fio, associate bios with blkcg by invoking wbc_init_bio() and account IOs issuing by wbc_account_io(). In

Re: [linux-sunxi] Re: [PATCH 06/11] dt-bindings: display: sun4i-drm: Add A83T HDMI pipeline

Hi, Dne petek, 05. januar 2018 ob 03:49:09 CET je Icenowy Zheng napisal(a): > 于 2018年1月5日 GMT+08:00 上午2:52:10, Maxime Ripard 写到: > >On Wed, Jan 03, 2018 at 10:32:26PM +0100, Jernej Škrabec wrote: > >> Hi Rob, > >> > >> Dne sreda, 03. januar 2018 ob 21:21:54

Re: [linux-sunxi] Re: [PATCH 06/11] dt-bindings: display: sun4i-drm: Add A83T HDMI pipeline

Hi, Dne petek, 05. januar 2018 ob 03:49:09 CET je Icenowy Zheng napisal(a): > 于 2018年1月5日 GMT+08:00 上午2:52:10, Maxime Ripard 写到: > >On Wed, Jan 03, 2018 at 10:32:26PM +0100, Jernej Škrabec wrote: > >> Hi Rob, > >> > >> Dne sreda, 03. januar 2018 ob 21:21:54 CET je Rob Herring napisal(a): > >> >

[PATCH] f2fs: add resgid and resuid to reserve root blocks

This patch adds mount options to reserve some blocks via resgid=%u,resuid=%u. It only activates with reserve_root=%u. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 26 -- fs/f2fs/super.c | 46 -- 2 files

[PATCH] f2fs: add resgid and resuid to reserve root blocks

This patch adds mount options to reserve some blocks via resgid=%u,resuid=%u. It only activates with reserve_root=%u. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 26 -- fs/f2fs/super.c | 46 -- 2 files changed, 68

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

Hi Dave, On 2018/1/5 13:18, Dave Hansen wrote: > On 01/04/2018 08:16 PM, Yisheng Xie wrote: >>> === Page Table Poisoning === >>> >>> KAISER has two copies of the page tables: one for the kernel and >>> one for when running in userspace. >> >> So, we have 2 page table, thinking about this case:

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

Hi Dave, On 2018/1/5 13:18, Dave Hansen wrote: > On 01/04/2018 08:16 PM, Yisheng Xie wrote: >>> === Page Table Poisoning === >>> >>> KAISER has two copies of the page tables: one for the kernel and >>> one for when running in userspace. >> >> So, we have 2 page table, thinking about this case:

[PATCH v2] mm/fadvise: discard partial page if endbyte is also EOF

From: shidao.ytt During our recent testing with fadvise(FADV_DONTNEED), we find that if given offset/length is not page-aligned, the last page will not be discarded. The tool we use is vmtouch (https://hoytech.com/vmtouch/), we map a 10KB-sized file into memory and

[PATCH v2] mm/fadvise: discard partial page if endbyte is also EOF

From: shidao.ytt During our recent testing with fadvise(FADV_DONTNEED), we find that if given offset/length is not page-aligned, the last page will not be discarded. The tool we use is vmtouch (https://hoytech.com/vmtouch/), we map a 10KB-sized file into memory and then try to run this tool to

Re: [PATCH 0/7] IBRS patch series

* Linus Torvalds: > On Thu, Jan 4, 2018 at 9:56 AM, Tim Chen wrote: >> >> Speculation on Skylake and later requires these patches ("dynamic IBRS") >> be used instead of retpoline[1]. > > Can somebody explain this part? > > I was assuming that retpoline would work

Re: [PATCH 0/7] IBRS patch series

* Linus Torvalds: > On Thu, Jan 4, 2018 at 9:56 AM, Tim Chen wrote: >> >> Speculation on Skylake and later requires these patches ("dynamic IBRS") >> be used instead of retpoline[1]. > > Can somebody explain this part? > > I was assuming that retpoline would work around this issue on all uarchs.

Re: [PATCH] driver: input :touchscreen :Modify Raydium Firmware update input file

Hi Jeffrey, On Thu, Dec 21, 2017 at 09:51:22PM +0800, jeffrey.lin wrote: > Modify update firmware to accept alternative file name > > Signed-off-by: jeffrey.lin > --- > drivers/input/touchscreen/raydium_i2c_ts.c | 11 --- > 1 file changed, 8 insertions(+), 3

Re: [PATCH] driver: input :touchscreen :Modify Raydium Firmware update input file

Hi Jeffrey, On Thu, Dec 21, 2017 at 09:51:22PM +0800, jeffrey.lin wrote: > Modify update firmware to accept alternative file name > > Signed-off-by: jeffrey.lin > --- > drivers/input/touchscreen/raydium_i2c_ts.c | 11 --- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff

linux-next: Tree for Jan 5

Hi all, Changes since 20180104: The drm tree gained a conflict against the drm-intel-fixes tree. The akpm-current tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 6981 7369 files changed, 288333 insertions(+), 202735 deletions

linux-next: Tree for Jan 5

Hi all, Changes since 20180104: The drm tree gained a conflict against the drm-intel-fixes tree. The akpm-current tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 6981 7369 files changed, 288333 insertions(+), 202735 deletions

[PATCH] [v3] x86/doc: add PTI description

Changes from v2: * Update some wording * Minor typo and grammar fixes * Further clarify what INVPCID is. Changes from v1: * update kernel-parameters.txt to clarify that the pti= option is not just for disabling. Also describe what 'pti=auto' does and why * Add a note about the

[PATCH] [v3] x86/doc: add PTI description

Changes from v2: * Update some wording * Minor typo and grammar fixes * Further clarify what INVPCID is. Changes from v1: * update kernel-parameters.txt to clarify that the pti= option is not just for disabling. Also describe what 'pti=auto' does and why * Add a note about the

[RFC] selftests/x86: Add test_vsyscall

This tests that the vsyscall entries do what they're expected to do. It also confirms that attempts to read the vsyscall page behave as expected. If changes are made to the vsyscall code or its memory map handling, running this test in all three of vsyscall=none, vsyscall=emulate, and

[RFC] selftests/x86: Add test_vsyscall

This tests that the vsyscall entries do what they're expected to do. It also confirms that attempts to read the vsyscall page behave as expected. If changes are made to the vsyscall code or its memory map handling, running this test in all three of vsyscall=none, vsyscall=emulate, and

Re: [PATCH] nvme-pci: fix the timeout case when reset is ongoing

Hi Christoph Many thanks for your kindly response. On 01/04/2018 06:35 PM, Christoph Hellwig wrote: > On Wed, Jan 03, 2018 at 06:31:44AM +0800, Jianchao Wang wrote: >> NVME_CTRL_RESETTING used to indicate the range of nvme initializing >> strictly in fd634f41(nvme: merge probe_work and

Re: [PATCH] nvme-pci: fix the timeout case when reset is ongoing

Hi Christoph Many thanks for your kindly response. On 01/04/2018 06:35 PM, Christoph Hellwig wrote: > On Wed, Jan 03, 2018 at 06:31:44AM +0800, Jianchao Wang wrote: >> NVME_CTRL_RESETTING used to indicate the range of nvme initializing >> strictly in fd634f41(nvme: merge probe_work and

Re: [PATCH 4.4 00/37] 4.4.110-stable review

On Thu, Jan 4, 2018 at 12:43 PM, Andy Lutomirski wrote: > >> On Jan 4, 2018, at 12:29 PM, Linus Torvalds >> wrote: >> >>> On Thu, Jan 4, 2018 at 12:16 PM, Thomas Voegtle wrote: >>> >>> Attached a screenshot. >>> Is that useful?

Re: [PATCH 4.4 00/37] 4.4.110-stable review

On Thu, Jan 4, 2018 at 12:43 PM, Andy Lutomirski wrote: > >> On Jan 4, 2018, at 12:29 PM, Linus Torvalds >> wrote: >> >>> On Thu, Jan 4, 2018 at 12:16 PM, Thomas Voegtle wrote: >>> >>> Attached a screenshot. >>> Is that useful? Are there some debug options I can add? >> >> Not much of an oops,

Re: [PATCH] [v2] x86/doc: add PTI description

On 01/04/2018 05:43 PM, Hector Martin 'marcan' wrote: > On 2018-01-05 09:24, Dave Hansen wrote: >> +Not specifying this option nothing is equivalent to >> +pti=auto. > > -nothing Sure, will fix. >> +Page Table Isolation (pti, previously known as

Re: [PATCH] [v2] x86/doc: add PTI description

On 01/04/2018 05:43 PM, Hector Martin 'marcan' wrote: > On 2018-01-05 09:24, Dave Hansen wrote: >> +Not specifying this option nothing is equivalent to >> +pti=auto. > > -nothing Sure, will fix. >> +Page Table Isolation (pti, previously known as

Re: [PATCH V7 12/12] arm64: dts: add clocks for SC9860

On 5 January 2018 at 07:01, Arnd Bergmann wrote: > On Thu, Jan 4, 2018 at 10:34 PM, Arnd Bergmann wrote: >> On Thu, Dec 7, 2017 at 1:57 PM, Chunyan Zhang >> wrote: >>> Some clocks on SC9860 are in the same address area with syscon

Re: [PATCH V7 12/12] arm64: dts: add clocks for SC9860

On 5 January 2018 at 07:01, Arnd Bergmann wrote: > On Thu, Jan 4, 2018 at 10:34 PM, Arnd Bergmann wrote: >> On Thu, Dec 7, 2017 at 1:57 PM, Chunyan Zhang >> wrote: >>> Some clocks on SC9860 are in the same address area with syscon devices, >>> those are what have a property of 'sprd,syscon'

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

On 01/04/2018 08:16 PM, Yisheng Xie wrote: >> === Page Table Poisoning === >> >> KAISER has two copies of the page tables: one for the kernel and >> one for when running in userspace. > > So, we have 2 page table, thinking about this case: > If _ONE_ process includes _TWO_ threads, one run in

Re: [PATCH 05/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

On 01/04/2018 08:16 PM, Yisheng Xie wrote: >> === Page Table Poisoning === >> >> KAISER has two copies of the page tables: one for the kernel and >> one for when running in userspace. > > So, we have 2 page table, thinking about this case: > If _ONE_ process includes _TWO_ threads, one run in

[RFC] boot failed when enable KAISER/KPTI

I run the latest RHEL 7.2 with the KAISER/KPTI patch, and boot failed. ... [0.00] PM: Registered nosave memory: [mem 0x810-0x8ff] [0.00] PM: Registered nosave memory: [mem 0x910-0xfff] [0.00] PM: Registered nosave memory: [mem

[RFC] boot failed when enable KAISER/KPTI

I run the latest RHEL 7.2 with the KAISER/KPTI patch, and boot failed. ... [0.00] PM: Registered nosave memory: [mem 0x810-0x8ff] [0.00] PM: Registered nosave memory: [mem 0x910-0xfff] [0.00] PM: Registered nosave memory: [mem

Re: [PATCH 3/7] x86/enter: Use IBRS on syscall and interrupts

On 01/04/2018 08:51 PM, Andy Lutomirski wrote: > Do we need an arch_prctl() to enable IBRS for user mode? Eventually, once the dust settles. I think there's a spectrum of paranoia here, that is roughly (with increasing paranoia): 1. do nothing 2. do retpoline 3. do IBRS in kernel 4. do IBRS

Re: [PATCH 3/7] x86/enter: Use IBRS on syscall and interrupts

On 01/04/2018 08:51 PM, Andy Lutomirski wrote: > Do we need an arch_prctl() to enable IBRS for user mode? Eventually, once the dust settles. I think there's a spectrum of paranoia here, that is roughly (with increasing paranoia): 1. do nothing 2. do retpoline 3. do IBRS in kernel 4. do IBRS

Re: [PATCH 2/7] x86/enter: MACROS to set/clear IBRS

On 01/04/2018 08:54 PM, Andy Lutomirski wrote: > On Thu, Jan 4, 2018 at 2:23 PM, Dave Hansen wrote: >> On 01/04/2018 02:21 PM, Tim Chen wrote: Does this really have to live outside of arch/x86/entry/ ? >>> There are some inline C routines later in this file >>>

Re: [PATCH 2/7] x86/enter: MACROS to set/clear IBRS

On 01/04/2018 08:54 PM, Andy Lutomirski wrote: > On Thu, Jan 4, 2018 at 2:23 PM, Dave Hansen wrote: >> On 01/04/2018 02:21 PM, Tim Chen wrote: Does this really have to live outside of arch/x86/entry/ ? >>> There are some inline C routines later in this file >>> that will be needed by

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/migrate.c: In function 'migrate_misplaced_page': mm/migrate.c:1933:46: error: passing argument 2 of 'migrate_pages' from incompatible pointer type

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/migrate.c: In function 'migrate_misplaced_page': mm/migrate.c:1933:46: error: passing argument 2 of 'migrate_pages' from incompatible pointer type

Re: KASAN: slab-out-of-bounds Read in cap_inode_getsecurity

On Thu, Jan 04, 2018 at 08:58:02AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 71ee203389f7cb1c1927eab22b95baa01405791c > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: KASAN: slab-out-of-bounds Read in cap_inode_getsecurity

On Thu, Jan 04, 2018 at 08:58:02AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 71ee203389f7cb1c1927eab22b95baa01405791c > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: [PATCH 2/7] x86/enter: MACROS to set/clear IBRS

On Thu, Jan 4, 2018 at 2:23 PM, Dave Hansen wrote: > On 01/04/2018 02:21 PM, Tim Chen wrote: >>> Does this really have to live outside of arch/x86/entry/ ? >>> >> There are some inline C routines later in this file >> that will be needed by other functions. Want to

Re: [PATCH 2/7] x86/enter: MACROS to set/clear IBRS

On Thu, Jan 4, 2018 at 2:23 PM, Dave Hansen wrote: > On 01/04/2018 02:21 PM, Tim Chen wrote: >>> Does this really have to live outside of arch/x86/entry/ ? >>> >> There are some inline C routines later in this file >> that will be needed by other functions. Want to consolidate >> them in the

Re: [PATCH 3/7] x86/enter: Use IBRS on syscall and interrupts

On Thu, Jan 4, 2018 at 4:08 PM, Dave Hansen wrote: > On 01/04/2018 02:33 PM, Peter Zijlstra wrote: >> On Thu, Jan 04, 2018 at 09:56:44AM -0800, Tim Chen wrote: >>> Set IBRS upon kernel entrance via syscall and interrupts. Clear it >>> upon exit. >> >> So not only did we add

Re: [PATCH 3/7] x86/enter: Use IBRS on syscall and interrupts

On Thu, Jan 4, 2018 at 4:08 PM, Dave Hansen wrote: > On 01/04/2018 02:33 PM, Peter Zijlstra wrote: >> On Thu, Jan 04, 2018 at 09:56:44AM -0800, Tim Chen wrote: >>> Set IBRS upon kernel entrance via syscall and interrupts. Clear it >>> upon exit. >> >> So not only did we add a CR3 write, we're now

Re: [PATCH 06/12] IB/core: Add optional PCI P2P flag to rdma_rw_ctx_[init|destroy]()

On Thu, Jan 04, 2018 at 04:44:00PM -0700, Logan Gunthorpe wrote: > On 04/01/18 03:13 PM, Jason Gunthorpe wrote: > >On Thu, Jan 04, 2018 at 12:52:24PM -0700, Logan Gunthorpe wrote: > >>We tried things like this in an earlier iteration[1] which assumed the SG > >>was homogenous (all P2P or all

Re: [PATCH 06/12] IB/core: Add optional PCI P2P flag to rdma_rw_ctx_[init|destroy]()

On Thu, Jan 04, 2018 at 04:44:00PM -0700, Logan Gunthorpe wrote: > On 04/01/18 03:13 PM, Jason Gunthorpe wrote: > >On Thu, Jan 04, 2018 at 12:52:24PM -0700, Logan Gunthorpe wrote: > >>We tried things like this in an earlier iteration[1] which assumed the SG > >>was homogenous (all P2P or all

  1   2   3   4   5   6   7   8   9   10   >