[PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

There was no code for handling memory leaks of device_init_rings() and request_irq(). It needs to free allocated memory in the device_init_rings() , when request_irq() is failed. Add freeing sequences of irq and device init rings. Signed-off-by: Ji-Hun Kim --- It's

[PATCH v4 2/2] staging: vt6655: add handling memory leak on vnt_start()

There was no code for handling memory leaks of device_init_rings() and request_irq(). It needs to free allocated memory in the device_init_rings() , when request_irq() is failed. Add freeing sequences of irq and device init rings. Signed-off-by: Ji-Hun Kim --- It's additional memory leak

[PATCH] f2fs: remain written times to update inode during fsync

This fixes xfstests/generic/392. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 15 +++ fs/f2fs/inode.c | 4 2 files changed, 19 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 000f93f6767e..675c39d85111 100644 --- a/fs/f2fs/f2fs.h +++

[PATCH v4 1/2] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim

[PATCH] f2fs: remain written times to update inode during fsync

This fixes xfstests/generic/392. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 15 +++ fs/f2fs/inode.c | 4 2 files changed, 19 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 000f93f6767e..675c39d85111 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@

[PATCH v4 1/2] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim --- Changes

Re: General protection fault with use_blk_mq=1.

On 03/29/2018 02:12 AM, Zephaniah E. Loss-Cutler-Hull wrote: > On 03/28/2018 10:13 PM, Paolo Valente wrote: >> In addition, the outcome of your attempt without >> CONFIG_DEBUG_BLK_CGROUP would give us useful bisection information: >> - if no failure occurs, then the issue is likely to be confined

Re: General protection fault with use_blk_mq=1.

On 03/29/2018 02:12 AM, Zephaniah E. Loss-Cutler-Hull wrote: > On 03/28/2018 10:13 PM, Paolo Valente wrote: >> In addition, the outcome of your attempt without >> CONFIG_DEBUG_BLK_CGROUP would give us useful bisection information: >> - if no failure occurs, then the issue is likely to be confined

Re: [PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length.

On (03/29/18 15:56), Maninder Singh wrote: > Hello Nick/Sergey, > > Any suggestion or comments, so that we can change code and resend the patch? Well... there were no replies to https://marc.info/?l=linux-kernel=152161450026771=2 and https://marc.info/?l=linux-kernel=152161860627974=2

Re: [PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length.

On (03/29/18 15:56), Maninder Singh wrote: > Hello Nick/Sergey, > > Any suggestion or comments, so that we can change code and resend the patch? Well... there were no replies to https://marc.info/?l=linux-kernel=152161450026771=2 and https://marc.info/?l=linux-kernel=152161860627974=2

Re: [PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

2018-03-29 11:19 GMT+09:00 Ulf Magnusson :. >> %% >> +static void expand_string(const char *in) >> +{ >> + char *p, *q; >> + >> + p = expand_string_value(in); >> + >> + q = p + strlen(p); >> + while (q > p) >> + unput(*--q); >> + >> +

Re: [PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

2018-03-29 11:19 GMT+09:00 Ulf Magnusson :. >> %% >> +static void expand_string(const char *in) >> +{ >> + char *p, *q; >> + >> + p = expand_string_value(in); >> + >> + q = p + strlen(p); >> + while (q > p) >> + unput(*--q); >> + >> + free(p); >> +} >>

Re: [GIT PULL] sound fixes for 4.16-final

On Thu, Mar 29, 2018 at 4:23 AM, Takashi Iwai wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git > tags/sound-4.16 No such tag. Forgot to push? There's the "for-linus" branch that matches the commit id you stated, but no tags that point to it.. Hmm?

Re: [GIT PULL] sound fixes for 4.16-final

On Thu, Mar 29, 2018 at 4:23 AM, Takashi Iwai wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git > tags/sound-4.16 No such tag. Forgot to push? There's the "for-linus" branch that matches the commit id you stated, but no tags that point to it.. Hmm? Linus

Re: [RFC PATCH ghak32 V2 01/13] audit: add container id

On 2018-03-29 07:03, Jonathan Corbet wrote: > On Thu, 29 Mar 2018 05:01:32 -0400 > Richard Guy Briggs wrote: > > > > A little detail, but still... > > > > I am understanding that you would prefer more context (as opposed to > > operational detail) in the description, laying

Re: [RFC PATCH ghak32 V2 01/13] audit: add container id

On 2018-03-29 07:03, Jonathan Corbet wrote: > On Thu, 29 Mar 2018 05:01:32 -0400 > Richard Guy Briggs wrote: > > > > A little detail, but still... > > > > I am understanding that you would prefer more context (as opposed to > > operational detail) in the description, laying out the use case

[PATCH] mm: limit a process RSS

we cannot limit a process RSS although there is ulimit -m, not sure why and when ulimit -m is not working, make it work similar requirement: https://stackoverflow.com/questions/3360348/why-ulimit-cant-limit-resident-memory-successfully-and-how Signed-off-by: Li RongQing

[PATCH] mm: limit a process RSS

we cannot limit a process RSS although there is ulimit -m, not sure why and when ulimit -m is not working, make it work similar requirement: https://stackoverflow.com/questions/3360348/why-ulimit-cant-limit-resident-memory-successfully-and-how Signed-off-by: Li RongQing --- mm/memory.c | 14

[PATCH v5 3/3] perf script: extend misc field decoding with switch out event type

Append 'p' sign to 'S' tag designating the type of context switch out event so 'Sp' means preemption context switch. Documentation is extended to cover new presentation changes. perf script --show-switch-events -F +misc -I -i perf.data: hdparm 4073 [004] U 762.198265:

[PATCH v5 3/3] perf script: extend misc field decoding with switch out event type

Append 'p' sign to 'S' tag designating the type of context switch out event so 'Sp' means preemption context switch. Documentation is extended to cover new presentation changes. perf script --show-switch-events -F +misc -I -i perf.data: hdparm 4073 [004] U 762.198265:

[PATCH v5 2/3] perf report: extend raw dump (-D) out with switch out event type

Print additional 'preempt' tag for PERF_RECORD_SWITCH[_CPU_WIDE] OUT records when event header misc field contains PERF_RECORD_MISC_SWITCH_OUT_PREEMPT bit set designating preemption context switch out event: tools/perf/perf report -D -i perf.data | grep _SWITCH 0 768361415226 0x27f076 [0x28]:

[PATCH v5 2/3] perf report: extend raw dump (-D) out with switch out event type

Print additional 'preempt' tag for PERF_RECORD_SWITCH[_CPU_WIDE] OUT records when event header misc field contains PERF_RECORD_MISC_SWITCH_OUT_PREEMPT bit set designating preemption context switch out event: tools/perf/perf report -D -i perf.data | grep _SWITCH 0 768361415226 0x27f076 [0x28]:

[RFC PATCH] lib/ioremap: Avoid triggering BUG_ON when end is not PAGE_ALIGN

Zhou reported a bug on Hisilicon arm64 D06 platform with 64KB page size: [2.470908] kernel BUG at lib/ioremap.c:72! [2.475079] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [2.480551] Modules linked in: [2.483594] CPU: 1 PID: 1 Comm: swapper/0 Not tainted

[RFC PATCH] lib/ioremap: Avoid triggering BUG_ON when end is not PAGE_ALIGN

Zhou reported a bug on Hisilicon arm64 D06 platform with 64KB page size: [2.470908] kernel BUG at lib/ioremap.c:72! [2.475079] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [2.480551] Modules linked in: [2.483594] CPU: 1 PID: 1 Comm: swapper/0 Not tainted

[PATCH v5 1/3] perf/core: store context switch out type into Perf trace

Store preempting context switch out event into Perf trace as a part of PERF_RECORD_SWITCH[_CPU_WIDE] record. Percentage of preempting and non-preempting context switches help understanding the nature of workloads (CPU or IO bound) that are running on a machine; The event is treated as

[PATCH v5 1/3] perf/core: store context switch out type into Perf trace

Store preempting context switch out event into Perf trace as a part of PERF_RECORD_SWITCH[_CPU_WIDE] record. Percentage of preempting and non-preempting context switches help understanding the nature of workloads (CPU or IO bound) that are running on a machine; The event is treated as

Re: [PATCH] nvme-multipath: implement active-active round-robin path selector

2018-03-29 4:47 GMT+09:00 Keith Busch : > On Wed, Mar 28, 2018 at 10:06:46AM +0200, Christoph Hellwig wrote: >> For PCIe devices the right policy is not a round robin but to use >> the pcie device closer to the node. I did a prototype for that >> long ago and the concept

Re: [PATCH] nvme-multipath: implement active-active round-robin path selector

2018-03-29 4:47 GMT+09:00 Keith Busch : > On Wed, Mar 28, 2018 at 10:06:46AM +0200, Christoph Hellwig wrote: >> For PCIe devices the right policy is not a round robin but to use >> the pcie device closer to the node. I did a prototype for that >> long ago and the concept can work. Can you look

[PATCH v5 0/3] perf/core: expose thread context switch out event type to user space

Implement preempting context switch out event as a part of PERF_RECORD_SWITCH[_CPU_WIDE] record. The event is treated as preemption one when task->state value of the thread being switched out is TASK_RUNNING; Percentage of preempting and non-preempting context switches help understanding the

[PATCH v5 0/3] perf/core: expose thread context switch out event type to user space

Implement preempting context switch out event as a part of PERF_RECORD_SWITCH[_CPU_WIDE] record. The event is treated as preemption one when task->state value of the thread being switched out is TASK_RUNNING; Percentage of preempting and non-preempting context switches help understanding the

[PATCH] RDMA/ucma: reject AF_IB ip multicast requests

syzbot discovered that ucma_join_ip_multicast() mishandles AF_IB request addresses. If an RDMA_USER_CM_CMD_JOIN_IP_MCAST request has cmd.addr.sa_family=AF_IB then ucma_join_ip_multicast() reads beyond the end of its cmd.addr. Reject non IP RDMA_USER_CM_CMD_JOIN_IP_MCAST requests.

[PATCH] RDMA/ucma: reject AF_IB ip multicast requests

syzbot discovered that ucma_join_ip_multicast() mishandles AF_IB request addresses. If an RDMA_USER_CM_CMD_JOIN_IP_MCAST request has cmd.addr.sa_family=AF_IB then ucma_join_ip_multicast() reads beyond the end of its cmd.addr. Reject non IP RDMA_USER_CM_CMD_JOIN_IP_MCAST requests.

[PATCH v3] kbuild: use -fmacro-prefix-map to make __FILE__ a relative path

The __FILE__ macro is used everywhere in the kernel to locate the file printing the log message, such as WARN_ON(), etc. If the kernel is built out of tree, this can be a long absolute path, like this: WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:... This is

[PATCH v3] kbuild: use -fmacro-prefix-map to make __FILE__ a relative path

The __FILE__ macro is used everywhere in the kernel to locate the file printing the log message, such as WARN_ON(), etc. If the kernel is built out of tree, this can be a long absolute path, like this: WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:... This is

Re: [PATCH 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU

On 3/29/2018 5:54 PM, Gary R Hook wrote: > Implement a skeleton framework for debugfs support in the > AMD IOMMU. > > > Signed-off-by: Gary R Hook > --- > drivers/iommu/Kconfig |6 ++--- > drivers/iommu/Makefile|2 +- >

Re: [PATCH 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU

On 3/29/2018 5:54 PM, Gary R Hook wrote: > Implement a skeleton framework for debugfs support in the > AMD IOMMU. > > > Signed-off-by: Gary R Hook > --- > drivers/iommu/Kconfig |6 ++--- > drivers/iommu/Makefile|2 +- > drivers/iommu/amd_iommu_debugfs.c | 47

Re: linux-next 20180327 - "SELinux: (dev dm-3, type ext4) getxattr errno 34"

On Thu, 29 Mar 2018 21:32:21 -0400, "Theodore Y. Ts'o" said: > Yes, the breakage is my fault; my apologies. The new version of the > patch is already posted in bugzilla (and on linux-ext4). I'll be > pushing out a refreshed ext4.git branch shortly. Confirming that reverting

Re: linux-next 20180327 - "SELinux: (dev dm-3, type ext4) getxattr errno 34"

On Thu, 29 Mar 2018 21:32:21 -0400, "Theodore Y. Ts'o" said: > Yes, the breakage is my fault; my apologies. The new version of the > patch is already posted in bugzilla (and on linux-ext4). I'll be > pushing out a refreshed ext4.git branch shortly. Confirming that reverting

Re: [PATCH 1/2] iommu - Enable debugfs exposure of the IOMMU

On 3/29/2018 5:54 PM, Gary R Hook wrote: > Provide base enablement for using debugfs to expose internal data of > an IOMMU driver. When enabled, create the /sys/kernel/debug/iommu So this can't actually create anything yet since nothing invokes the function. Maybe describe how it should be used

Re: [PATCH 1/2] iommu - Enable debugfs exposure of the IOMMU

On 3/29/2018 5:54 PM, Gary R Hook wrote: > Provide base enablement for using debugfs to expose internal data of > an IOMMU driver. When enabled, create the /sys/kernel/debug/iommu So this can't actually create anything yet since nothing invokes the function. Maybe describe how it should be used

[PATCH 0/2] add thermal monitor support for UniPhier PXs3 SoC

Add support for thermal monitor implemented on UniPhier PXs3 SoC. Kunihiko Hayashi (2): dt-bindings: thermal: uniphier: add a compatible string for PXs3 thermal: uniphier: add UniPhier PXs3 support Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 +

[PATCH 2/2] thermal: uniphier: add UniPhier PXs3 support

Add support for UniPhier PXs3 SoC. It is equivalent to LD20. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/uniphier_thermal.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/thermal/uniphier_thermal.c b/drivers/thermal/uniphier_thermal.c

[PATCH 1/2] dt-bindings: thermal: uniphier: add a compatible string for PXs3

Add a compatible string for thermal monitor implemented on UniPhier PXs3 SoC. Signed-off-by: Kunihiko Hayashi --- Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/2] thermal: uniphier: add UniPhier PXs3 support

Add support for UniPhier PXs3 SoC. It is equivalent to LD20. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/uniphier_thermal.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/thermal/uniphier_thermal.c b/drivers/thermal/uniphier_thermal.c index 9570473..55477d7 100644 ---

[PATCH 1/2] dt-bindings: thermal: uniphier: add a compatible string for PXs3

Add a compatible string for thermal monitor implemented on UniPhier PXs3 SoC. Signed-off-by: Kunihiko Hayashi --- Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/thermal/uniphier-thermal.txt

[PATCH 0/2] add thermal monitor support for UniPhier PXs3 SoC

Add support for thermal monitor implemented on UniPhier PXs3 SoC. Kunihiko Hayashi (2): dt-bindings: thermal: uniphier: add a compatible string for PXs3 thermal: uniphier: add UniPhier PXs3 support Documentation/devicetree/bindings/thermal/uniphier-thermal.txt | 1 +

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On 2018/3/30 11:39, Ji-Hun Kim wrote: On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: On 2018/3/30 10:44, Ji-Hun Kim wrote: @@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) } dev_dbg(>pcid->dev, "call device init rd0 ring\n"); -

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On 2018/3/30 11:39, Ji-Hun Kim wrote: On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: On 2018/3/30 10:44, Ji-Hun Kim wrote: @@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) } dev_dbg(>pcid->dev, "call device init rd0 ring\n"); -

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: > > > On 2018/3/30 10:44, Ji-Hun Kim wrote: > >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) > > } > > dev_dbg(>pcid->dev, "call device init rd0 ring\n"); > >-device_init_rd0_ring(priv); > >-

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: > > > On 2018/3/30 10:44, Ji-Hun Kim wrote: > >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) > > } > > dev_dbg(>pcid->dev, "call device init rd0 ring\n"); > >-device_init_rd0_ring(priv); > >-

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: > > > On 2018/3/30 10:44, Ji-Hun Kim wrote: > >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) > > } > > dev_dbg(>pcid->dev, "call device init rd0 ring\n"); > >-device_init_rd0_ring(priv); > >-

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On Fri, Mar 30, 2018 at 11:15:03AM +0800, Jia-Ju Bai wrote: > > > On 2018/3/30 10:44, Ji-Hun Kim wrote: > >@@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) > > } > > dev_dbg(>pcid->dev, "call device init rd0 ring\n"); > >-device_init_rd0_ring(priv); > >-

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Fri, Mar 30, 2018 at 12:05 AM, Steven Rostedt wrote: > On Thu, 29 Mar 2018 18:41:44 +0800 > Zhaoyang Huang wrote: > >> It is reported that some user app would like to echo a huge >> number to "/sys/kernel/debug/tracing/buffer_size_kb" regardless

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Fri, Mar 30, 2018 at 12:05 AM, Steven Rostedt wrote: > On Thu, 29 Mar 2018 18:41:44 +0800 > Zhaoyang Huang wrote: > >> It is reported that some user app would like to echo a huge >> number to "/sys/kernel/debug/tracing/buffer_size_kb" regardless >> of the available memory, which will cause

linux-next: Signed-off-by missing for commits in the spi-nor tree

Hi Cyrille, Commits 3efa50903ff3 ("mtd: fsl-quadspi: Distinguish the mtd device names") 85da6da22843 ("dt-bindings: fsl-quadspi: Add the example of two SPI NOR") are missing a Signed-off-by from their committer. P.S. should I be changing the contact I have for the spi-nor trees? --

linux-next: Signed-off-by missing for commits in the spi-nor tree

Hi Cyrille, Commits 3efa50903ff3 ("mtd: fsl-quadspi: Distinguish the mtd device names") 85da6da22843 ("dt-bindings: fsl-quadspi: Add the example of two SPI NOR") are missing a Signed-off-by from their committer. P.S. should I be changing the contact I have for the spi-nor trees? --

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

Hi Alison, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on v4.16-rc7] [also build test WARNING on next-20180329] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

Hi Alison, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on v4.16-rc7] [also build test WARNING on next-20180329] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH] MAINTAINERS: update entry for entry for ARM/berlin

Hi, On Thu, 29 Mar 2018 15:08:04 +0200 Andrew Lunn wrote: > On Thu, Mar 29, 2018 at 04:42:40PM +0800, Jisheng Zhang wrote: > > > > Change the entry name and move it to its alphabetical location. > > We move to ARM/Synaptics instead of ARM/Marvell. > > Hi Jisheng > > Please could you add

Re: [PATCH] MAINTAINERS: update entry for entry for ARM/berlin

Hi, On Thu, 29 Mar 2018 15:08:04 +0200 Andrew Lunn wrote: > On Thu, Mar 29, 2018 at 04:42:40PM +0800, Jisheng Zhang wrote: > > > > Change the entry name and move it to its alphabetical location. > > We move to ARM/Synaptics instead of ARM/Marvell. > > Hi Jisheng > > Please could you add

[PATCH v4 2/6] doc: Add documentation for Coresight panic kdump

Add detailed documentation for Coresight panic kdump, which contains the idea for why need Coresight panic kdump and introduce the implementation of Coresight panic kdump framework; the last section is to explain what's usage. Credits to Mathieu Poirier for many suggestions since the first

[PATCH v4 2/6] doc: Add documentation for Coresight panic kdump

Add detailed documentation for Coresight panic kdump, which contains the idea for why need Coresight panic kdump and introduce the implementation of Coresight panic kdump framework; the last section is to explain what's usage. Credits to Mathieu Poirier for many suggestions since the first

Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible

Hi Thomas, On Fri, Mar 09, 2018 at 04:08:19PM +0100, Thomas Gleixner wrote: > On Fri, 9 Mar 2018, Ming Lei wrote: > > On Fri, Mar 09, 2018 at 11:08:54AM +0100, Thomas Gleixner wrote: > > > > > So my understanding is that these irq patches are enhancements and > > > > > not bug > > > > > fixes.

[PATCH v4 3/6] coresight: Support panic kdump functionality

After kernel panic happens, Coresight tracing data has much useful info which can be used for analysis. For example, the trace info from ETB RAM can be used to check the CPU execution flows before the crash. So we can save the tracing data from sink devices, and rely on kdump to save DDR content

[PATCH v4 1/6] doc: Add Coresight documentation directory

For easy management and friendly adding more Coresight documentation, this commit creates a new directory: Documentation/trace/coresight. This commit also moves Coresight related docs into the new directory and updates MAINTAINERS file to reflect docs movement. Signed-off-by: Leo Yan

[PATCH v4 5/6] coresight: Set and clear sink device handler for kdump node

If Coresight path is enabled for specific CPU, the sink device handler need to be set to kdump node; on the other hand we also need to clear sink device handler when path is disabled. This patch sets sink devices handler for kdump node for two separate Coresight enabling modes: CS_MODE_SYSFS and

Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible

Hi Thomas, On Fri, Mar 09, 2018 at 04:08:19PM +0100, Thomas Gleixner wrote: > On Fri, 9 Mar 2018, Ming Lei wrote: > > On Fri, Mar 09, 2018 at 11:08:54AM +0100, Thomas Gleixner wrote: > > > > > So my understanding is that these irq patches are enhancements and > > > > > not bug > > > > > fixes.

[PATCH v4 3/6] coresight: Support panic kdump functionality

After kernel panic happens, Coresight tracing data has much useful info which can be used for analysis. For example, the trace info from ETB RAM can be used to check the CPU execution flows before the crash. So we can save the tracing data from sink devices, and rely on kdump to save DDR content

[PATCH v4 1/6] doc: Add Coresight documentation directory

For easy management and friendly adding more Coresight documentation, this commit creates a new directory: Documentation/trace/coresight. This commit also moves Coresight related docs into the new directory and updates MAINTAINERS file to reflect docs movement. Signed-off-by: Leo Yan ---

[PATCH v4 5/6] coresight: Set and clear sink device handler for kdump node

If Coresight path is enabled for specific CPU, the sink device handler need to be set to kdump node; on the other hand we also need to clear sink device handler when path is disabled. This patch sets sink devices handler for kdump node for two separate Coresight enabling modes: CS_MODE_SYSFS and

[PATCH v4 4/6] coresight: tmc: Hook callback for panic kdump

Since Coresight panic kdump functionality has been ready, this patch is to hook panic callback function for ETB/ETF driver. The driver data structure has allocated a buffer when the session started, so simply save tracing data into this buffer when panic happens and update buffer related info for

[PATCH v4 6/6] coresight: etm4x: Support panic kdump

ETMv4 hardware information and configuration needs to be saved as metadata; the metadata format should be compatible with 'perf' tool and finally is used by tracing data decoder. ETMv4 works as tracer per CPU, we cannot wait for gathering ETM info after CPU panic has happened in case there have

[PATCH v4 6/6] coresight: etm4x: Support panic kdump

ETMv4 hardware information and configuration needs to be saved as metadata; the metadata format should be compatible with 'perf' tool and finally is used by tracing data decoder. ETMv4 works as tracer per CPU, we cannot wait for gathering ETM info after CPU panic has happened in case there have

[PATCH v4 4/6] coresight: tmc: Hook callback for panic kdump

Since Coresight panic kdump functionality has been ready, this patch is to hook panic callback function for ETB/ETF driver. The driver data structure has allocated a buffer when the session started, so simply save tracing data into this buffer when panic happens and update buffer related info for

[PATCH v4 0/6] Coresight: Support panic kdump

This patch set is to explore Coresight tracing data for postmortem debugging. When kernel panic happens, the Coresight panic kdump can help to save on-chip tracing data and tracer metadata into DRAM, later relies on kdump and crash/perf tools to recovery tracing data for "offline" analysis. The

[PATCH v4 0/6] Coresight: Support panic kdump

This patch set is to explore Coresight tracing data for postmortem debugging. When kernel panic happens, the Coresight panic kdump can help to save on-chip tracing data and tracer metadata into DRAM, later relies on kdump and crash/perf tools to recovery tracing data for "offline" analysis. The

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On 2018/3/30 10:44, Ji-Hun Kim wrote: @@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) } dev_dbg(>pcid->dev, "call device init rd0 ring\n"); - device_init_rd0_ring(priv); - device_init_rd1_ring(priv); - device_init_td0_ring(priv); -

Re: [PATCH v3] staging: vt6655: check for memory allocation failures

On 2018/3/30 10:44, Ji-Hun Kim wrote: @@ -1165,10 +1205,18 @@ static int vnt_start(struct ieee80211_hw *hw) } dev_dbg(>pcid->dev, "call device init rd0 ring\n"); - device_init_rd0_ring(priv); - device_init_rd1_ring(priv); - device_init_td0_ring(priv); -

[PATCH v2] MAINTAINERS: update entry for ARM/berlin

Synaptics has acquired the Multimedia Solutions Business of Marvell[1]. So change the berlin entry name and move it to its alphabetical location. We move to ARM/Synaptics instead of ARM/Marvell. This patch also updates my email address from marvell to synaptics. [1]

[PATCH v2] MAINTAINERS: update entry for ARM/berlin

Synaptics has acquired the Multimedia Solutions Business of Marvell[1]. So change the berlin entry name and move it to its alphabetical location. We move to ARM/Synaptics instead of ARM/Marvell. This patch also updates my email address from marvell to synaptics. [1]

Re: [PATCH] xfs: always free inline data before resetting inode fork during ifree

On Thu, Mar 29, 2018 at 10:05:35AM +1100, Dave Chinner wrote: >On Wed, Mar 28, 2018 at 07:30:06PM +, Sasha Levin wrote: >> This is actually something I want maintainers to dictate. What sort of >> testing would make the XFS folks happy here? Right now I'm doing >> "./check 'xfs/*'" with

Re: [PATCH] xfs: always free inline data before resetting inode fork during ifree

On Thu, Mar 29, 2018 at 10:05:35AM +1100, Dave Chinner wrote: >On Wed, Mar 28, 2018 at 07:30:06PM +, Sasha Levin wrote: >> This is actually something I want maintainers to dictate. What sort of >> testing would make the XFS folks happy here? Right now I'm doing >> "./check 'xfs/*'" with

Re: [RFC PATCH V2 8/8] vhost: event suppression for packed ring

On 2018年03月30日 10:05, Tiwei Bie wrote: On Mon, Mar 26, 2018 at 11:38:53AM +0800, Jason Wang wrote: This patch introduces basic support for event suppression aka driver and device area. Compile tested only. Signed-off-by: Jason Wang --- [...] + +static bool

Re: [RFC PATCH V2 8/8] vhost: event suppression for packed ring

On 2018年03月30日 10:05, Tiwei Bie wrote: On Mon, Mar 26, 2018 at 11:38:53AM +0800, Jason Wang wrote: This patch introduces basic support for event suppression aka driver and device area. Compile tested only. Signed-off-by: Jason Wang --- [...] + +static bool vhost_notify_packed(struct

[PATCH v3] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim

[PATCH v3] staging: vt6655: check for memory allocation failures

There are no null pointer checking on rd_info and td_info values which are allocated by kzalloc. It has potential null pointer dereferencing issues. Implement error handling code on device_init_rd*, device_init_td* and vnt_start for the allocation failures. Signed-off-by: Ji-Hun Kim --- Changes

Re: [PATCH v5] ANDROID: binder: change down_write to down_read

On Fri, Mar 30, 2018 at 09:39:03AM +0800, Ganesh Mahendran wrote: > 2018-03-30 9:29 GMT+08:00 Minchan Kim : > > Hi Ganesh, > > > > On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote: > >> 2018-03-29 14:54 GMT+08:00 Minchan Kim : > >> >

Re: [PATCH v5] ANDROID: binder: change down_write to down_read

On Fri, Mar 30, 2018 at 09:39:03AM +0800, Ganesh Mahendran wrote: > 2018-03-30 9:29 GMT+08:00 Minchan Kim : > > Hi Ganesh, > > > > On Fri, Mar 30, 2018 at 09:21:55AM +0800, Ganesh Mahendran wrote: > >> 2018-03-29 14:54 GMT+08:00 Minchan Kim : > >> > binder_update_page_range needs down_write of

Re: [PATCH v3 1/1] security: Add mechanism to safely (un)load LSMs after boot time

On Thu, Mar 29, 2018 at 02:37:10PM -0700, Casey Schaufler wrote: > On 3/29/2018 2:14 PM, Sargun Dhillon wrote: > > This patch introduces a mechanism to add mutable hooks and immutable > > hooks to the callback chain. It adds an intermediary item to the > > chain which separates mutable and

Re: [PATCH v3 1/1] security: Add mechanism to safely (un)load LSMs after boot time

On Thu, Mar 29, 2018 at 02:37:10PM -0700, Casey Schaufler wrote: > On 3/29/2018 2:14 PM, Sargun Dhillon wrote: > > This patch introduces a mechanism to add mutable hooks and immutable > > hooks to the callback chain. It adds an intermediary item to the > > chain which separates mutable and

Re: [PATCH net] vhost: validate log when IOTLB is enabled

On 2018年03月29日 22:44, Michael S. Tsirkin wrote: On Thu, Mar 29, 2018 at 04:00:04PM +0800, Jason Wang wrote: Vq log_base is the userspace address of bitmap which has nothing to do with IOTLB. So it needs to be validated unconditionally otherwise we may try use 0 as log_base which may lead to

Re: [PATCH net] vhost: validate log when IOTLB is enabled

On 2018年03月29日 22:44, Michael S. Tsirkin wrote: On Thu, Mar 29, 2018 at 04:00:04PM +0800, Jason Wang wrote: Vq log_base is the userspace address of bitmap which has nothing to do with IOTLB. So it needs to be validated unconditionally otherwise we may try use 0 as log_base which may lead to

[PATCH -next] drm/amdkfd: Make function kfd_dev_is_large_bar() static

Fixes the following sparse warning: drivers/gpu/drm/amd/amdkfd/kfd_chardev.c:1150:6: warning: symbol 'kfd_dev_is_large_bar' was not declared. Should it be static? Signed-off-by: Wei Yongjun --- drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 +- 1 file changed, 1

[PATCH -next] drm/amdkfd: Fix the error return code in kfd_ioctl_unmap_memory_from_gpu()

Passing NULL pointer to PTR_ERR will result in return value of 0 indicating success which is clearly not what it is intended here. This patch returns -EINVAL instead. Fixes: 5ec7e02854b3 ("drm/amdkfd: Add ioctls for GPUVM memory management") Signed-off-by: Wei Yongjun ---

[PATCH -next] drm/amdkfd: Make function kfd_dev_is_large_bar() static

Fixes the following sparse warning: drivers/gpu/drm/amd/amdkfd/kfd_chardev.c:1150:6: warning: symbol 'kfd_dev_is_large_bar' was not declared. Should it be static? Signed-off-by: Wei Yongjun --- drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH -next] drm/amdkfd: Fix the error return code in kfd_ioctl_unmap_memory_from_gpu()

Passing NULL pointer to PTR_ERR will result in return value of 0 indicating success which is clearly not what it is intended here. This patch returns -EINVAL instead. Fixes: 5ec7e02854b3 ("drm/amdkfd: Add ioctls for GPUVM memory management") Signed-off-by: Wei Yongjun ---

Re: [PATCH v3] ANDROID: binder: change down_write to down_read

. :-) [auto build test ERROR on staging/staging-testing] [also build test ERROR on v4.16-rc7 next-20180329] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Minchan-Kim/ANDROID-binder-change-down_write

Re: [PATCH v3] ANDROID: binder: change down_write to down_read

. :-) [auto build test ERROR on staging/staging-testing] [also build test ERROR on v4.16-rc7 next-20180329] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Minchan-Kim/ANDROID-binder-change-down_write

Re: [PATCH v3 2/5] mm: page_alloc: reduce unnecessary binary search in memblock_next_valid_pfn()

On 3/30/2018 9:43 AM, Wei Yang Wrote: On Thu, Mar 29, 2018 at 04:06:38PM +0800, Jia He wrote: On 3/28/2018 5:26 PM, Wei Yang Wrote: On Sun, Mar 25, 2018 at 08:02:16PM -0700, Jia He wrote: Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns where possible") optimized the

Re: [PATCH v3 2/5] mm: page_alloc: reduce unnecessary binary search in memblock_next_valid_pfn()

On 3/30/2018 9:43 AM, Wei Yang Wrote: On Thu, Mar 29, 2018 at 04:06:38PM +0800, Jia He wrote: On 3/28/2018 5:26 PM, Wei Yang Wrote: On Sun, Mar 25, 2018 at 08:02:16PM -0700, Jia He wrote: Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns where possible") optimized the

  1   2   3   4   5   6   7   8   9   10   >