[PATCH for v3.18 04/18] media: v4l2-compat-ioctl32.c: fix the indentation

From: Hans Verkuil commit b7b957d429f601d6d1942122b339474f31191d75 upstream. The indentation of this source is all over the place. Fix this. This patch only changes whitespace. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus

[PATCH for v3.18 00/18] Backport CVE-2017-13166 fixes to Kernel 3.18

Hi Greg, Those are the backports meant to solve CVE-2017-13166 on Kernel 3.18. It contains two v4l2-ctrls fixes that are required to avoid crashes at the test application. I wrote two patches myself for Kernel 3.18 in order to solve some issues specific for Kernel 3.18 with aren't needed

[PATCH for v3.18 04/18] media: v4l2-compat-ioctl32.c: fix the indentation

From: Hans Verkuil commit b7b957d429f601d6d1942122b339474f31191d75 upstream. The indentation of this source is all over the place. Fix this. This patch only changes whitespace. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Sasha Levin

[PATCH for v3.18 00/18] Backport CVE-2017-13166 fixes to Kernel 3.18

Hi Greg, Those are the backports meant to solve CVE-2017-13166 on Kernel 3.18. It contains two v4l2-ctrls fixes that are required to avoid crashes at the test application. I wrote two patches myself for Kernel 3.18 in order to solve some issues specific for Kernel 3.18 with aren't needed

Re: [PATCH 1/1] x86/platform/UV: Fix critical UV MMR address error

On Wed, 28 Mar 2018, mike.tra...@hpe.com wrote: > A critical error was found testing the fixed UV4 HUB in that an MMR > address was found to be incorrect. This causes the virtual address > space for accessing the MMIOH1 region to be allocated with the > incorrect size. Even if this is not

Re: [PATCH 1/1] x86/platform/UV: Fix critical UV MMR address error

On Wed, 28 Mar 2018, mike.tra...@hpe.com wrote: > A critical error was found testing the fixed UV4 HUB in that an MMR > address was found to be incorrect. This causes the virtual address > space for accessing the MMIOH1 region to be allocated with the > incorrect size. Even if this is not

[PATCH for v3.18 10/18] media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha

From: Daniel Mentz commit 025a26fa14f8fd55d50ab284a30c016a5be953d0 upstream. Commit b2787845fb91 ("V4L/DVB (5289): Add support for video output overlays.") added the field global_alpha to struct v4l2_window but did not update the compat layer accordingly. This change

[PATCH for v3.18 10/18] media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha

From: Daniel Mentz commit 025a26fa14f8fd55d50ab284a30c016a5be953d0 upstream. Commit b2787845fb91 ("V4L/DVB (5289): Add support for video output overlays.") added the field global_alpha to struct v4l2_window but did not update the compat layer accordingly. This change adds global_alpha to struct

[PATCH for v3.18 11/18] media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32

From: Hans Verkuil commit a751be5b142ef6bcbbb96d9899516f4d9c8d0ef4 upstream. put_v4l2_window32() didn't copy back the clip list to userspace. Drivers can update the clip rectangles, so this should be done. Signed-off-by: Hans Verkuil Acked-by:

[PATCH for v3.18 11/18] media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32

From: Hans Verkuil commit a751be5b142ef6bcbbb96d9899516f4d9c8d0ef4 upstream. put_v4l2_window32() didn't copy back the clip list to userspace. Drivers can update the clip rectangles, so this should be done. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus Signed-off-by: Mauro Carvalho

[PATCH for v3.18 05/18] media: v4l2-compat-ioctl32.c: move 'helper' functions to __get/put_v4l2_format32

From: Hans Verkuil commit 486c521510c44a04cd756a9267e7d1e271c8a4ba upstream. These helper functions do not really help. Move the code to the __get/put_v4l2_format32 functions. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus

[PATCH for v3.18 05/18] media: v4l2-compat-ioctl32.c: move 'helper' functions to __get/put_v4l2_format32

From: Hans Verkuil commit 486c521510c44a04cd756a9267e7d1e271c8a4ba upstream. These helper functions do not really help. Move the code to the __get/put_v4l2_format32 functions. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Sasha Levin

Re: [PATCH] debugfs: Check return value of debugfs_real_fops() for NULL

El Wed, Mar 28, 2018 at 08:05:56PM +0200 Greg Kroah-Hartman ha dit: > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > A: No. > Q: Should I include quotations

Re: [PATCH] debugfs: Check return value of debugfs_real_fops() for NULL

El Wed, Mar 28, 2018 at 08:05:56PM +0200 Greg Kroah-Hartman ha dit: > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > A: No. > Q: Should I include quotations

[PATCH for v3.18 17/18] media: v4l2-compat-ioctl32: use compat_u64 for video standard

Instead of using the "v4l2_std_id" typedef, use compat_u64, as otherwise it fails to properly handle some ioctls. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH for v3.18 08/18] media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer

From: Hans Verkuil commit b8c601e8af2d08f733d74defa8465303391bb930 upstream. ctrl_is_pointer just hardcoded two known string controls, but that caused problems when using e.g. custom controls that use a pointer for the payload. Reimplement this function: it now finds

[PATCH for v3.18 08/18] media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer

From: Hans Verkuil commit b8c601e8af2d08f733d74defa8465303391bb930 upstream. ctrl_is_pointer just hardcoded two known string controls, but that caused problems when using e.g. custom controls that use a pointer for the payload. Reimplement this function: it now finds the v4l2_ctrl (if the

[PATCH for v3.18 17/18] media: v4l2-compat-ioctl32: use compat_u64 for video standard

Instead of using the "v4l2_std_id" typedef, use compat_u64, as otherwise it fails to properly handle some ioctls. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v7 0/2] hid-steam driver with user mode client dection

On Mon, Mar 26, 2018 at 10:12:19AM +0200, Benjamin Tissoires wrote: > Hi Rodrigo, > > On Sun, Mar 25, 2018 at 6:07 PM, Rodrigo Rivas Costa > wrote: > > This is a reroll of the Steam Controller driver. > > > > This time the client usage is detected by using exposing a

Re: [PATCH v7 0/2] hid-steam driver with user mode client dection

On Mon, Mar 26, 2018 at 10:12:19AM +0200, Benjamin Tissoires wrote: > Hi Rodrigo, > > On Sun, Mar 25, 2018 at 6:07 PM, Rodrigo Rivas Costa > wrote: > > This is a reroll of the Steam Controller driver. > > > > This time the client usage is detected by using exposing a custom hidraw > > device

[PATCH for v3.18 02/18] vb2: V4L2_BUF_FLAG_DONE is set after DQBUF

From: Ricardo Ribalda commit 3171cc2b4eb9831ab4df1d80d0410a945b8bc84e upstream. According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF: V4L2_BUF_FLAG_DONE 0x0004 ... After calling the VIDIOC_QBUF or VIDIOC_DQBUF it is always cleared ... Unfortunately,

[PATCH for v3.18 02/18] vb2: V4L2_BUF_FLAG_DONE is set after DQBUF

From: Ricardo Ribalda commit 3171cc2b4eb9831ab4df1d80d0410a945b8bc84e upstream. According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF: V4L2_BUF_FLAG_DONE 0x0004 ... After calling the VIDIOC_QBUF or VIDIOC_DQBUF it is always cleared ... Unfortunately, it seems that videobuf2

[PATCH for v3.18 16/18] media: media/v4l2-ctrls: volatiles should not generate CH_VALUE

From: Ricardo Ribalda Volatile controls should not generate CH_VALUE events. Set has_changed to false to prevent this happening. Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Hans Verkuil Signed-off-by:

[PATCH for v3.18 12/18] media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type

From: Hans Verkuil commit 169f24ca68bf0f247d111aef07af00dd3a02ae88 upstream. There is nothing wrong with using an unknown buffer type. So stop spamming the kernel log whenever this happens. The kernel will just return -EINVAL to signal this. Signed-off-by: Hans Verkuil

[PATCH for v3.18 16/18] media: media/v4l2-ctrls: volatiles should not generate CH_VALUE

From: Ricardo Ribalda Volatile controls should not generate CH_VALUE events. Set has_changed to false to prevent this happening. Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Mauro Carvalho Chehab ---

[PATCH for v3.18 12/18] media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type

From: Hans Verkuil commit 169f24ca68bf0f247d111aef07af00dd3a02ae88 upstream. There is nothing wrong with using an unknown buffer type. So stop spamming the kernel log whenever this happens. The kernel will just return -EINVAL to signal this. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus

[PATCH for v3.18 18/18] media: v4l2-compat-ioctl32: initialize a reserved field

The get_v4l2_create32() function is missing a logic with would be cleaning a reserved field, causing v4l2-compliance to complain: Buffer ioctls (Input 0): fail: v4l2-test-buffers.cpp(506): check_0(crbufs.reserved, sizeof(crbufs.reserved)) test

[PATCH for v3.18 18/18] media: v4l2-compat-ioctl32: initialize a reserved field

The get_v4l2_create32() function is missing a logic with would be cleaning a reserved field, causing v4l2-compliance to complain: Buffer ioctls (Input 0): fail: v4l2-test-buffers.cpp(506): check_0(crbufs.reserved, sizeof(crbufs.reserved)) test

[PATCH for v3.18 06/18] media: v4l2-compat-ioctl32.c: avoid sizeof(type)

From: Hans Verkuil commit 333b1e9f96ce05f7498b581509bb30cde03018bf upstream. Instead of doing sizeof(struct foo) use sizeof(*up). There even were cases where 4 * sizeof(__u32) was used instead of sizeof(kp->reserved), which is very dangerous when the size of the reserved

[PATCH for v3.18 06/18] media: v4l2-compat-ioctl32.c: avoid sizeof(type)

From: Hans Verkuil commit 333b1e9f96ce05f7498b581509bb30cde03018bf upstream. Instead of doing sizeof(struct foo) use sizeof(*up). There even were cases where 4 * sizeof(__u32) was used instead of sizeof(kp->reserved), which is very dangerous when the size of the reserved array changes.

[PATCH for v3.18 14/18] media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic

From: Daniel Mentz commit a1dfb4c48cc1e64eeb7800a27c66a6f7e88d075a upstream. The 32-bit compat v4l2 ioctl handling is implemented based on its 64-bit equivalent. It converts 32-bit data structures into its 64-bit equivalents and needs to provide the data to the 64-bit

[PATCH for v3.18 14/18] media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic

From: Daniel Mentz commit a1dfb4c48cc1e64eeb7800a27c66a6f7e88d075a upstream. The 32-bit compat v4l2 ioctl handling is implemented based on its 64-bit equivalent. It converts 32-bit data structures into its 64-bit equivalents and needs to provide the data to the 64-bit ioctl in user space memory

[PATCH for v3.18 01/18] media: v4l2-ioctl.c: don't copy back the result for -ENOTTY

From: Hans Verkuil commit 181a4a2d5a0a7b43cab08a70710d727e7764ccdd upstream. If the ioctl returned -ENOTTY, then don't bother copying back the result as there is no point. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus

[PATCH for v3.18 01/18] media: v4l2-ioctl.c: don't copy back the result for -ENOTTY

From: Hans Verkuil commit 181a4a2d5a0a7b43cab08a70710d727e7764ccdd upstream. If the ioctl returned -ENOTTY, then don't bother copying back the result as there is no point. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Sasha Levin

[PATCH for v3.18 13/18] media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors

From: Hans Verkuil commit d83a8243aaefe62ace433e4384a4f077bed86acb upstream. Some ioctls need to copy back the result even if the ioctl returned an error. However, don't do this for the error code -ENOTTY. It makes no sense in that cases. Signed-off-by: Hans Verkuil

[PATCH for v3.18 13/18] media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors

From: Hans Verkuil commit d83a8243aaefe62ace433e4384a4f077bed86acb upstream. Some ioctls need to copy back the result even if the ioctl returned an error. However, don't do this for the error code -ENOTTY. It makes no sense in that cases. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus

[PATCH for v3.18 07/18] media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32

From: Hans Verkuil commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream. The struct v4l2_plane32 should set m.userptr as well. The same happens in v4l2_buffer32 and v4l2-compliance tests for this. Signed-off-by: Hans Verkuil Acked-by: Sakari

[PATCH for v3.18 07/18] media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32

From: Hans Verkuil commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream. The struct v4l2_plane32 should set m.userptr as well. The same happens in v4l2_buffer32 and v4l2-compliance tests for this. Signed-off-by: Hans Verkuil Acked-by: Sakari Ailus Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH v9 09/24] mm: protect mremap() against SPF hanlder

On 28/03/2018 00:12, David Rientjes wrote: > On Tue, 13 Mar 2018, Laurent Dufour wrote: > >> diff --git a/include/linux/mm.h b/include/linux/mm.h >> index 88042d843668..ef6ef0627090 100644 >> --- a/include/linux/mm.h >> +++ b/include/linux/mm.h >> @@ -2189,16 +2189,24 @@ void

Re: [PATCH v9 09/24] mm: protect mremap() against SPF hanlder

On 28/03/2018 00:12, David Rientjes wrote: > On Tue, 13 Mar 2018, Laurent Dufour wrote: > >> diff --git a/include/linux/mm.h b/include/linux/mm.h >> index 88042d843668..ef6ef0627090 100644 >> --- a/include/linux/mm.h >> +++ b/include/linux/mm.h >> @@ -2189,16 +2189,24 @@ void

Re: [PATCH] crypto: cavium: zip: Remove unnecessary parentheses

On Wed, 2018-03-28 at 23:27 +0530, Varsha Rao wrote: > This patch fixes the clang warning of extraneous parentheses, with the > following coccinelle script. > > @@ > identifier i; > constant c; > @@ > ( > -((i == c)) > +i == c > > > > -((i <= c)) > +i <= c Why just the "==" and "<=" cases? Why

Re: [PATCH] crypto: cavium: zip: Remove unnecessary parentheses

On Wed, 2018-03-28 at 23:27 +0530, Varsha Rao wrote: > This patch fixes the clang warning of extraneous parentheses, with the > following coccinelle script. > > @@ > identifier i; > constant c; > @@ > ( > -((i == c)) > +i == c > > > > -((i <= c)) > +i <= c Why just the "==" and "<=" cases? Why

Re: [PATCH] debugfs: Check return value of debugfs_real_fops() for NULL

A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Wed, Mar 28, 2018 at

Re: [PATCH] debugfs: Check return value of debugfs_real_fops() for NULL

A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Wed, Mar 28, 2018 at

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 02:03:34PM -0400, J. Bruce Fields wrote: > Thanks, got it. Do you know how to find a commit id for that change? > It's not entirely fair to blame the crypto change for what was really a > latent nfs bug, but it might still be worth adding a Fixes: line just so > people

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 02:03:34PM -0400, J. Bruce Fields wrote: > Thanks, got it. Do you know how to find a commit id for that change? > It's not entirely fair to blame the crypto change for what was really a > latent nfs bug, but it might still be worth adding a Fixes: line just so > people

Re: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}

On Wed, 28 Mar 2018, Paul E. McKenney wrote: > On Wed, Mar 28, 2018 at 11:01:25AM -0400, Alan Stern wrote: > > On Wed, 28 Mar 2018, Paul E. McKenney wrote: > > > > > Hello! > > > > > > The prototype patch shown below provides files required to allow herd7 to > > > evaluate C-language litmus

Re: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}

On Wed, 28 Mar 2018, Paul E. McKenney wrote: > On Wed, Mar 28, 2018 at 11:01:25AM -0400, Alan Stern wrote: > > On Wed, 28 Mar 2018, Paul E. McKenney wrote: > > > > > Hello! > > > > > > The prototype patch shown below provides files required to allow herd7 to > > > evaluate C-language litmus

Re: [PATCH] docs/memory-barriers.txt: Fix broken DMA vs MMIO ordering example

On Wed, Mar 28, 2018 at 10:57:11AM -0700, Tony Luck wrote: > On Wed, Mar 28, 2018 at 6:02 AM, Sinan Kaya wrote: > > +linux-ia64 > > Does IA64 follow this requirement? If not, is implementation planned? > > > > "no wmb() before writel()" > > > > Linus asked us to get rid of

Re: [PATCH] docs/memory-barriers.txt: Fix broken DMA vs MMIO ordering example

On Wed, Mar 28, 2018 at 10:57:11AM -0700, Tony Luck wrote: > On Wed, Mar 28, 2018 at 6:02 AM, Sinan Kaya wrote: > > +linux-ia64 > > Does IA64 follow this requirement? If not, is implementation planned? > > > > "no wmb() before writel()" > > > > Linus asked us to get rid of wmb() in front of

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 10:50:51AM -0700, Eric Biggers wrote: > On Wed, Mar 28, 2018 at 11:46:28AM -0400, J. Bruce Fields wrote: > > On Tue, Mar 27, 2018 at 03:29:50PM -0700, Eric Biggers wrote: > > > Hi Michael, > > > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > >

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 10:50:51AM -0700, Eric Biggers wrote: > On Wed, Mar 28, 2018 at 11:46:28AM -0400, J. Bruce Fields wrote: > > On Tue, Mar 27, 2018 at 03:29:50PM -0700, Eric Biggers wrote: > > > Hi Michael, > > > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > >

[PATCH v3] gpio: Remove VLA from stmpe driver

The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) The number of GPIOs on the supported chips is fairly small so stack allocate to a known upper bound and spit out a warning if any new chips have more gpios. Signed-off-by: Laura Abbott

[PATCH v3] gpio: Remove VLA from stmpe driver

The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) The number of GPIOs on the supported chips is fairly small so stack allocate to a known upper bound and spit out a warning if any new chips have more gpios. Signed-off-by: Laura Abbott --- v3: Split

Re: [PATCH V4 Resend] ZBOOT: fix stack protector in compressed boot phase

On Wed, Mar 28, 2018 at 04:48:53PM +0800, Huacai Chen wrote: > Call __stack_chk_guard_setup() in decompress_kernel() is too late that > stack checking always fails for decompress_kernel() itself. So remove > __stack_chk_guard_setup() and initialize __stack_chk_guard before we > call

Re: [PATCH V4 Resend] ZBOOT: fix stack protector in compressed boot phase

On Wed, Mar 28, 2018 at 04:48:53PM +0800, Huacai Chen wrote: > Call __stack_chk_guard_setup() in decompress_kernel() is too late that > stack checking always fails for decompress_kernel() itself. So remove > __stack_chk_guard_setup() and initialize __stack_chk_guard before we > call

Re: [PATCH v9 07/24] mm: VMA sequence count

On 27/03/2018 23:30, David Rientjes wrote: > On Tue, 13 Mar 2018, Laurent Dufour wrote: > >> diff --git a/mm/mmap.c b/mm/mmap.c >> index faf85699f1a1..5898255d0aeb 100644 >> --- a/mm/mmap.c >> +++ b/mm/mmap.c >> @@ -558,6 +558,10 @@ void __vma_link_rb(struct mm_struct *mm, struct >>

Re: [PATCH v9 07/24] mm: VMA sequence count

On 27/03/2018 23:30, David Rientjes wrote: > On Tue, 13 Mar 2018, Laurent Dufour wrote: > >> diff --git a/mm/mmap.c b/mm/mmap.c >> index faf85699f1a1..5898255d0aeb 100644 >> --- a/mm/mmap.c >> +++ b/mm/mmap.c >> @@ -558,6 +558,10 @@ void __vma_link_rb(struct mm_struct *mm, struct >>

[PATCH] crypto: cavium: zip: Remove unnecessary parentheses

This patch fixes the clang warning of extraneous parentheses, with the following coccinelle script. @@ identifier i; constant c; @@ ( -((i == c)) +i == c | -((i <= c)) +i <= c ) Signed-off-by: Varsha Rao --- drivers/crypto/cavium/zip/zip_regs.h | 42

[PATCH] crypto: cavium: zip: Remove unnecessary parentheses

This patch fixes the clang warning of extraneous parentheses, with the following coccinelle script. @@ identifier i; constant c; @@ ( -((i == c)) +i == c | -((i <= c)) +i <= c ) Signed-off-by: Varsha Rao --- drivers/crypto/cavium/zip/zip_regs.h | 42 ++-- 1 file

Re: [PATCH] docs/memory-barriers.txt: Fix broken DMA vs MMIO ordering example

On Wed, Mar 28, 2018 at 6:02 AM, Sinan Kaya wrote: > +linux-ia64 > Does IA64 follow this requirement? If not, is implementation planned? > > "no wmb() before writel()" > > Linus asked us to get rid of wmb() in front of writel() for UC memory. > Just checking that we are not

Re: [PATCH] docs/memory-barriers.txt: Fix broken DMA vs MMIO ordering example

On Wed, Mar 28, 2018 at 6:02 AM, Sinan Kaya wrote: > +linux-ia64 > Does IA64 follow this requirement? If not, is implementation planned? > > "no wmb() before writel()" > > Linus asked us to get rid of wmb() in front of writel() for UC memory. > Just checking that we are not breaking anything for

[PATCH v6 7/9] gpio: Add gpio driver for Actions OWL S900 SoC

Add gpio driver for Actions Semi OWL family S900 SoC. Set of registers controlling the gpio shares the same register range with pinctrl block. GPIO registers are organized as 6 banks and each bank controls the maximum of 32 gpios. Signed-off-by: Manivannan Sadhasivam

[PATCH v6 7/9] gpio: Add gpio driver for Actions OWL S900 SoC

Add gpio driver for Actions Semi OWL family S900 SoC. Set of registers controlling the gpio shares the same register range with pinctrl block. GPIO registers are organized as 6 banks and each bank controls the maximum of 32 gpios. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Andy

[PATCH v6 8/9] MAINTAINERS: Add reviewer for ACTIONS platforms

Since I'll be working on improving support for ACTIONS platforms, adding myself as the reviewer. Signed-off-by: Manivannan Sadhasivam --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9a7f76eadae9..640dabc4c311

[PATCH v6 9/9] MAINTAINERS: Add Actions Semi S900 pinctrl and gpio entries

Add S900 pinctrl and gpio entries under ARCH_ACTIONS Signed-off-by: Manivannan Sadhasivam --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 640dabc4c311..d63793ee545e 100644 --- a/MAINTAINERS +++

[PATCH v6 8/9] MAINTAINERS: Add reviewer for ACTIONS platforms

Since I'll be working on improving support for ACTIONS platforms, adding myself as the reviewer. Signed-off-by: Manivannan Sadhasivam --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9a7f76eadae9..640dabc4c311 100644 --- a/MAINTAINERS +++

[PATCH v6 9/9] MAINTAINERS: Add Actions Semi S900 pinctrl and gpio entries

Add S900 pinctrl and gpio entries under ARCH_ACTIONS Signed-off-by: Manivannan Sadhasivam --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 640dabc4c311..d63793ee545e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1125,10 +1125,14 @@ F:

Re: 98f929b1bd ("ipc/shm: Fix shmctl(..., IPC_STAT, ...) between .."): Oops: 0000 [#1]

Nagarathnam Muthusamy writes: > Hi Eric, > >     From > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/tree/ipc/shm.c?h=for-next > > It looks like if the following condition in Line 616 succeeds > > error = PTR_ERR(file); > if

Re: 98f929b1bd ("ipc/shm: Fix shmctl(..., IPC_STAT, ...) between .."): Oops: 0000 [#1]

Nagarathnam Muthusamy writes: > Hi Eric, > >     From > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/tree/ipc/shm.c?h=for-next > > It looks like if the following condition in Line 616 succeeds > > error = PTR_ERR(file); > if (IS_ERR(file)) >     goto no_file; > >

Re: [RFC PATCH for 4.17 10/21] cpu_opv: Provide cpu_opv system call (v6)

- On Mar 28, 2018, at 11:22 AM, Peter Zijlstra pet...@infradead.org wrote: > On Tue, Mar 27, 2018 at 12:05:31PM -0400, Mathieu Desnoyers wrote: > >> 1) Allow algorithms to perform per-cpu data migration without relying on >>sched_setaffinity() >> >> The use-cases are migrating memory

Re: [RFC PATCH for 4.17 10/21] cpu_opv: Provide cpu_opv system call (v6)

- On Mar 28, 2018, at 11:22 AM, Peter Zijlstra pet...@infradead.org wrote: > On Tue, Mar 27, 2018 at 12:05:31PM -0400, Mathieu Desnoyers wrote: > >> 1) Allow algorithms to perform per-cpu data migration without relying on >>sched_setaffinity() >> >> The use-cases are migrating memory

[PATCH v6 6/9] arm64: dts: actions: Add gpio line names to Bubblegum-96 board

Add gpio line names to Actions Semi S900 based Bubblegum-96 board. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/boot/dts/actions/s900-bubblegum-96.dts | 195 ++ 1 file changed, 195

[PATCH v6 6/9] arm64: dts: actions: Add gpio line names to Bubblegum-96 board

Add gpio line names to Actions Semi S900 based Bubblegum-96 board. Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/boot/dts/actions/s900-bubblegum-96.dts | 195 ++ 1 file changed, 195 insertions(+) diff --git

[PATCH v6 4/9] dt-bindings: gpio: Add gpio nodes for Actions S900 SoC

Add gpio nodes for Actions Semi S900 SoC. Signed-off-by: Manivannan Sadhasivam --- .../devicetree/bindings/gpio/actions,owl-gpio.txt | 87 ++ 1 file changed, 87 insertions(+) create mode 100644

[PATCH v6 2/9] arm64: actions: Enable PINCTRL in platforms Kconfig

Select PINCTRL for Actions Semi SoCs Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/Kconfig.platforms | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig.platforms

[PATCH v6 4/9] dt-bindings: gpio: Add gpio nodes for Actions S900 SoC

Add gpio nodes for Actions Semi S900 SoC. Signed-off-by: Manivannan Sadhasivam --- .../devicetree/bindings/gpio/actions,owl-gpio.txt | 87 ++ 1 file changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/gpio/actions,owl-gpio.txt diff --git

[PATCH v6 2/9] arm64: actions: Enable PINCTRL in platforms Kconfig

Select PINCTRL for Actions Semi SoCs Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/Kconfig.platforms | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms index fbedbd8f619a..bae1289bdc3f 100644 ---

[PATCH v6 3/9] pinctrl: actions: Add Actions S900 pinctrl driver

Add pinctrl driver for Actions Semi S900 SoC. The driver supports pinctrl, pinmux and pinconf functionalities through a range of registers common to both gpio driver and pinctrl driver. Pinmux functionality is available only for the pin groups while the pinconf functionality is available for both

[PATCH v6 3/9] pinctrl: actions: Add Actions S900 pinctrl driver

Add pinctrl driver for Actions Semi S900 SoC. The driver supports pinctrl, pinmux and pinconf functionalities through a range of registers common to both gpio driver and pinctrl driver. Pinmux functionality is available only for the pin groups while the pinconf functionality is available for both

[PATCH v6 5/9] arm64: dts: actions: Add S900 gpio nodes

Add gpio nodes for Actions Semi S900 SoC. Signed-off-by: Manivannan Sadhasivam --- arch/arm64/boot/dts/actions/s900.dtsi | 51 +++ 1 file changed, 51 insertions(+) diff --git a/arch/arm64/boot/dts/actions/s900.dtsi

[PATCH v6 5/9] arm64: dts: actions: Add S900 gpio nodes

Add gpio nodes for Actions Semi S900 SoC. Signed-off-by: Manivannan Sadhasivam --- arch/arm64/boot/dts/actions/s900.dtsi | 51 +++ 1 file changed, 51 insertions(+) diff --git a/arch/arm64/boot/dts/actions/s900.dtsi b/arch/arm64/boot/dts/actions/s900.dtsi index

[PATCH v6 0/9] Add Actions Semi S900 pinctrl and gpio support

This patchset adds pinctrl and gpio support for Actions Semi S900 SoC. Pinctrl and gpio subsystems share the common set of register range but implemented as individual drivers for making it less complex. Pinmux functions are only accessible for pin groups while pinconf parameters are available

[PATCH v6 1/9] arm64: dts: actions: Add pinctrl node for S900

Add pinctrl nodes for Actions Semi S900 SoC Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/boot/dts/actions/s900.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v6 1/9] arm64: dts: actions: Add pinctrl node for S900

Add pinctrl nodes for Actions Semi S900 SoC Signed-off-by: Manivannan Sadhasivam Reviewed-by: Linus Walleij --- arch/arm64/boot/dts/actions/s900.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/actions/s900.dtsi b/arch/arm64/boot/dts/actions/s900.dtsi index

[PATCH v6 0/9] Add Actions Semi S900 pinctrl and gpio support

This patchset adds pinctrl and gpio support for Actions Semi S900 SoC. Pinctrl and gpio subsystems share the common set of register range but implemented as individual drivers for making it less complex. Pinmux functions are only accessible for pin groups while pinconf parameters are available

Re: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}

On Wed, Mar 28, 2018 at 11:01:25AM -0400, Alan Stern wrote: > I don't quite see the point of this. You're not suggesting that we > have one Linux Kernel Memory Consistency Model for s390 and another > one for all the other architectures, are you? > > If the idea is merely to provide a herd model

Re: [PATCH RFC tools/memory-model] Add s390.{cfg,cat}

On Wed, Mar 28, 2018 at 11:01:25AM -0400, Alan Stern wrote: > I don't quite see the point of this. You're not suggesting that we > have one Linux Kernel Memory Consistency Model for s390 and another > one for all the other architectures, are you? > > If the idea is merely to provide a herd model

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 11:46:28AM -0400, J. Bruce Fields wrote: > On Tue, Mar 27, 2018 at 03:29:50PM -0700, Eric Biggers wrote: > > Hi Michael, > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > NFS mounts stopped working on one of my computers after a kernel update >

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 11:46:28AM -0400, J. Bruce Fields wrote: > On Tue, Mar 27, 2018 at 03:29:50PM -0700, Eric Biggers wrote: > > Hi Michael, > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > NFS mounts stopped working on one of my computers after a kernel update >

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

On Wed, Mar 28, 2018 at 11:37:06AM -0400, Mathieu Desnoyers wrote: > - On Mar 28, 2018, at 11:28 AM, Peter Zijlstra pet...@infradead.org wrote: > > > On Wed, Mar 28, 2018 at 11:14:05AM -0400, Mathieu Desnoyers wrote: > > > >> > If at all possible I would make it SIGSEGV when issueing

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

On Wed, Mar 28, 2018 at 11:37:06AM -0400, Mathieu Desnoyers wrote: > - On Mar 28, 2018, at 11:28 AM, Peter Zijlstra pet...@infradead.org wrote: > > > On Wed, Mar 28, 2018 at 11:14:05AM -0400, Mathieu Desnoyers wrote: > > > >> > If at all possible I would make it SIGSEGV when issueing

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 09:00:14AM +0100, M A Young wrote: > On Tue, 27 Mar 2018, Eric Biggers wrote: > > > Hi Michael, > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > NFS mounts stopped working on one of my computers after a kernel update > > > from > > > 4.15.3 to

Re: NFS mounts failing when keytab present on client

On Wed, Mar 28, 2018 at 09:00:14AM +0100, M A Young wrote: > On Tue, 27 Mar 2018, Eric Biggers wrote: > > > Hi Michael, > > > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > > NFS mounts stopped working on one of my computers after a kernel update > > > from > > > 4.15.3 to

Re: [PATCH][next] wil6210: fix potential null dereference of ndev before null check

On 2018-03-28 20:40, Colin King wrote: From: Colin Ian King The pointer ndev is being dereferenced before it is being null checked, hence there is a potential null pointer deference. Fix this by only dereferencing ndev after it has been null checked Detected by

Re: [PATCH][next] wil6210: fix potential null dereference of ndev before null check

On 2018-03-28 20:40, Colin King wrote: From: Colin Ian King The pointer ndev is being dereferenced before it is being null checked, hence there is a potential null pointer deference. Fix this by only dereferencing ndev after it has been null checked Detected by CoverityScan, CID#1467010

[PATCH 0/1] x86/platform/UV: UV Fix patches for Intel processors

Updates to UV4 fix patches. --

[PATCH 0/1] x86/platform/UV: UV Fix patches for Intel processors

Updates to UV4 fix patches. --

[PATCH 1/1] x86/platform/UV: Fix critical UV MMR address error

A critical error was found testing the fixed UV4 HUB in that an MMR address was found to be incorrect. This causes the virtual address space for accessing the MMIOH1 region to be allocated with the incorrect size. Signed-off-by: Mike Travis --- arch/x86/include/asm/uv/uv_mmrs.h

[PATCH 1/1] x86/platform/UV: Fix critical UV MMR address error

A critical error was found testing the fixed UV4 HUB in that an MMR address was found to be incorrect. This causes the virtual address space for accessing the MMIOH1 region to be allocated with the incorrect size. Signed-off-by: Mike Travis --- arch/x86/include/asm/uv/uv_mmrs.h |2 +- 1

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