Re: [ANNOUNCE] Git v2.16.0-rc0

On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder wrote: > Hi Bryan, > > Bryan Turner wrote: > >> Our test environment is still on Ubuntu 12.04 LTS (it's a long story, >> but one I doubt is unique to us), which means it's using OpenSSH 5.9. >> ssh -G was added in OpenSSH 6.8

Re: [ANNOUNCE] Git v2.16.0-rc0

On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder wrote: > Hi Bryan, > > Bryan Turner wrote: > >> Our test environment is still on Ubuntu 12.04 LTS (it's a long story, >> but one I doubt is unique to us), which means it's using OpenSSH 5.9. >> ssh -G was added in OpenSSH 6.8 [1], circa March 2015,

Re: [ANNOUNCE] Git v2.16.0-rc0

Hi, A few more notes. Bryan Turner wrote: > bturner@ubuntu:~$ ssh -V > OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8, OpenSSL 1.0.1f 6 Jan 2014 > > bturner@ubuntu:~$ ssh -G -p 7999 localhost > unknown option -- G > usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [...] > Is it

Re: [ANNOUNCE] Git v2.16.0-rc0

Hi, A few more notes. Bryan Turner wrote: > bturner@ubuntu:~$ ssh -V > OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8, OpenSSL 1.0.1f 6 Jan 2014 > > bturner@ubuntu:~$ ssh -G -p 7999 localhost > unknown option -- G > usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [...] > Is it

Re: [PATCH] PCI: exynos: remove the deprecated phy codes

On 01/03/2018 01:34 AM, Lorenzo Pieralisi wrote: > On Wed, Dec 27, 2017 at 06:43:27PM +0900, Jaehoon Chung wrote: >> pci-exynos had updated to use the PHY framework. >> (drivers/phy/samsung/phy-exynos-pcie.c) >> Removed the depreccated codes relevant to phy in pci-exynos.c. >> Instead, use the

Re: [PATCH] PCI: exynos: remove the deprecated phy codes

On 01/03/2018 01:34 AM, Lorenzo Pieralisi wrote: > On Wed, Dec 27, 2017 at 06:43:27PM +0900, Jaehoon Chung wrote: >> pci-exynos had updated to use the PHY framework. >> (drivers/phy/samsung/phy-exynos-pcie.c) >> Removed the depreccated codes relevant to phy in pci-exynos.c. >> Instead, use the

Re: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

On Wed, Jan 03, 2018 at 05:13:29AM +, Appana Durga Kedareswara Rao wrote: > Hi Vinod, > > Thanks for the review... > > > > >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: > > > >Fix title here too > > Sure will fix in v2... > > > > >BTW whats with LINUX tag

Re: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

On Wed, Jan 03, 2018 at 05:13:29AM +, Appana Durga Kedareswara Rao wrote: > Hi Vinod, > > Thanks for the review... > > > > >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: > > > >Fix title here too > > Sure will fix in v2... > > > > >BTW whats with LINUX tag

Re: [Ocfs2-devel] [PATCH v3 2/3] ocfs2: add ocfs2_overwrite_io function

Hi Alex, >>> > Hi Gang, > > On 2017/12/28 18:07, Gang He wrote: >> Add ocfs2_overwrite_io function, which is used to judge if >> overwrite allocated blocks, otherwise, the write will bring extra >> block allocation overhead. >> >> Signed-off-by: Gang He >> --- >>

[PATCH] ata_piix: constify pci_bits

pci_bits are not supposed to change at runtime. Functions pci_test_config_bits() working with const 'struct pci_bits'. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/ata/ata_piix.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [Ocfs2-devel] [PATCH v3 2/3] ocfs2: add ocfs2_overwrite_io function

Hi Alex, >>> > Hi Gang, > > On 2017/12/28 18:07, Gang He wrote: >> Add ocfs2_overwrite_io function, which is used to judge if >> overwrite allocated blocks, otherwise, the write will bring extra >> block allocation overhead. >> >> Signed-off-by: Gang He >> --- >> fs/ocfs2/extent_map.c | 45

[PATCH] ata_piix: constify pci_bits

pci_bits are not supposed to change at runtime. Functions pci_test_config_bits() working with const 'struct pci_bits'. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/ata/ata_piix.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

RE: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: > >Fix title here too Sure will fix in v2... > >BTW whats with LINUX tag in patches, pls drop them Ok will mention the Linux tag info in the cover letter patch from the next

RE: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: > >Fix title here too Sure will fix in v2... > >BTW whats with LINUX tag in patches, pls drop them Ok will mention the Linux tag info in the cover letter patch from the next

RE: [LINUX PATCH 2/4] dmaengine: xilinx_dma: Fix race condition in the driver for cdma

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:36PM +0530, Kedareswara rao Appana wrote: > >same issue for patch title here too Ok will fix in v2... > >> when hardware is idle we need to toggle the SG bit in the control >> register, inorder to update new value to

RE: [LINUX PATCH 2/4] dmaengine: xilinx_dma: Fix race condition in the driver for cdma

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:36PM +0530, Kedareswara rao Appana wrote: > >same issue for patch title here too Ok will fix in v2... > >> when hardware is idle we need to toggle the SG bit in the control >> register, inorder to update new value to

RE: [LINUX PATCH 1/4] dmaengine: xilinx_dma: Fix dma_get_slave_caps() API failures

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:35PM +0530, Kedareswara rao Appana wrote: > >Patch title should say what is does, not the cause/effect Sure will fix in v2... > >An apt title might be "populate dma caps properly" > >> When client driver uses

RE: [LINUX PATCH 1/4] dmaengine: xilinx_dma: Fix dma_get_slave_caps() API failures

Hi Vinod, Thanks for the review... > >On Thu, Dec 21, 2017 at 03:41:35PM +0530, Kedareswara rao Appana wrote: > >Patch title should say what is does, not the cause/effect Sure will fix in v2... > >An apt title might be "populate dma caps properly" > >> When client driver uses

Re: [ANNOUNCE] Git v2.16.0-rc0

Hi Bryan, Bryan Turner wrote: > Our test environment is still on Ubuntu 12.04 LTS (it's a long story, > but one I doubt is unique to us), which means it's using OpenSSH 5.9. > ssh -G was added in OpenSSH 6.8 [1], circa March 2015, which means the > "auto" detection "fails" and chooses "simple"

Re: [ANNOUNCE] Git v2.16.0-rc0

Hi Bryan, Bryan Turner wrote: > Our test environment is still on Ubuntu 12.04 LTS (it's a long story, > but one I doubt is unique to us), which means it's using OpenSSH 5.9. > ssh -G was added in OpenSSH 6.8 [1], circa March 2015, which means the > "auto" detection "fails" and chooses "simple"

Re: perf test BPF failing on 4.15.0-rc6

And please check if the kprobe created by $ perf probe -v SyS_epoll_wait works for the test program used by this testcase: #include #include #define NR_ITERS 100 static int epoll_wait_loop(void) { int i; /* Should fail NR_ITERS times */ for (i = 0; i < NR_ITERS;

Re: perf test BPF failing on 4.15.0-rc6

And please check if the kprobe created by $ perf probe -v SyS_epoll_wait works for the test program used by this testcase: #include #include #define NR_ITERS 100 static int epoll_wait_loop(void) { int i; /* Should fail NR_ITERS times */ for (i = 0; i < NR_ITERS;

Re: [PATCH v2 5/8] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver

On 01/02/2018 08:48 AM, Paul Cercueil wrote: Hi PrasannaKumar, Le mar. 2 janv. 2018 à 17:37, PrasannaKumar Muralidharan a écrit : Hi Paul, On 30 December 2017 at 19:21, Paul Cercueil wrote:  Also remove the watchdog platform_device from

Re: [PATCH v2 5/8] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver

On 01/02/2018 08:48 AM, Paul Cercueil wrote: Hi PrasannaKumar, Le mar. 2 janv. 2018 à 17:37, PrasannaKumar Muralidharan a écrit : Hi Paul, On 30 December 2017 at 19:21, Paul Cercueil wrote:  Also remove the watchdog platform_device from platform.c, since it  wasn't used anywhere anyway.  

Re: perf test BPF failing on 4.15.0-rc6

Unable to reproduce. In my kernel configuration, SyS_epoll_wait is not inlined at all. From the log you sent, it seems that all 3 instances are attached. This testcase should work if the last one (SyS_epoll_wait) get probed correctly. Could you please have a look if the 3rd kprobe event

Re: perf test BPF failing on 4.15.0-rc6

Unable to reproduce. In my kernel configuration, SyS_epoll_wait is not inlined at all. From the log you sent, it seems that all 3 instances are attached. This testcase should work if the last one (SyS_epoll_wait) get probed correctly. Could you please have a look if the 3rd kprobe event

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Wed, 2018-01-03 at 14:16 +1100, Dave Chinner wrote: > On Tue, Jan 02, 2018 at 09:52:03PM -0500, Mimi Zohar wrote: > > On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > > > [might as well cc linux-xfs] > > > > > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > >

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Wed, 2018-01-03 at 14:16 +1100, Dave Chinner wrote: > On Tue, Jan 02, 2018 at 09:52:03PM -0500, Mimi Zohar wrote: > > On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > > > [might as well cc linux-xfs] > > > > > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > >

Re: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: Fix title here too BTW whats with LINUX tag in patches, pls drop them > This patch fixes the below sparse warning in the driver > drivers/dma/xilinx/xilinx_dma.c: In function > ‘xilinx_vdma_dma_prep_interleaved’: >

Re: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: Fix title here too BTW whats with LINUX tag in patches, pls drop them > This patch fixes the below sparse warning in the driver > drivers/dma/xilinx/xilinx_dma.c: In function > ‘xilinx_vdma_dma_prep_interleaved’: >

Re: [LINUX PATCH 2/4] dmaengine: xilinx_dma: Fix race condition in the driver for cdma

On Thu, Dec 21, 2017 at 03:41:36PM +0530, Kedareswara rao Appana wrote: same issue for patch title here too > when hardware is idle we need to toggle the SG bit > in the control register, inorder to update new value to the > current descriptor register other wise undefined > results will occur.

Re: [LINUX PATCH 2/4] dmaengine: xilinx_dma: Fix race condition in the driver for cdma

On Thu, Dec 21, 2017 at 03:41:36PM +0530, Kedareswara rao Appana wrote: same issue for patch title here too > when hardware is idle we need to toggle the SG bit > in the control register, inorder to update new value to the > current descriptor register other wise undefined > results will occur.

Re: [PATCH 01/13] powerpc/powernv: Introduce new PHB type for opencapi links

On 19/12/17 02:21, Frederic Barrat wrote: The NPU was already abstracted by opal as a virtual PHB for nvlink, but it helps to be able to differentiate between a nvlink or opencapi PHB, as it's not completely transparent to linux. In particular, PE assignment differs and we'll also need the

Re: [PATCH 01/13] powerpc/powernv: Introduce new PHB type for opencapi links

On 19/12/17 02:21, Frederic Barrat wrote: The NPU was already abstracted by opal as a virtual PHB for nvlink, but it helps to be able to differentiate between a nvlink or opencapi PHB, as it's not completely transparent to linux. In particular, PE assignment differs and we'll also need the

Re: [LINUX PATCH 1/4] dmaengine: xilinx_dma: Fix dma_get_slave_caps() API failures

On Thu, Dec 21, 2017 at 03:41:35PM +0530, Kedareswara rao Appana wrote: Patch title should say what is does, not the cause/effect An apt title might be "populate dma caps properly" > When client driver uses dma_get_slave_caps() api, > it checks for certain fields of dma_device struct >

Re: [LINUX PATCH 1/4] dmaengine: xilinx_dma: Fix dma_get_slave_caps() API failures

On Thu, Dec 21, 2017 at 03:41:35PM +0530, Kedareswara rao Appana wrote: Patch title should say what is does, not the cause/effect An apt title might be "populate dma caps properly" > When client driver uses dma_get_slave_caps() api, > it checks for certain fields of dma_device struct >

Re: dma_async_device_unregister called while 2 clients hold a reference

On Tue, Dec 26, 2017 at 10:37:13AM +0530, Rayagonda Kokatanur wrote: > Hi All, > > I am getting following error when I unload one of my dma client driver. > When I looked further into dmaengine.c file I found that the error is > because of WARN_ONCE in dma_async_device_unregister() api. > > Is

Re: dma_async_device_unregister called while 2 clients hold a reference

On Tue, Dec 26, 2017 at 10:37:13AM +0530, Rayagonda Kokatanur wrote: > Hi All, > > I am getting following error when I unload one of my dma client driver. > When I looked further into dmaengine.c file I found that the error is > because of WARN_ONCE in dma_async_device_unregister() api. > > Is

[PATCH] ARM: dts: imx6ul: remove unnecessary clocks for cpu-freq

Remove unnecessary clocks for cpu-freq driver to avoid confusion. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6ul.dtsi | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/arch/arm/boot/dts/imx6ul.dtsi b/arch/arm/boot/dts/imx6ul.dtsi index

[PATCH] ARM: dts: imx6ul: remove unnecessary clocks for cpu-freq

Remove unnecessary clocks for cpu-freq driver to avoid confusion. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6ul.dtsi | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/arch/arm/boot/dts/imx6ul.dtsi b/arch/arm/boot/dts/imx6ul.dtsi index 86b3251..fb06a9a 100644

Re: [PATCH] rpmsg: virtio_rpmsg_bus: fix rpmsg_probe() for virtio-mmio transport

Hi Bjorn, Ping? If possible please consider this fix for Linux-4.15-rcX Thanks, Anup

Re: [PATCH] rpmsg: virtio_rpmsg_bus: fix rpmsg_probe() for virtio-mmio transport

Hi Bjorn, Ping? If possible please consider this fix for Linux-4.15-rcX Thanks, Anup

Re: [ANNOUNCE] Git v2.16.0-rc0

On Thu, Dec 28, 2017 at 8:30 PM, Junio C Hamano wrote: > An early preview release Git v2.16.0-rc0 is now available for > testing at the usual places. It is comprised of 435 non-merge > commits since v2.15.0, contributed by 76 people, 22 of which are > new faces. > Brandon

Re: [ANNOUNCE] Git v2.16.0-rc0

On Thu, Dec 28, 2017 at 8:30 PM, Junio C Hamano wrote: > An early preview release Git v2.16.0-rc0 is now available for > testing at the usual places. It is comprised of 435 non-merge > commits since v2.15.0, contributed by 76 people, 22 of which are > new faces. > Brandon Williams (24): >

Re: [PATCH v2] f2fs: add an ioctl to disable GC for specific file

On 01/02, Chao Yu wrote: > On 2018/1/1 9:07, Jaegeuk Kim wrote: > > On 12/29, Chao Yu wrote: > >> On 2017/12/28 11:40, Jaegeuk Kim wrote: > >>> This patch gives a flag to disable GC on given file, which would be > >>> useful, when > >>> user wants to keep its block map. It also conducts

Re: [PATCH v2] f2fs: add an ioctl to disable GC for specific file

On 01/02, Chao Yu wrote: > On 2018/1/1 9:07, Jaegeuk Kim wrote: > > On 12/29, Chao Yu wrote: > >> On 2017/12/28 11:40, Jaegeuk Kim wrote: > >>> This patch gives a flag to disable GC on given file, which would be > >>> useful, when > >>> user wants to keep its block map. It also conducts

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

This patch gives a flag to disable GC on given file, which would be useful, when user wants to keep its block map. It also conducts in-place-update for dontmove file. Signed-off-by: Jaegeuk Kim --- Change log from v2: - modify ioctl to allow users unpin the file

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

This patch gives a flag to disable GC on given file, which would be useful, when user wants to keep its block map. It also conducts in-place-update for dontmove file. Signed-off-by: Jaegeuk Kim --- Change log from v2: - modify ioctl to allow users unpin the file fs/f2fs/data.c | 2

Re: [PATCH -next] soundwire: Fix typo in return value check of sdw_read()

On Tue, Jan 02, 2018 at 04:08:19AM +, Wei Yongjun wrote: > Fix the typo, 'status' should be instead of 'status2'. > > Fixes: b0a9c37b0178 ("soundwire: Add slave status handling") > Signed-off-by: Wei Yongjun Applied, thanks -- ~Vinod

Re: [PATCH -next] soundwire: Fix typo in return value check of sdw_read()

On Tue, Jan 02, 2018 at 04:08:19AM +, Wei Yongjun wrote: > Fix the typo, 'status' should be instead of 'status2'. > > Fixes: b0a9c37b0178 ("soundwire: Add slave status handling") > Signed-off-by: Wei Yongjun Applied, thanks -- ~Vinod

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Tue, Jan 02, 2018 at 09:52:03PM -0500, Mimi Zohar wrote: > On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > > [might as well cc linux-xfs] > > > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > > Hi, > > > > > > Could I ask FS maintainers to test IMA with this

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Tue, Jan 02, 2018 at 09:52:03PM -0500, Mimi Zohar wrote: > On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > > [might as well cc linux-xfs] > > > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > > Hi, > > > > > > Could I ask FS maintainers to test IMA with this

Re: [RFC PATCH 1/3] mm, numa: rework do_pages_move

On 01/02/2018 05:42 PM, Michal Hocko wrote: > On Tue 02-01-18 16:55:46, Anshuman Khandual wrote: >> On 12/08/2017 09:45 PM, Michal Hocko wrote: >>> From: Michal Hocko >>> >>> do_pages_move is supposed to move user defined memory (an array of >>> addresses) to the user defined

Re: [RFC PATCH 1/3] mm, numa: rework do_pages_move

On 01/02/2018 05:42 PM, Michal Hocko wrote: > On Tue 02-01-18 16:55:46, Anshuman Khandual wrote: >> On 12/08/2017 09:45 PM, Michal Hocko wrote: >>> From: Michal Hocko >>> >>> do_pages_move is supposed to move user defined memory (an array of >>> addresses) to the user defined numa nodes (an array

[PATCH V6 1/2] xxHash: create arch dependent 32/64-bit xxhash()

xxh32() - fast on both 32/64-bit platforms xxh64() - fast only on 64-bit platform Create xxhash() which will pickup fastest version on compile time. As result depends on cpu word size, the main proporse of that - in memory hashing. Changes: v2: - Create that patch v3 -> v6: -

[PATCH V6 1/2] xxHash: create arch dependent 32/64-bit xxhash()

xxh32() - fast on both 32/64-bit platforms xxh64() - fast only on 64-bit platform Create xxhash() which will pickup fastest version on compile time. As result depends on cpu word size, the main proporse of that - in memory hashing. Changes: v2: - Create that patch v3 -> v6: -

[PATCH V6 2/2] ksm: replace jhash2 with faster hash

1. Pickup, Sioh Lee crc32 patch, after some long conversation 2. Merge with my work on xxhash 3. Add autoselect code to choice fastest hash helper. Base idea are same, replace jhash2 with something faster. Perf numbers: Intel(R) Xeon(R) CPU E5-2420 v2 @ 2.20GHz ksm: crc32c hash() 12081 MB/s

[PATCH V6 2/2] ksm: replace jhash2 with faster hash

1. Pickup, Sioh Lee crc32 patch, after some long conversation 2. Merge with my work on xxhash 3. Add autoselect code to choice fastest hash helper. Base idea are same, replace jhash2 with something faster. Perf numbers: Intel(R) Xeon(R) CPU E5-2420 v2 @ 2.20GHz ksm: crc32c hash() 12081 MB/s

[PATCH -next] drm/panel: ili9322：Make local symbols static

Fixes the following sparse warnings: drivers/gpu/drm/panel/panel-ilitek-ili9322.c:182:12: warning: symbol 'ili9322_inputs' was not declared. Should it be static? drivers/gpu/drm/panel/panel-ilitek-ili9322.c:343:28: warning: symbol 'ili9322_regmap_config' was not declared. Should it be static?

[PATCH -next] drm/panel: ili9322：Make local symbols static

Fixes the following sparse warnings: drivers/gpu/drm/panel/panel-ilitek-ili9322.c:182:12: warning: symbol 'ili9322_inputs' was not declared. Should it be static? drivers/gpu/drm/panel/panel-ilitek-ili9322.c:343:28: warning: symbol 'ili9322_regmap_config' was not declared. Should it be static?

Re: [PATCH] liquidio: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sun, 31 Dec 2017 17:57:29 +0530 > Use vzalloc for allocating zeroed memory and remove unnecessary > memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no

Re: [PATCH] liquidio: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sun, 31 Dec 2017 17:57:29 +0530 > Use vzalloc for allocating zeroed memory and remove unnecessary > memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > > Suggested-by: Luis R.

[PATCH] nl80211: Check for the required netlink attribute presence

nl80211_nan_add_func() does not check if the required attribute NL80211_NAN_FUNC_FOLLOW_UP_DEST is present when processing NL80211_CMD_ADD_NAN_FUNCTION request. This request can be issued by users with CAP_NET_ADMIN privilege and may result in NULL dereference and a system crash. Add a check for

[PATCH] nl80211: Check for the required netlink attribute presence

nl80211_nan_add_func() does not check if the required attribute NL80211_NAN_FUNC_FOLLOW_UP_DEST is present when processing NL80211_CMD_ADD_NAN_FUNCTION request. This request can be issued by users with CAP_NET_ADMIN privilege and may result in NULL dereference and a system crash. Add a check for

Re: [PATCH 4/5] clk: sunxi: Use CLK_IS_CRITICAL flag for critical clks

On Wed, Jan 3, 2018 at 9:35 AM, Stephen Boyd wrote: > We'd like to privatize __clk_get(), but the sunxi clk driver is > calling this function to keep a reference held on the clk and > call clk_prepare_enable() on it. We support this design in the > clk core now with the

Re: [PATCH 4/5] clk: sunxi: Use CLK_IS_CRITICAL flag for critical clks

On Wed, Jan 3, 2018 at 9:35 AM, Stephen Boyd wrote: > We'd like to privatize __clk_get(), but the sunxi clk driver is > calling this function to keep a reference held on the clk and > call clk_prepare_enable() on it. We support this design in the > clk core now with the CLK_IS_CRITICAL flag, so

Re: About the try to remove cross-release feature entirely by Ingo

On Wed, Jan 03, 2018 at 11:28:44AM +0900, Byungchul Park wrote: > On 1/1/2018 7:18 PM, Matthew Wilcox wrote: > >On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: > >>Also, what to do with TCP connections which are created in userspace > >>(with some authentication exchanges happening

Re: About the try to remove cross-release feature entirely by Ingo

On Wed, Jan 03, 2018 at 11:28:44AM +0900, Byungchul Park wrote: > On 1/1/2018 7:18 PM, Matthew Wilcox wrote: > >On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: > >>Also, what to do with TCP connections which are created in userspace > >>(with some authentication exchanges happening

Re: [PATCH] ethernet/broadcom: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sat, 30 Dec 2017 21:14:57 +0530 > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with

Re: [PATCH] ethernet/broadcom: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sat, 30 Dec 2017 21:14:57 +0530 > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] qed: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sat, 30 Dec 2017 21:07:04 +0530 > Use dma_zalloc_coherent and vzalloc for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day

Re: [PATCH] qed: Use zeroing memory allocator than allocator/memset

From: Himanshu Jha Date: Sat, 30 Dec 2017 21:07:04 +0530 > Use dma_zalloc_coherent and vzalloc for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. >

Re: [PATCH net-next 0/2] net: stmmac: Couple of debug prints improvements

From: Florian Fainelli Date: Fri, 29 Dec 2017 19:56:31 -0800 > While working on a particular problem, I had to turn on debug prints and found > them to be useful, but could deserve some improvements in order to help debug > situations. Series applied, thanks Florian.

Re: [PATCH net-next 0/2] net: stmmac: Couple of debug prints improvements

From: Florian Fainelli Date: Fri, 29 Dec 2017 19:56:31 -0800 > While working on a particular problem, I had to turn on debug prints and found > them to be useful, but could deserve some improvements in order to help debug > situations. Series applied, thanks Florian.

Re: [PATCH net-next 2/2] tun: allow to attach ebpf socket filter

On 2018年01月02日 17:19, Willem de Bruijn wrote: More importantly, should this program just return a boolean pass or drop. Taking a length and trimming may introduce bugs later on if the stack parses the packet unconditionally, expecting a minimum size to be present. This was the reason for

Re: [PATCH net-next 2/2] tun: allow to attach ebpf socket filter

On 2018年01月02日 17:19, Willem de Bruijn wrote: More importantly, should this program just return a boolean pass or drop. Taking a length and trimming may introduce bugs later on if the stack parses the packet unconditionally, expecting a minimum size to be present. This was the reason for

Re: [PATCH net-next] net: dsa: Fix dsa_legacy_register() return value

From: Florian Fainelli Date: Fri, 29 Dec 2017 11:05:45 -0800 > We need to make the dsa_legacy_register() stub return 0 in order for > dsa_init_module() to successfully register and continue registering the > ETH_P_XDSA packet handler. > > Fixes: 2a93c1a3651f ("net: dsa:

Re: [PATCH net-next] net: dsa: Fix dsa_legacy_register() return value

From: Florian Fainelli Date: Fri, 29 Dec 2017 11:05:45 -0800 > We need to make the dsa_legacy_register() stub return 0 in order for > dsa_init_module() to successfully register and continue registering the > ETH_P_XDSA packet handler. > > Fixes: 2a93c1a3651f ("net: dsa: Allow compiling out

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > [might as well cc linux-xfs] > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > Hi, > > > > Could I ask FS maintainers to test IMA with this patch additionally > > and provide ack/tested. > > We tested but may be

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote: > [might as well cc linux-xfs] > > On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > > Hi, > > > > Could I ask FS maintainers to test IMA with this patch additionally > > and provide ack/tested. > > We tested but may be

Re: [PATCH net] ethtool: do not print warning for applications using legacy API

From: Stephen Hemminger Date: Fri, 29 Dec 2017 10:02:52 -0800 > From: Stephen Hemminger > > In kernel log ths message appears on every boot: > "warning: `NetworkChangeNo' uses legacy ethtool link settings API, > link modes are only

Re: [PATCH net] ethtool: do not print warning for applications using legacy API

From: Stephen Hemminger Date: Fri, 29 Dec 2017 10:02:52 -0800 > From: Stephen Hemminger > > In kernel log ths message appears on every boot: > "warning: `NetworkChangeNo' uses legacy ethtool link settings API, > link modes are only partially reported" > > When ethtool link settings API

Re: [linux-sunxi] [PATCH v4 1/6] ARM: sunxi: h3/h5: add simplefb nodes

On Tue, Jan 2, 2018 at 4:14 PM, Icenowy Zheng wrote: > 在 2018年1月2日星期二 CST 下午4:11:04，Chen-Yu Tsai 写道： >> On Sat, Dec 30, 2017 at 7:30 PM, Icenowy Zheng wrote: >> > The H3/H5 SoCs have a HDMI output and a TV Composite output. >> > >> > Add simplefb nodes for these

Re: [linux-sunxi] [PATCH v4 1/6] ARM: sunxi: h3/h5: add simplefb nodes

On Tue, Jan 2, 2018 at 4:14 PM, Icenowy Zheng wrote: > 在 2018年1月2日星期二 CST 下午4:11:04，Chen-Yu Tsai 写道： >> On Sat, Dec 30, 2017 at 7:30 PM, Icenowy Zheng wrote: >> > The H3/H5 SoCs have a HDMI output and a TV Composite output. >> > >> > Add simplefb nodes for these outputs. >> > >> > Signed-off-by:

Re: [PATCH V3] ARM: imx: use outer_disable/resume for low power

Hi Peng, On Tue, Jan 2, 2018 at 10:53 PM, Peng Fan wrote: > > A better solution maybe > > if (outer_cache.write_sec) > outer_disable(); > > . > > if (outer_cache.write_sec) > outer_resume(); > > Then, nothing changed for secure linux. The

Re: [PATCH V3] ARM: imx: use outer_disable/resume for low power

Hi Peng, On Tue, Jan 2, 2018 at 10:53 PM, Peng Fan wrote: > > A better solution maybe > > if (outer_cache.write_sec) > outer_disable(); > > . > > if (outer_cache.write_sec) > outer_resume(); > > Then, nothing changed for secure linux. The outer_disable/outer_resume only >

linux-next: manual merge of the kvm-arm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm-arm tree got a conflict in: virt/kvm/arm/arch_timer.c between commit: 36e5cfd410ad ("KVM: arm/arm64: Properly handle arch-timer IRQs after vtimer_save_state") from Linus' tree and commit: 70450a9fbe06 ("KVM: arm/arm64: Don't cache the timer

Re: About the try to remove cross-release feature entirely by Ingo

On 1/2/2018 1:00 AM, Theodore Ts'o wrote: On Mon, Jan 01, 2018 at 02:18:55AM -0800, Matthew Wilcox wrote: Clarification: all TCP connections that are used by kernel code would need to be in their own separate lock class. All TCP connections used only by userspace could be in their own shared

linux-next: manual merge of the kvm-arm tree with Linus' tree

Hi all, Today's linux-next merge of the kvm-arm tree got a conflict in: virt/kvm/arm/arch_timer.c between commit: 36e5cfd410ad ("KVM: arm/arm64: Properly handle arch-timer IRQs after vtimer_save_state") from Linus' tree and commit: 70450a9fbe06 ("KVM: arm/arm64: Don't cache the timer

Re: About the try to remove cross-release feature entirely by Ingo

On 1/2/2018 1:00 AM, Theodore Ts'o wrote: On Mon, Jan 01, 2018 at 02:18:55AM -0800, Matthew Wilcox wrote: Clarification: all TCP connections that are used by kernel code would need to be in their own separate lock class. All TCP connections used only by userspace could be in their own shared

Re: [PATCH v20 4/7] virtio-balloon: VIRTIO_BALLOON_F_SG

Matthew Wilcox wrote: > The radix tree convention is objectively awful, which is why I'm working > to change it. Specifying the GFP flags at radix tree initialisation time > rather than allocation time leads to all kinds of confusion. The preload > API is a pretty awful workaround, and it will

Re: About the try to remove cross-release feature entirely by Ingo

On 1/1/2018 7:18 PM, Matthew Wilcox wrote: On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 05:40:28PM -0500, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 12:44:17PM -0800, Matthew Wilcox wrote: I'm not sure I agree with this part. What if we add a new

Re: [PATCH v20 4/7] virtio-balloon: VIRTIO_BALLOON_F_SG

Matthew Wilcox wrote: > The radix tree convention is objectively awful, which is why I'm working > to change it. Specifying the GFP flags at radix tree initialisation time > rather than allocation time leads to all kinds of confusion. The preload > API is a pretty awful workaround, and it will

Re: About the try to remove cross-release feature entirely by Ingo

On 1/1/2018 7:18 PM, Matthew Wilcox wrote: On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 05:40:28PM -0500, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 12:44:17PM -0800, Matthew Wilcox wrote: I'm not sure I agree with this part. What if we add a new

Re: [PATCH] clk: fix reentrancy of clk_enable() on UP systems

On 12/28, David Lechner wrote: > On 12/26/2017 08:21 PM, Stephen Boyd wrote: > >On 12/26, David Lechner wrote: > >>Reentrant calls to clk_enable() are not working on UP systems. This is > >>caused by the fact spin_trylock_irqsave() always returns true when > >>CONFIG_SMP=n (and

Re: [PATCH] clk: fix reentrancy of clk_enable() on UP systems

On 12/28, David Lechner wrote: > On 12/26/2017 08:21 PM, Stephen Boyd wrote: > >On 12/26, David Lechner wrote: > >>Reentrant calls to clk_enable() are not working on UP systems. This is > >>caused by the fact spin_trylock_irqsave() always returns true when > >>CONFIG_SMP=n (and

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both

Re: [PATCH v5] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- Change log from v4: - fix f_bfree in statfs fs/f2fs/f2fs.h | 26 ++ fs/f2fs/super.c | 34

Re: [PATCH v1] eSPI: add Aspeed AST2500 eSPI driver to boot a host with PCH runs on eSPI

On 2018-01-03 00:23, Arnd Bergmann wrote: On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue wrote: On 2018-01-02 23:13, Arnd Bergmann wrote: On 2017-12-31 07:10, Arnd Bergmann wrote: It also seems rather inflexible to have a single driver that is responsible both for the transport (eSPI

Re: [PATCH v5] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- Change log from v4: - fix f_bfree in statfs fs/f2fs/f2fs.h | 26 ++ fs/f2fs/super.c | 34

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