[PATCH 16/34] [media] DaVinci-VPFE-Capture: Delete an unnecessary variable initialisation in vpfe_probe()

From: Markus Elfring Date: Wed, 12 Oct 2016 10:30:28 +0200 * Return an error code as a constant after a failed call of the function "vpfe_initialize". * The local variable "ret" will be set then to an appropriate value a bit later. Thus omit the explicit

[PATCH 15/34] [media] DaVinci-VPFE-Capture: Improve another size determination in vpfe_probe()

From: Markus Elfring Date: Wed, 12 Oct 2016 10:24:57 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer. Signed-off-by: Markus Elfring

[PATCH 15/34] [media] DaVinci-VPFE-Capture: Improve another size determination in vpfe_probe()

From: Markus Elfring Date: Wed, 12 Oct 2016 10:24:57 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer. Signed-off-by: Markus Elfring ---

[PATCH 16/34] [media] DaVinci-VPFE-Capture: Delete an unnecessary variable initialisation in vpfe_probe()

From: Markus Elfring Date: Wed, 12 Oct 2016 10:30:28 +0200 * Return an error code as a constant after a failed call of the function "vpfe_initialize". * The local variable "ret" will be set then to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning.

Re: linux.git: printk() problem

On Wed 12-10-16 22:30:03, Tetsuo Handa wrote: > Hello. > > I noticed that current linux.git generates hardly readable console output > due to KERN_CONT changes. Are you suggesting developers that output like > this be fixed? Joe has already posted a patch

Re: linux.git: printk() problem

On Wed 12-10-16 22:30:03, Tetsuo Handa wrote: > Hello. > > I noticed that current linux.git generates hardly readable console output > due to KERN_CONT changes. Are you suggesting developers that output like > this be fixed? Joe has already posted a patch

[PATCH 10/34] [media] DaVinci-VPBE: Check return value of a setup_if_config() call in vpbe_set_output()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:56:56 +0200 * A function was called over the pointer "setup_if_config" in the data structure "venc_platform_data". But the return value was not used so far. Thus assign it to the local variable "ret" which will be

[PATCH 10/34] [media] DaVinci-VPBE: Check return value of a setup_if_config() call in vpbe_set_output()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:56:56 +0200 * A function was called over the pointer "setup_if_config" in the data structure "venc_platform_data". But the return value was not used so far. Thus assign it to the local variable "ret" which will be checked with the next

Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)

On Wed, 2016-10-12 at 17:34 +0300, Jani Nikula wrote: > In the mean time, please file a bug over at [1] so we don't lose > track. Done:  https://bugs.freedesktop.org/show_bug.cgi?id=98214 Paul Bolle

Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)

On Wed, 2016-10-12 at 17:34 +0300, Jani Nikula wrote: > In the mean time, please file a bug over at [1] so we don't lose > track. Done:  https://bugs.freedesktop.org/show_bug.cgi?id=98214 Paul Bolle

Re: btrfs bio linked list corruption.

On Wed, Oct 12, 2016 at 09:47:17AM -0400, Dave Jones wrote: > On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > > This is from Linus' current tree, with Al's iovec fixups on top. > > > > > > [ cut here

Re: btrfs bio linked list corruption.

On Wed, Oct 12, 2016 at 09:47:17AM -0400, Dave Jones wrote: > On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > > This is from Linus' current tree, with Al's iovec fixups on top. > > > > > > [ cut here

[PATCH 05/34] [media] DaVinci-VPBE: Return an error code only as a constant in vpbe_probe()

From: Markus Elfring Date: Tue, 11 Oct 2016 13:43:25 +0200 * Return an error code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

[PATCH 06/34] [media] DaVinci-VPBE: Return an error code only by a single variable in vpbe_initialize()

From: Markus Elfring Date: Tue, 11 Oct 2016 14:15:57 +0200 An error code was assigned to the local variable "err" in an if branch. But this variable was not used further then. Use the local variable "ret" instead like at other places in this function. Fixes:

[PATCH 05/34] [media] DaVinci-VPBE: Return an error code only as a constant in vpbe_probe()

From: Markus Elfring Date: Tue, 11 Oct 2016 13:43:25 +0200 * Return an error code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- drivers/media/platform/davinci/vpbe.c | 3

[PATCH 06/34] [media] DaVinci-VPBE: Return an error code only by a single variable in vpbe_initialize()

From: Markus Elfring Date: Tue, 11 Oct 2016 14:15:57 +0200 An error code was assigned to the local variable "err" in an if branch. But this variable was not used further then. Use the local variable "ret" instead like at other places in this function. Fixes:

Re: [PATCH v3 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation

Hi Christoph, On 12 October 2016 at 16:08, Christoph Lameter wrote: > On Wed, 12 Oct 2016, Michael Kerrisk (man-pages) wrote: > >> > +arguments must specify the empty set. If the "local node" is low >> > +on free memory the kernel will try to allocate memory from other >> >

Re: [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue

On Wed, Oct 12, 2016 at 07:33:07PM +0530, Nadim Almas wrote: > >Someone else already sent this same patch in before you, sorry > But sir how can i come to know that Someone else already sent > particular patch before sending that particular patch You can subscribe to the driverdev mailing list

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On 10/12/2016 06:35 AM, Thomas Gleixner wrote: > On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: >> > + /* >> > + * Setting ring 3 MONITOR/MWAIT for all threads >> > + * when CPU is Xeon Phi Family x200 >> > + * This can be disabled with phir3mwait=disable cmdline switch. >> > + * We preserve

Re: [PATCH v3 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation

Hi Christoph, On 12 October 2016 at 16:08, Christoph Lameter wrote: > On Wed, 12 Oct 2016, Michael Kerrisk (man-pages) wrote: > >> > +arguments must specify the empty set. If the "local node" is low >> > +on free memory the kernel will try to allocate memory from other >> > +nodes. The kernel

Re: [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue

On Wed, Oct 12, 2016 at 07:33:07PM +0530, Nadim Almas wrote: > >Someone else already sent this same patch in before you, sorry > But sir how can i come to know that Someone else already sent > particular patch before sending that particular patch You can subscribe to the driverdev mailing list

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On 10/12/2016 06:35 AM, Thomas Gleixner wrote: > On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: >> > + /* >> > + * Setting ring 3 MONITOR/MWAIT for all threads >> > + * when CPU is Xeon Phi Family x200 >> > + * This can be disabled with phir3mwait=disable cmdline switch. >> > + * We preserve

Re: [RFC PATCH 1/1] mm/vmalloc.c: correct logic errors when insert vmap_area

[Let's CC Nick who has written this code] On Wed 12-10-16 22:30:13, zijun_hu wrote: > From: zijun_hu > > the KVA allocator organizes vmap_areas allocated by rbtree. in order to > insert a new vmap_area @i_va into the rbtree, walk around the rbtree from > root and compare the

Re: [RFC PATCH 1/1] mm/vmalloc.c: correct logic errors when insert vmap_area

[Let's CC Nick who has written this code] On Wed 12-10-16 22:30:13, zijun_hu wrote: > From: zijun_hu > > the KVA allocator organizes vmap_areas allocated by rbtree. in order to > insert a new vmap_area @i_va into the rbtree, walk around the rbtree from > root and compare the vmap_area @t_va met

[PATCH 09/34] [media] DaVinci-VPBE: Reduce the scope for a variable in vpbe_set_default_output()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:54:26 +0200 * Move the definition for the variable "ret" into an if branch so that an extra initialisation can be avoided at the beginning by this refactoring. * Return a success code as a constant at the end.

[PATCH] arch/x86: Remove second call to topology_update_package_map()

This was noticed during the investigation of http://git.kernel.org/tip/2a51fe083eba7f99cbda72f5ef90cdf2f4df882c A note for reviewers on the cleanup in smp_init_package_map(): The per_cpu variable x86_bios_cpu_apicid is initialized to BAD_APICID, and the bitmaps are set to false by default so the

[PATCH 09/34] [media] DaVinci-VPBE: Reduce the scope for a variable in vpbe_set_default_output()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:54:26 +0200 * Move the definition for the variable "ret" into an if branch so that an extra initialisation can be avoided at the beginning by this refactoring. * Return a success code as a constant at the end. Signed-off-by: Markus Elfring

[PATCH] arch/x86: Remove second call to topology_update_package_map()

This was noticed during the investigation of http://git.kernel.org/tip/2a51fe083eba7f99cbda72f5ef90cdf2f4df882c A note for reviewers on the cleanup in smp_init_package_map(): The per_cpu variable x86_bios_cpu_apicid is initialized to BAD_APICID, and the bitmaps are set to false by default so the

[PATCH 08/34] [media] DaVinci-VPBE: Return the success indication only as a constant in vpbe_set_mode()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:51:29 +0200 * Return a success code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

[PATCH 08/34] [media] DaVinci-VPBE: Return the success indication only as a constant in vpbe_set_mode()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:51:29 +0200 * Return a success code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- drivers/media/platform/davinci/vpbe.c | 4

Re: btrfs bio linked list corruption.

On 10/12/2016 10:40 AM, Dave Jones wrote: On Wed, Oct 12, 2016 at 09:47:17AM -0400, Dave Jones wrote: > On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > > This is from Linus' current tree, with Al's iovec fixups on

Re: btrfs bio linked list corruption.

On 10/12/2016 10:40 AM, Dave Jones wrote: On Wed, Oct 12, 2016 at 09:47:17AM -0400, Dave Jones wrote: > On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > > This is from Linus' current tree, with Al's iovec fixups on

[PATCH 07/34] [media] DaVinci-VPBE: Delete an unnecessary variable initialisation in vpbe_initialize()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:45:39 +0200 The local variable "ret" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 07/34] [media] DaVinci-VPBE: Delete an unnecessary variable initialisation in vpbe_initialize()

From: Markus Elfring Date: Wed, 12 Oct 2016 09:45:39 +0200 The local variable "ret" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring --- drivers/media/platform/davinci/vpbe.c | 2 +- 1 file changed, 1

Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)

On Wed, 12 Oct 2016, Paul Bolle wrote: > On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote: >> Bisecting the offending commit between v4.8 and v4.8.1 would be a good >> start. > > That would be between v4.7 and v4.8. (I guess my report was ambiguous.) > > That might

Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)

On Wed, 12 Oct 2016, Paul Bolle wrote: > On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote: >> Bisecting the offending commit between v4.8 and v4.8.1 would be a good >> start. > > That would be between v4.7 and v4.8. (I guess my report was ambiguous.) > > That might take some time. Because

[PATCH 04/34] [media] DaVinci-VPBE: Combine substrings for four messages

From: Markus Elfring Date: Tue, 11 Oct 2016 13:40:14 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: quoted string split across lines Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 04/34] [media] DaVinci-VPBE: Combine substrings for four messages

From: Markus Elfring Date: Tue, 11 Oct 2016 13:40:14 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: quoted string split across lines Thus fix the affected source code places. Signed-off-by: Markus Elfring --- drivers/media/platform/davinci/vpbe.c | 18

Re: [PATCH] ext4: super.c: Update logging style using PR_CONT

On Wed, 2016-10-12 at 12:41 +0200, Jan Kara wrote: > On Tue 11-10-16 18:57:58, Joe Perches wrote: > > Recent commit require line continuing printks to use PR_CONT. > > > > Update super.c to use PR_CONT and use vsprintf extension %pV > > to avoid a printk/vprintk/printk("\n") sequence as well. >

Re: [PATCH] ext4: super.c: Update logging style using PR_CONT

On Wed, 2016-10-12 at 12:41 +0200, Jan Kara wrote: > On Tue 11-10-16 18:57:58, Joe Perches wrote: > > Recent commit require line continuing printks to use PR_CONT. > > > > Update super.c to use PR_CONT and use vsprintf extension %pV > > to avoid a printk/vprintk/printk("\n") sequence as well. >

[PATCH 02/34] [media] DaVinci-VPBE: Delete two error messages for a failed memory allocation

From: Markus Elfring Date: Tue, 11 Oct 2016 09:56:13 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus remove such a logging statement in two functions. Link:

[PATCH 02/34] [media] DaVinci-VPBE: Delete two error messages for a failed memory allocation

From: Markus Elfring Date: Tue, 11 Oct 2016 09:56:13 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus remove such a logging statement in two functions. Link:

[RFC PATCH 1/1] mm/vmalloc.c: correct logic errors when insert vmap_area

From: zijun_hu the KVA allocator organizes vmap_areas allocated by rbtree. in order to insert a new vmap_area @i_va into the rbtree, walk around the rbtree from root and compare the vmap_area @t_va met on the rbtree against @i_va; walk toward the left branch of @t_va if @i_va

[RFC PATCH 1/1] mm/vmalloc.c: correct logic errors when insert vmap_area

From: zijun_hu the KVA allocator organizes vmap_areas allocated by rbtree. in order to insert a new vmap_area @i_va into the rbtree, walk around the rbtree from root and compare the vmap_area @t_va met on the rbtree against @i_va; walk toward the left branch of @t_va if @i_va is lower than

Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Wed, 12 Oct 2016, Emil Velikov wrote: > On 11 October 2016 at 10:33, Jani Nikula wrote: >> On Tue, 11 Oct 2016, "Sun, Jing A" wrote: >>> It's needed that DRM Driver module could be removed and reloaded after >>>

Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Wed, 12 Oct 2016, Emil Velikov wrote: > On 11 October 2016 at 10:33, Jani Nikula wrote: >> On Tue, 11 Oct 2016, "Sun, Jing A" wrote: >>> It's needed that DRM Driver module could be removed and reloaded after >>> kernel booting on the projects that I have been working on, and I hope >>> such

[PATCH 01/34] [media] DaVinci-VPBE: Use kmalloc_array() in vpbe_initialize()

From: Markus Elfring Date: Tue, 11 Oct 2016 09:40:41 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 01/34] [media] DaVinci-VPBE: Use kmalloc_array() in vpbe_initialize()

From: Markus Elfring Date: Tue, 11 Oct 2016 09:40:41 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 00/34] [media] DaVinci-Video Processing: Fine-tuning for several function implementations

From: Markus Elfring Date: Wed, 12 Oct 2016 16:20:02 +0200 Several update suggestions were taken into account from static source code analysis. Markus Elfring (34): Use kmalloc_array() in vpbe_initialize() Delete two error messages for a failed memory

[PATCH 00/34] [media] DaVinci-Video Processing: Fine-tuning for several function implementations

From: Markus Elfring Date: Wed, 12 Oct 2016 16:20:02 +0200 Several update suggestions were taken into account from static source code analysis. Markus Elfring (34): Use kmalloc_array() in vpbe_initialize() Delete two error messages for a failed memory allocation Adjust 16 checks for null

Re: [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7)

> > Can you elaborate on how exactly it kills your system? > > the last time I saw it it was a NULL deref at > ieee80211_aes_ccm_decrypt. Hm. I was expecting something within the crypto code would cause the crash, this seems strange. Anyway, I'm surely out of my depth wrt. the actual cause.

Re: [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7)

> > Can you elaborate on how exactly it kills your system? > > the last time I saw it it was a NULL deref at > ieee80211_aes_ccm_decrypt. Hm. I was expecting something within the crypto code would cause the crash, this seems strange. Anyway, I'm surely out of my depth wrt. the actual cause.

Re: [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue

>Someone else already sent this same patch in before you, sorry But sir how can i come to know that Someone else already sent particular patch before sending that particular patch On Wed, Oct 12, 2016 at 6:55 PM, Greg KH wrote: > On Tue, Oct 11, 2016 at 12:49:54PM -0700, Nadim

Re: [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue

>Someone else already sent this same patch in before you, sorry But sir how can i come to know that Someone else already sent particular patch before sending that particular patch On Wed, Oct 12, 2016 at 6:55 PM, Greg KH wrote: > On Tue, Oct 11, 2016 at 12:49:54PM -0700, Nadim Almas wrote: >>

Re: [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7)

Hello, On (10/12/16 11:05), Johannes Berg wrote: > Sorry - I meant to look into this yesterday but forgot. > > > Andy, can this be related to CONFIG_VMAP_STACK? > > I think it is. yeah, the system works fine with !CONFIG_VMAP_STACK. > > > current -git kills my system. > > Can you elaborate

Re: [mac80211] BUG_ON with current -git (4.8.0-11417-g24532f7)

Hello, On (10/12/16 11:05), Johannes Berg wrote: > Sorry - I meant to look into this yesterday but forgot. > > > Andy, can this be related to CONFIG_VMAP_STACK? > > I think it is. yeah, the system works fine with !CONFIG_VMAP_STACK. > > > current -git kills my system. > > Can you elaborate

Re: [git pull] vfs pile 1 (splice)

On Mon, 10 Oct 2016, Linus Torvalds wrote: > But the fact that it reacts _so_ badly to double-freeing issues when > the freelist has become corrupted due to an object being free'd and > then modified is clearly very fragile and not great. Yup that is why the debug options move the freepointer

Re: [git pull] vfs pile 1 (splice)

On Mon, 10 Oct 2016, Linus Torvalds wrote: > But the fact that it reacts _so_ badly to double-freeing issues when > the freelist has become corrupted due to an object being free'd and > then modified is clearly very fragile and not great. Yup that is why the debug options move the freepointer

Re: [PATCH v3 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation

On Wed, 12 Oct 2016, Michael Kerrisk (man-pages) wrote: > > +arguments must specify the empty set. If the "local node" is low > > +on free memory the kernel will try to allocate memory from other > > +nodes. The kernel will allocate memory from the "local node" > > +whenever memory for this node

Re: [PATCH v3 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation

On Wed, 12 Oct 2016, Michael Kerrisk (man-pages) wrote: > > +arguments must specify the empty set. If the "local node" is low > > +on free memory the kernel will try to allocate memory from other > > +nodes. The kernel will allocate memory from the "local node" > > +whenever memory for this node

Re: [PATCH v15 03/15] selftests/powerpc: Add ptrace tests for EBB

On Fri, Oct 07, 2016 at 08:44:48AM +1100, Michael Ellerman wrote: > wei.guo.si...@gmail.com writes: > > > From: Anshuman Khandual > > > > This patch adds ptrace interface test for EBB/PMU specific > > registers. This also adds some generic ptrace interface > > based

Re: [PATCH v15 03/15] selftests/powerpc: Add ptrace tests for EBB

On Fri, Oct 07, 2016 at 08:44:48AM +1100, Michael Ellerman wrote: > wei.guo.si...@gmail.com writes: > > > From: Anshuman Khandual > > > > This patch adds ptrace interface test for EBB/PMU specific > > registers. This also adds some generic ptrace interface > > based helper functions to be used

Re: [PATCH] kvm: x86: correct the misleading comment in vmx_handle_external_intr

2016-10-12 09:15+0800, Longpeng (Mike): > On 2016/10/12 2:23, Radim Krčmář wrote: >> This part is acceptable as it gives a new information code, yet the >> function does not modify flags, which makes it unremarkable. >> And dependencies on the caller would be better described in a header >> (if we

Re: [PATCH] kvm: x86: correct the misleading comment in vmx_handle_external_intr

2016-10-12 09:15+0800, Longpeng (Mike): > On 2016/10/12 2:23, Radim Krčmář wrote: >> This part is acceptable as it gives a new information code, yet the >> function does not modify flags, which makes it unremarkable. >> And dependencies on the caller would be better described in a header >> (if we

false checkpatch finding?

<4.8 tree>/scripts/checkpatch.pl -F foo.h WARNING: Missing a blank line after declarations #3: FILE: foo.h:3: + unsigned long f1; + volatile __le64 f2. WARNING: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt #3: FILE: foo.h:3: + volatile

false checkpatch finding?

<4.8 tree>/scripts/checkpatch.pl -F foo.h WARNING: Missing a blank line after declarations #3: FILE: foo.h:3: + unsigned long f1; + volatile __le64 f2. WARNING: Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt #3: FILE: foo.h:3: + volatile

pre 4.9-rc dma regression, imx6 sound etc

Hi! Bisected that commit 5881826 - "dmaengine: imx-sdma - update the residue calculation for cyclic channels" is first bad commit to cause audio regression on imx6q, sgtl5000 codec. It causes audible disturbing background noise when playing wavs. Unfortunately, reverting only 5881826

pre 4.9-rc dma regression, imx6 sound etc

Hi! Bisected that commit 5881826 - "dmaengine: imx-sdma - update the residue calculation for cyclic channels" is first bad commit to cause audio regression on imx6q, sgtl5000 codec. It causes audible disturbing background noise when playing wavs. Unfortunately, reverting only 5881826

Re: [PATCH v3 05/11] x86/tracing: fix compat syscall handling

On Tue, 11 Oct 2016, Marcin Nowakowski wrote: > -/* > - * Because ia32 syscalls do not map to x86_64 syscall numbers > - * this screws up the trace output when tracing a ia32 task. > - * Instead of reporting bogus syscalls, just do not trace them. > - * > - * If the user really wants these, then

Re: [PATCH v3 05/11] x86/tracing: fix compat syscall handling

On Tue, 11 Oct 2016, Marcin Nowakowski wrote: > -/* > - * Because ia32 syscalls do not map to x86_64 syscall numbers > - * this screws up the trace output when tracing a ia32 task. > - * Instead of reporting bogus syscalls, just do not trace them. > - * > - * If the user really wants these, then

Re: [PATCH v2 3/4] Add hwcap2 for x86

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > +/* HWCAP2 supplies kernel enabled CPU feature, so that the application > + can know that it can safely use them. The bits are defined in > + uapi/asm/hwcap.h. */ Please read: http://lkml.iu.edu/hypermail/linux/kernel/1607.1/00627.html

Re: [PATCH v2 3/4] Add hwcap2 for x86

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > +/* HWCAP2 supplies kernel enabled CPU feature, so that the application > + can know that it can safely use them. The bits are defined in > + uapi/asm/hwcap.h. */ Please read: http://lkml.iu.edu/hypermail/linux/kernel/1607.1/00627.html

Re: [PATCH v2 3/4] Add hwcap2 for x86

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > +extern unsigned int elf_hwcap2; > +unsigned elf_hwcap2 __read_mostly; Oh well. Getting two lines straight is hard, right? Thanks, tglx

Re: [PATCH v2 3/4] Add hwcap2 for x86

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > +extern unsigned int elf_hwcap2; > +unsigned elf_hwcap2 __read_mostly; Oh well. Getting two lines straight is hard, right? Thanks, tglx

[PATCH (net.git) 2/2] stmmac: fix error check when init ptp

This patch fixes a problem when propagated the failure of ptp_clock_register to open function. Signed-off-by: Giuseppe Cavallaro Cc: Alexandre TORGUE Cc: Rayagond Kokatanur ---

[PATCH (net.git) 2/2] stmmac: fix error check when init ptp

This patch fixes a problem when propagated the failure of ptp_clock_register to open function. Signed-off-by: Giuseppe Cavallaro Cc: Alexandre TORGUE Cc: Rayagond Kokatanur --- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++-- drivers/net/ethernet/stmicro/stmmac/stmmac_ptp.c | 10

[PATCH (net.git) 1/2] stmmac: fix ptp init for gmac4

The gmac 4.x version has not extended descriptors (that are available on 3.x instead of). While initializing the PTP module, the advanced PTP was enabled in case of extended descriptors. This cannot be applied for 4.x version where only the hardware capability register has to show if the feature

[PATCH (net.git) 1/2] stmmac: fix ptp init for gmac4

The gmac 4.x version has not extended descriptors (that are available on 3.x instead of). While initializing the PTP module, the advanced PTP was enabled in case of extended descriptors. This cannot be applied for 4.x version where only the hardware capability register has to show if the feature

Re: btrfs bio linked list corruption.

On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > This is from Linus' current tree, with Al's iovec fixups on top. > > > > [ cut here ] > > WARNING: CPU: 1 PID: 3673 at lib/list_debug.c:33

Re: btrfs bio linked list corruption.

On Tue, Oct 11, 2016 at 11:54:09AM -0400, Chris Mason wrote: > > > On 10/11/2016 10:45 AM, Dave Jones wrote: > > This is from Linus' current tree, with Al's iovec fixups on top. > > > > [ cut here ] > > WARNING: CPU: 1 PID: 3673 at lib/list_debug.c:33

Re: [PATCH 3.4 081/125] mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't make any progress

On Wed 12-10-16 20:33:17, l...@kernel.org wrote: > From: Michal Hocko > > 3.4.113-rc1 review patch. If anyone has any objections, please let me know. Do not forget to take the follow up fix 564e81a57f97 ("mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make any

Re: [PATCH 3.4 081/125] mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't make any progress

On Wed 12-10-16 20:33:17, l...@kernel.org wrote: > From: Michal Hocko > > 3.4.113-rc1 review patch. If anyone has any objections, please let me know. Do not forget to take the follow up fix 564e81a57f97 ("mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make any progress") > >

ATENCIÓN;

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

ATENCIÓN;

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > > +static int phir3mwait = 1; > +static int __init phir3mwait_disable(char *value) Can someone @Intel please tell everyone to stop this annoying habit of glueing variable declarations without a newline to the function? And the variable should be

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > + /* > + * Setting ring 3 MONITOR/MWAIT for all threads > + * when CPU is Xeon Phi Family x200 > + * This can be disabled with phir3mwait=disable cmdline switch. > + * We preserve the reserved values and set only 2nd bit. > +

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > > +static int phir3mwait = 1; > +static int __init phir3mwait_disable(char *value) Can someone @Intel please tell everyone to stop this annoying habit of glueing variable declarations without a newline to the function? And the variable should be

Re: [PATCH v2 2/4] Add enabling of the R3 MWAIT during boot for KNL

On Wed, 12 Oct 2016, Grzegorz Andrejczuk wrote: > + /* > + * Setting ring 3 MONITOR/MWAIT for all threads > + * when CPU is Xeon Phi Family x200 > + * This can be disabled with phir3mwait=disable cmdline switch. > + * We preserve the reserved values and set only 2nd bit. > +

[PATCH v14 11/16] vfio/type1: Implement recursive vfio_find_dma_from_node

This patch handles the case where a node is encountered, matching @start and @size arguments but not matching the @type argument. In that case, we need to skip that node and pursue the search in the node's leaves. In case @start is inferior to the node's base, we resume the search on the left

[POC/RFC PATCH] overlayfs: fix data inconsistency at copy up

This is a proof of concept patch to fix the following. /ovl is in overlay mount and /ovl/foo exists on the lower layer only. rofd = open("/ovl/foo", O_RDONLY); rwfd = open("/ovl/foo", O_WRONLY); /* this causes copy up */ write(rwfd, "bar", 3); read(rofd, buf, 3); assert(memcmp(buf, "bar",

[PATCH v14 09/16] vfio: Introduce a vfio_dma type field

We introduce a vfio_dma type since we will need to discriminate different types of dma slots: - VFIO_IOVA_USER: IOVA region used to map user vaddr - VFIO_IOVA_RESERVED_MSI: IOVA region reserved to map MSI doorbells Signed-off-by: Eric Auger Acked-by: Alex Williamson

[PATCH v14 12/16] vfio/type1: Handle unmap/unpin and replay for VFIO_IOVA_RESERVED slots

Before allowing the end-user to create VFIO_IOVA_RESERVED dma slots, let's implement the expected behavior for removal and replay. As opposed to user dma slots, reserved IOVAs are not systematically bound to PAs and PAs are not pinned. VFIO just initializes the IOVA "aperture". IOVAs are

[PATCH v14 11/16] vfio/type1: Implement recursive vfio_find_dma_from_node

This patch handles the case where a node is encountered, matching @start and @size arguments but not matching the @type argument. In that case, we need to skip that node and pursue the search in the node's leaves. In case @start is inferior to the node's base, we resume the search on the left

[POC/RFC PATCH] overlayfs: fix data inconsistency at copy up

This is a proof of concept patch to fix the following. /ovl is in overlay mount and /ovl/foo exists on the lower layer only. rofd = open("/ovl/foo", O_RDONLY); rwfd = open("/ovl/foo", O_WRONLY); /* this causes copy up */ write(rwfd, "bar", 3); read(rofd, buf, 3); assert(memcmp(buf, "bar",

[PATCH v14 09/16] vfio: Introduce a vfio_dma type field

We introduce a vfio_dma type since we will need to discriminate different types of dma slots: - VFIO_IOVA_USER: IOVA region used to map user vaddr - VFIO_IOVA_RESERVED_MSI: IOVA region reserved to map MSI doorbells Signed-off-by: Eric Auger Acked-by: Alex Williamson --- v9 -> v10: - renamed

[PATCH v14 12/16] vfio/type1: Handle unmap/unpin and replay for VFIO_IOVA_RESERVED slots

Before allowing the end-user to create VFIO_IOVA_RESERVED dma slots, let's implement the expected behavior for removal and replay. As opposed to user dma slots, reserved IOVAs are not systematically bound to PAs and PAs are not pinned. VFIO just initializes the IOVA "aperture". IOVAs are

[PATCH v14 10/16] vfio/type1: vfio_find_dma accepting a type argument

In our RB-tree we get prepared to insert slots of different types (USER and RESERVED). It becomes useful to be able to search for dma slots of a specific type or any type. This patch introduces vfio_find_dma_from_node which starts the search from a given node and stops on the first node that

linux.git: printk() problem

Hello. I noticed that current linux.git generates hardly readable console output due to KERN_CONT changes. Are you suggesting developers that output like this be fixed? [ 93.723582] Mem-Info: [ 93.725919] active_anon:380970 inactive_anon:2098 isolated_anon:0 [ 93.725919] active_file:242

[PATCH v14 13/16] vfio: Allow reserved msi iova registration

The user is allowed to register a reserved MSI IOVA range by using the DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. This region is stored in the vfio_dma rb tree. At that point the iova range is not mapped to any target address yet. The host kernel will use those iova

[PATCH v14 10/16] vfio/type1: vfio_find_dma accepting a type argument

In our RB-tree we get prepared to insert slots of different types (USER and RESERVED). It becomes useful to be able to search for dma slots of a specific type or any type. This patch introduces vfio_find_dma_from_node which starts the search from a given node and stops on the first node that

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