RE: [PATCH 00/17] fs, btrfs refcount conversions

> At 03/06/2017 05:43 PM, Reshetova, Elena wrote: > > > >> At 03/03/2017 04:55 PM, Elena Reshetova wrote: > >>> Now when new refcount_t type and API are finally merged > >>> (see include/linux/refcount.h), the following > >>> patches convert various refcounters in the btrfs filesystem from

RE: [PATCH 00/17] fs, btrfs refcount conversions

> At 03/06/2017 05:43 PM, Reshetova, Elena wrote: > > > >> At 03/03/2017 04:55 PM, Elena Reshetova wrote: > >>> Now when new refcount_t type and API are finally merged > >>> (see include/linux/refcount.h), the following > >>> patches convert various refcounters in the btrfs filesystem from

Re: [PATCH] docs: Clarify details for reporting security bugs

On Mon, Mar 6, 2017 at 11:27 PM, Jonathan Corbet wrote: > On Mon, 6 Mar 2017 11:13:51 -0800 > Kees Cook wrote: > >> The kernel security team is regularly asked to provide CVE identifiers, >> which we don't normally do. This updates the documentation to

Re: [PATCH] docs: Clarify details for reporting security bugs

On Mon, Mar 6, 2017 at 11:27 PM, Jonathan Corbet wrote: > On Mon, 6 Mar 2017 11:13:51 -0800 > Kees Cook wrote: > >> The kernel security team is regularly asked to provide CVE identifiers, >> which we don't normally do. This updates the documentation to mention >> this and adds some more details

[tip:perf/core] tools arch x86: Include asm/cmpxchg.h

Commit-ID: 3337e682d9f3043bb0b925d976558ed5c41b0a09 Gitweb: http://git.kernel.org/tip/3337e682d9f3043bb0b925d976558ed5c41b0a09 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:54:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] tools arch x86: Include asm/cmpxchg.h

Commit-ID: 3337e682d9f3043bb0b925d976558ed5c41b0a09 Gitweb: http://git.kernel.org/tip/3337e682d9f3043bb0b925d976558ed5c41b0a09 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:54:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 3 Mar 2017 19:07:13 -0300

[RFC PATCH 1/5] Document: Add document file for Sony CXD2880 DVB-T2/T tuner + demodulator

From: Yasunari Takiguchi This is the driver for Sony CXD2880 DVB-T2/T tuner + demodulator. Regarding this third Beta Release, the status is: - Tested on Raspberry Pi 3. - The DVB-API operates under dvbv5 tools. Signed-off-by: Yasunari Takiguchi

[RFC PATCH 1/5] Document: Add document file for Sony CXD2880 DVB-T2/T tuner + demodulator

From: Yasunari Takiguchi This is the driver for Sony CXD2880 DVB-T2/T tuner + demodulator. Regarding this third Beta Release, the status is: - Tested on Raspberry Pi 3. - The DVB-API operates under dvbv5 tools. Signed-off-by: Yasunari Takiguchi Signed-off-by: Masayuki Yamamoto Signed-off-by:

[tip:perf/core] tools include: Introduce atomic_cmpxchg_{relaxed,release}()

Commit-ID: 2bcdeadbc094b4f6511aedea1e5b8052bf0cc89c Gitweb: http://git.kernel.org/tip/2bcdeadbc094b4f6511aedea1e5b8052bf0cc89c Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:57:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] tools include: Introduce atomic_cmpxchg_{relaxed,release}()

Commit-ID: 2bcdeadbc094b4f6511aedea1e5b8052bf0cc89c Gitweb: http://git.kernel.org/tip/2bcdeadbc094b4f6511aedea1e5b8052bf0cc89c Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:57:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 3 Mar 2017 19:07:14 -0300

RE: [PATCH] Input: elan_i2c - add ASUS EeeBook X205TA special touchpad fw

Hi Dmitry -Original Message- From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] Sent: Tuesday, March 07, 2017 3:55 AM To: KT Liao Cc: linux-in...@vger.kernel.org; linux-kernel@vger.kernel.org; Matjaz Hegedic Subject: Re: [PATCH] Input: elan_i2c - add ASUS EeeBook X205TA special

RE: [PATCH] Input: elan_i2c - add ASUS EeeBook X205TA special touchpad fw

Hi Dmitry -Original Message- From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] Sent: Tuesday, March 07, 2017 3:55 AM To: KT Liao Cc: linux-in...@vger.kernel.org; linux-kernel@vger.kernel.org; Matjaz Hegedic Subject: Re: [PATCH] Input: elan_i2c - add ASUS EeeBook X205TA special

Re: [PATCH 1/9] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

On Mon, Mar 06, 2017 at 11:24:10AM -0500, Johannes Weiner wrote: > On Mon, Mar 06, 2017 at 10:37:40AM +0900, Minchan Kim wrote: > > On Fri, Mar 03, 2017 at 08:59:54AM +0100, Michal Hocko wrote: > > > On Fri 03-03-17 10:26:09, Minchan Kim wrote: > > > > On Tue, Feb 28, 2017 at 04:39:59PM -0500,

Re: [PATCH 1/9] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

On Mon, Mar 06, 2017 at 11:24:10AM -0500, Johannes Weiner wrote: > On Mon, Mar 06, 2017 at 10:37:40AM +0900, Minchan Kim wrote: > > On Fri, Mar 03, 2017 at 08:59:54AM +0100, Michal Hocko wrote: > > > On Fri 03-03-17 10:26:09, Minchan Kim wrote: > > > > On Tue, Feb 28, 2017 at 04:39:59PM -0500,

Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain

* Mike Travis wrote: > Add a new NMI call chain that is called last after all other NMI handlers > have been checked and did not "handle" the NMI. This mimics the current > NMI_UNKNOWN call chain except it eliminates the WARNING message about > multiple NMI handlers

Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain

* Mike Travis wrote: > Add a new NMI call chain that is called last after all other NMI handlers > have been checked and did not "handle" the NMI. This mimics the current > NMI_UNKNOWN call chain except it eliminates the WARNING message about > multiple NMI handlers registering on this call

Re: [PATCH] irqchip/gic-v3: Fix GICD_CTLR_ARE_NS bit field

On Tue, Mar 07 2017 at 4:07:05 am GMT, Alim Akhtar wrote: > From: Alim Akhtar > > As per GICv3 Architecture specification 8.9.4 field descriptions, > GICD_CTLR_ARE_NS is bit[5]. This patch correct the same. > > Fixes: 021f6537 ("irqchip: gic-v3:

Re: [PATCH] irqchip/gic-v3: Fix GICD_CTLR_ARE_NS bit field

On Tue, Mar 07 2017 at 4:07:05 am GMT, Alim Akhtar wrote: > From: Alim Akhtar > > As per GICv3 Architecture specification 8.9.4 field descriptions, > GICD_CTLR_ARE_NS is bit[5]. This patch correct the same. > > Fixes: 021f6537 ("irqchip: gic-v3: Initial support for GICv3") > Cc:

Re: [PATCH] docs: Clarify details for reporting security bugs

On Mon, 6 Mar 2017 11:13:51 -0800 Kees Cook wrote: > The kernel security team is regularly asked to provide CVE identifiers, > which we don't normally do. This updates the documentation to mention > this and adds some more details about coordination and patch handling >

Re: [PATCH] docs: Clarify details for reporting security bugs

On Mon, 6 Mar 2017 11:13:51 -0800 Kees Cook wrote: > The kernel security team is regularly asked to provide CVE identifiers, > which we don't normally do. This updates the documentation to mention > this and adds some more details about coordination and patch handling > that come up regularly.

[tip:perf/core] tools arch x86: Introduce atomic_cmpxchg()

Commit-ID: 8a73615df3b8973df2de1455c00e9169522d8257 Gitweb: http://git.kernel.org/tip/8a73615df3b8973df2de1455c00e9169522d8257 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:55:43 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] tools arch x86: Introduce atomic_cmpxchg()

Commit-ID: 8a73615df3b8973df2de1455c00e9169522d8257 Gitweb: http://git.kernel.org/tip/8a73615df3b8973df2de1455c00e9169522d8257 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 22 Feb 2017 16:55:43 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 3 Mar 2017 19:07:13 -0300

Re: [PATCH] perf probe: Return errno when does not hit any event

+ Arnaldo Carvalho de Melo On 2017/3/6 17:34, Kefeng Wang wrote: > On old perf, when using perf probe -d to delete an inexistent event, > it return errno, eg, > > -bash-4.3# perf probe -d xxx || echo $? > Info: Event "*:xxx" does not exist. > Error: Failed to delete events.

Re: [PATCH] perf probe: Return errno when does not hit any event

+ Arnaldo Carvalho de Melo On 2017/3/6 17:34, Kefeng Wang wrote: > On old perf, when using perf probe -d to delete an inexistent event, > it return errno, eg, > > -bash-4.3# perf probe -d xxx || echo $? > Info: Event "*:xxx" does not exist. > Error: Failed to delete events. > 255 > > But

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

On 03/07/2017 06:22 AM, Minchan Kim wrote: > Hello Johannes, > > On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: >> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using >> the NVMe over Fabrics loopback target which potentially sends a huge bulk of >>

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

On 03/07/2017 06:22 AM, Minchan Kim wrote: > Hello Johannes, > > On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: >> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using >> the NVMe over Fabrics loopback target which potentially sends a huge bulk of >>

Re: [PATCH] x86/fpu: fix boolreturn.cocci warnings

* kbuild test robot wrote: > arch/x86/kernel/fpu/xstate.c:931:9-10: WARNING: return of 0/1 in function > 'xfeatures_mxcsr_quirk' with return type bool > > Return statements in functions returning bool should use > true/false instead of 1/0. Note that this is a

Re: [PATCH] x86/fpu: fix boolreturn.cocci warnings

* kbuild test robot wrote: > arch/x86/kernel/fpu/xstate.c:931:9-10: WARNING: return of 0/1 in function > 'xfeatures_mxcsr_quirk' with return type bool > > Return statements in functions returning bool should use > true/false instead of 1/0. Note that this is a totally bogus warning. I

Re: [lustre-devel] [PATCH] staging: lustre: fix sparse warning about different address spaces

On Mar 1, 2017, at 6:57 PM, Mario Bambagini wrote: > fixed the following sparse warning by adding proper cast: > drivers/staging//lustre/lustre/obdclass/obd_config.c:1055:74: warning: > incorrect type in argument 2 (different address spaces) >

Re: [lustre-devel] [PATCH] staging: lustre: fix sparse warning about different address spaces

On Mar 1, 2017, at 6:57 PM, Mario Bambagini wrote: > fixed the following sparse warning by adding proper cast: > drivers/staging//lustre/lustre/obdclass/obd_config.c:1055:74: warning: > incorrect type in argument 2 (different address spaces) >

[tip:perf/core] perf vendor events: Add mapping for KnightsMill PMU events

Commit-ID: 771ceddaadd0a2b31603034b36dca50943ff6836 Gitweb: http://git.kernel.org/tip/771ceddaadd0a2b31603034b36dca50943ff6836 Author: Karol Wachowski AuthorDate: Mon, 20 Feb 2017 12:50:40 +0100 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf vendor events: Add mapping for KnightsMill PMU events

Commit-ID: 771ceddaadd0a2b31603034b36dca50943ff6836 Gitweb: http://git.kernel.org/tip/771ceddaadd0a2b31603034b36dca50943ff6836 Author: Karol Wachowski AuthorDate: Mon, 20 Feb 2017 12:50:40 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 3 Mar 2017 19:07:13 -0300 perf vendor

[PATCH 1/2] usb: xhci-mtk: rebuild xhci_mtk_setup()

simplify xhci_mtk_setup() and add xhci_mtk_start() for xhci_driver_overrides struct Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/drivers/usb/host/xhci-mtk.c

[PATCH 1/2] usb: xhci-mtk: rebuild xhci_mtk_setup()

simplify xhci_mtk_setup() and add xhci_mtk_start() for xhci_driver_overrides struct Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c index

[PATCH 2/2] usb: xhci-mtk: fix checkpatch warning and erorr

there are two warnings and a erorr when checked by checkpatch.pl as following: WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses Signed-off-by: Chunfeng Yun

[PATCH 2/2] usb: xhci-mtk: fix checkpatch warning and erorr

there are two warnings and a erorr when checked by checkpatch.pl as following: WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses Signed-off-by: Chunfeng Yun ---

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hi Hannes, On Tue, Mar 7, 2017 at 4:00 PM, Hannes Reinecke wrote: > On 03/07/2017 06:22 AM, Minchan Kim wrote: >> Hello Johannes, >> >> On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: >>> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hi Hannes, On Tue, Mar 7, 2017 at 4:00 PM, Hannes Reinecke wrote: > On 03/07/2017 06:22 AM, Minchan Kim wrote: >> Hello Johannes, >> >> On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: >>> zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using >>> the

Re: [PATCH v5 05/15] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

On Mon, 2017-02-13 at 19:42 -0600, Josh Poimboeuf wrote: > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > per-task consistency model for powerpc. The bit getting set indicates > the thread has a pending patch which needs to be applied when the thread > exits the kernel. > >

Re: [PATCH v5 05/15] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

On Mon, 2017-02-13 at 19:42 -0600, Josh Poimboeuf wrote: > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > per-task consistency model for powerpc. The bit getting set indicates > the thread has a pending patch which needs to be applied when the thread > exits the kernel. > >

Re: [GIT PULL 00/35] perf/core improvements and fixes

> > The following changes since commit 9d020d33fc1b2faa0eb35859df1381ca5dc94ffe: > > Merge branch 'linus' into perf/urgent, to resolve conflict (2017-03-02 > 08:05:45 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > ta

Re: [GIT PULL 00/35] perf/core improvements and fixes

81ca5dc94ffe: > > Merge branch 'linus' into perf/urgent, to resolve conflict (2017-03-02 > 08:05:45 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core

[PATCH] staging: rtl8192e: fix coding style issue, improve error handling

Fix coding style issue and comments in rtl_core.c Return -ENOMEM, if it is out of memory Pointer comparison with NULL replaced by logical NOT Signed-off-by: Suniel Mahesh --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 253 +++ 1 file changed,

[PATCH] staging: rtl8192e: fix coding style issue, improve error handling

Fix coding style issue and comments in rtl_core.c Return -ENOMEM, if it is out of memory Pointer comparison with NULL replaced by logical NOT Signed-off-by: Suniel Mahesh --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 253 +++ 1 file changed, 100 insertions(+), 153

[PATCH 2/5] locking/locktorture: Fix rwsem reader_delay

We should account for nreader threads, not writers in this callback. Could even trigger a div by 0 if the user explicitly disables writers. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/5] locking/locktorture: Fix rwsem reader_delay

We should account for nreader threads, not writers in this callback. Could even trigger a div by 0 if the user explicitly disables writers. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/5] locking: Introduce range reader/writer lock

This implements a sleepable range rwlock, based on interval tree, serializing conflicting/intersecting/overlapping ranges within the tree. The largest range is given by [0, ~0 - 1] (inclusive). Unlike traditional locks, range locking involves dealing with the tree itself and the range to be

[PATCH 1/5] locking: Introduce range reader/writer lock

This implements a sleepable range rwlock, based on interval tree, serializing conflicting/intersecting/overlapping ranges within the tree. The largest range is given by [0, ~0 - 1] (inclusive). Unlike traditional locks, range locking involves dealing with the tree itself and the range to be

[PATCH 3/5] locking/locktorture: Fix num reader/writer corner cases

Things can explode for locktorture if the user does combinations of nwriters_stress=0 nreaders_stress=0. Fix this by not assuming we always want to torture writer threads. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 76

[PATCH 3/5] locking/locktorture: Fix num reader/writer corner cases

Things can explode for locktorture if the user does combinations of nwriters_stress=0 nreaders_stress=0. Fix this by not assuming we always want to torture writer threads. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 76 +--- 1 file

RE: [v3] mmc: sdhci-cadence: add HS400 enhanced strobe support

Hi Masahiro, Thanks for all of your reviews. Best Regards Piotr Sroka > -Original Message- > From: Masahiro Yamada [mailto:yamada.masah...@socionext.com] > Sent: 06 March, 2017 9:59 PM > Subject: Re: [v3] mmc: sdhci-cadence: add HS400 enhanced strobe support > > Hi Piotr, > >

RE: [v3] mmc: sdhci-cadence: add HS400 enhanced strobe support

Hi Masahiro, Thanks for all of your reviews. Best Regards Piotr Sroka > -Original Message- > From: Masahiro Yamada [mailto:yamada.masah...@socionext.com] > Sent: 06 March, 2017 9:59 PM > Subject: Re: [v3] mmc: sdhci-cadence: add HS400 enhanced strobe support > > Hi Piotr, > >

Re: [PATCH 00/17] fs, btrfs refcount conversions

At 03/06/2017 05:43 PM, Reshetova, Elena wrote: At 03/03/2017 04:55 PM, Elena Reshetova wrote: Now when new refcount_t type and API are finally merged (see include/linux/refcount.h), the following patches convert various refcounters in the btrfs filesystem from atomic_t to refcount_t. By

Re: [PATCH 00/17] fs, btrfs refcount conversions

At 03/06/2017 05:43 PM, Reshetova, Elena wrote: At 03/03/2017 04:55 PM, Elena Reshetova wrote: Now when new refcount_t type and API are finally merged (see include/linux/refcount.h), the following patches convert various refcounters in the btrfs filesystem from atomic_t to refcount_t. By

Re: [PATCH V3 1/3] sched/deadline: Replenishment timer should fire in the next period

2017-02-28 18:07 GMT+08:00 Daniel Bristot de Oliveira : > Currently, the replenishment timer is set to fire at the deadline > of a task. Although that works for implicit deadline tasks because the > deadline is equals to the begin of the next period, that is not correct > for

Re: [PATCH V3 1/3] sched/deadline: Replenishment timer should fire in the next period

2017-02-28 18:07 GMT+08:00 Daniel Bristot de Oliveira : > Currently, the replenishment timer is set to fire at the deadline > of a task. Although that works for implicit deadline tasks because the > deadline is equals to the begin of the next period, that is not correct > for constrained deadline

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hello Johannes, On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: > zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using > the NVMe over Fabrics loopback target which potentially sends a huge bulk of > pages attached to the bio's bvec this results in a

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hello Johannes, On Mon, Mar 06, 2017 at 11:23:35AM +0100, Johannes Thumshirn wrote: > zram can handle at most SECTORS_PER_PAGE sectors in a bio's bvec. When using > the NVMe over Fabrics loopback target which potentially sends a huge bulk of > pages attached to the bio's bvec this results in a

[PATCH 0/5] locking Introduce range reader/writer lock

Hi, Here's a very tardy proposal for enhancements to Jan's original[1] range lock using interval trees. Because at some point it would be awesome to switch mmap_sem from rwsem to range rwlock, I've focused on making it sharable and performance enhancements reducing the performance delta between

[PATCH 0/5] locking Introduce range reader/writer lock

Hi, Here's a very tardy proposal for enhancements to Jan's original[1] range lock using interval trees. Because at some point it would be awesome to switch mmap_sem from rwsem to range rwlock, I've focused on making it sharable and performance enhancements reducing the performance delta between

[PATCH 1/1] mtk-vcodec: check the vp9 decoder buffer index from VPU.

From: Wu-Cheng Li VPU firmware has a bug and may return invalid buffer index for some vp9 videos. Check the buffer indexes before accessing the buffer. Signed-off-by: Wu-Cheng Li --- drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 6 +

Re: Subject: [PATCH v4] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

      > On Fri, 3 Mar 2017, Ajay Kaher wrote: >  > > > usb_class->kref is not accessible outside the file.c > > > as usb_class is _static_ inside the file.c and > > > pointer of usb_class->kref is not passed anywhere. > > >  > > > Hence as you wanted, there are no references of usb_class->kref > > 

[PATCH 1/1] mtk-vcodec: check the vp9 decoder buffer index from VPU.

From: Wu-Cheng Li VPU firmware has a bug and may return invalid buffer index for some vp9 videos. Check the buffer indexes before accessing the buffer. Signed-off-by: Wu-Cheng Li --- drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 6 +

Re: Subject: [PATCH v4] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

      > On Fri, 3 Mar 2017, Ajay Kaher wrote: >  > > > usb_class->kref is not accessible outside the file.c > > > as usb_class is _static_ inside the file.c and > > > pointer of usb_class->kref is not passed anywhere. > > >  > > > Hence as you wanted, there are no references of usb_class->kref > > 

[PATCH v1 0/1] mtk-vcodec: check the vp9 decoder buffer index from VPU

From: Wu-Cheng Li This patch guards against the invalid buffer index from VPU firmware. Wu-Cheng Li (1): mtk-vcodec: check the vp9 decoder buffer index from VPU. drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 6 +

[PATCH v1 0/1] mtk-vcodec: check the vp9 decoder buffer index from VPU

From: Wu-Cheng Li This patch guards against the invalid buffer index from VPU firmware. Wu-Cheng Li (1): mtk-vcodec: check the vp9 decoder buffer index from VPU. drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 6 + .../media/platform/mtk-vcodec/vdec/vdec_vp9_if.c | 26

[PATCH] sched/deadline: Add missing update_rq_clock() in dl_task_timer()

From: Wanpeng Li The following warning can be triggered by hot-unplugging the CPU on which an active SCHED_DEADLINE task is running on: [ cut here ] WARNING: CPU: 7 PID: 0 at kernel/sched/sched.h:833 replenish_dl_entity+0x71e/0xc40

[PATCH] sched/deadline: Add missing update_rq_clock() in dl_task_timer()

From: Wanpeng Li The following warning can be triggered by hot-unplugging the CPU on which an active SCHED_DEADLINE task is running on: [ cut here ] WARNING: CPU: 7 PID: 0 at kernel/sched/sched.h:833 replenish_dl_entity+0x71e/0xc40 rq->clock_update_flags <

Re: + mm-reclaim-madv_free-pages.patch added to -mm tree

On Mon, Mar 06, 2017 at 10:49:06AM -0500, Johannes Weiner wrote: < snip > > > @@ -1413,20 +1413,24 @@ static int try_to_unmap_one(struct page *page, > > struct vm_area_struct *vma, > > * Store the swap location in the pte. > > * See handle_pte_fault()

Re: + mm-reclaim-madv_free-pages.patch added to -mm tree

On Mon, Mar 06, 2017 at 10:49:06AM -0500, Johannes Weiner wrote: < snip > > > @@ -1413,20 +1413,24 @@ static int try_to_unmap_one(struct page *page, > > struct vm_area_struct *vma, > > * Store the swap location in the pte. > > * See handle_pte_fault()

RE: [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts

Hi Marc, can you please look into my last comments ? Regards, Bharat > Subject: RE: [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy > interrupts > > Waiting for Marc's Reply... > > > > -Original Message- > > > From: Marc Zyngier [mailto:marc.zyng...@arm.com] > > > Sent:

RE: [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts

Hi Marc, can you please look into my last comments ? Regards, Bharat > Subject: RE: [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy > interrupts > > Waiting for Marc's Reply... > > > > -Original Message- > > > From: Marc Zyngier [mailto:marc.zyng...@arm.com] > > > Sent:

[PATCH 4/5] locking/locktorture: Support range rwlocks

Torture the reader/writer range locks. Each thread will attempt to lock+unlock a range of up to [0, 4096]. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 221 +-- 1 file changed, 172 insertions(+), 49 deletions(-) diff

[PATCH 4/5] locking/locktorture: Support range rwlocks

Torture the reader/writer range locks. Each thread will attempt to lock+unlock a range of up to [0, 4096]. Signed-off-by: Davidlohr Bueso --- kernel/locking/locktorture.c | 221 +-- 1 file changed, 172 insertions(+), 49 deletions(-) diff --git

Re: + mm-reclaim-madv_free-pages.patch added to -mm tree

On Mon, Mar 06, 2017 at 10:49:06AM -0500, Johannes Weiner wrote: > On Mon, Mar 06, 2017 at 12:03:44PM +0900, Minchan Kim wrote: > > On Fri, Mar 03, 2017 at 10:18:51AM -0500, Johannes Weiner wrote: > > > On Fri, Mar 03, 2017 at 11:52:37AM +0900, Minchan Kim wrote: > > > > On Tue, Feb 28, 2017 at

Re: + mm-reclaim-madv_free-pages.patch added to -mm tree

On Mon, Mar 06, 2017 at 10:49:06AM -0500, Johannes Weiner wrote: > On Mon, Mar 06, 2017 at 12:03:44PM +0900, Minchan Kim wrote: > > On Fri, Mar 03, 2017 at 10:18:51AM -0500, Johannes Weiner wrote: > > > On Fri, Mar 03, 2017 at 11:52:37AM +0900, Minchan Kim wrote: > > > > On Tue, Feb 28, 2017 at

[PATCH 5/5] staging/lustre: Use generic range rwlock

This replaces the in-house version, which is also derived from Jan's interval tree implementation. Cc: oleg.dro...@intel.com Cc: andreas.dil...@intel.com Cc: jsimm...@infradead.org Cc: lustre-de...@lists.lustre.org Signed-off-by: Davidlohr Bueso --- XXX: compile tested only. In

[PATCH 5/5] staging/lustre: Use generic range rwlock

This replaces the in-house version, which is also derived from Jan's interval tree implementation. Cc: oleg.dro...@intel.com Cc: andreas.dil...@intel.com Cc: jsimm...@infradead.org Cc: lustre-de...@lists.lustre.org Signed-off-by: Davidlohr Bueso --- XXX: compile tested only. In house uses

Re: [tip:x86/asm] x86/asm: Optimize clear_page()

On Wed, Mar 1, 2017 at 1:47 AM, tip-bot for Borislav Petkov wrote: > Commit-ID: 49ca7bb328c630dd43be626534b49e19513296fd > Gitweb: http://git.kernel.org/tip/49ca7bb328c630dd43be626534b49e19513296fd > Author: Borislav Petkov > AuthorDate: Thu, 9 Feb 2017

Re: [tip:x86/asm] x86/asm: Optimize clear_page()

On Wed, Mar 1, 2017 at 1:47 AM, tip-bot for Borislav Petkov wrote: > Commit-ID: 49ca7bb328c630dd43be626534b49e19513296fd > Gitweb: http://git.kernel.org/tip/49ca7bb328c630dd43be626534b49e19513296fd > Author: Borislav Petkov > AuthorDate: Thu, 9 Feb 2017 01:34:49 +0100 > Committer: Ingo

Re: linux-next: build failure after merge of the staging tree

p2/./atomisp_compat.h:27:27: fatal > error: linux/atomisp.h: No such file or directory > > Caused by commit > > a49d25364dfb ("staging/atomisp: Add support for the Intel IPU v2") > > or maybe some of the followups? > > I have used the staging tree from nex

Re: linux-next: build failure after merge of the staging tree

p2/./atomisp_compat.h:27:27: fatal > error: linux/atomisp.h: No such file or directory > > Caused by commit > > a49d25364dfb ("staging/atomisp: Add support for the Intel IPU v2") > > or maybe some of the followups? > > I have used the staging tree from nex

[lkp-robot] [block] 165a5e22fa: BUG_kmalloc-#(Not_tainted):Poison_overwritten

FYI, we noticed the following commit: commit: 165a5e22fafb127ecb5914e12e8c32a1f0d3f820 ("block: Move bdi_unregister() to del_gendisk()") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [block] 165a5e22fa: BUG_kmalloc-#(Not_tainted):Poison_overwritten

FYI, we noticed the following commit: commit: 165a5e22fafb127ecb5914e12e8c32a1f0d3f820 ("block: Move bdi_unregister() to del_gendisk()") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Tue, 2017-03-07 at 05:08 +, Parav Pandit wrote: > I replied with pseudo code in previous reply to Bart to bring back dma_device > member in the ib_device. > dma_device member was already present in near past of few weeks. > It should be able to work using it without performance impact and

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Tue, 2017-03-07 at 05:08 +, Parav Pandit wrote: > I replied with pseudo code in previous reply to Bart to bring back dma_device > member in the ib_device. > dma_device member was already present in near past of few weeks. > It should be able to work using it without performance impact and

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Greg, > -Original Message- > From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org] > Sent: Monday, March 6, 2017 10:53 PM > To: Bart Van Assche > Cc: Doug Ledford ; Sebastian Ott > ; Parav Pandit

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Tue, Mar 07, 2017 at 11:54:20AM +1100, Dave Chinner wrote: > > Or maybe I've misunderstood, and you're asking if we should try > > kmem_zalloc(4 pages), then kmem_zalloc(1 page), and only then switch to > > the __vmalloc calls? > > Just call kmem_zalloc_large() for 4 pages without a fallback

Re: [PATCH] xfs: remove kmem_zalloc_greedy

On Tue, Mar 07, 2017 at 11:54:20AM +1100, Dave Chinner wrote: > > Or maybe I've misunderstood, and you're asking if we should try > > kmem_zalloc(4 pages), then kmem_zalloc(1 page), and only then switch to > > the __vmalloc calls? > > Just call kmem_zalloc_large() for 4 pages without a fallback

RE: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

Hi Greg, > -Original Message- > From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org] > Sent: Monday, March 6, 2017 10:53 PM > To: Bart Van Assche > Cc: Doug Ledford ; Sebastian Ott > ; Parav Pandit ; linux- > r...@vger.kernel.org; linux-kernel@vger.kernel.org; Bjorn Helgaas > ;

Re: netlink: GPF in netlink_unicast

On 2017-03-06 10:10, Cong Wang wrote: > On Mon, Mar 6, 2017 at 2:54 AM, Dmitry Vyukov wrote: > > Hello, > > > > I've got the following crash while running syzkaller fuzzer on > > net-next/8d70eeb84ab277377c017af6a21d0a337025dede: > > > > kasan: GPF could be caused by NULL-ptr

Re: netlink: GPF in netlink_unicast

On 2017-03-06 10:10, Cong Wang wrote: > On Mon, Mar 6, 2017 at 2:54 AM, Dmitry Vyukov wrote: > > Hello, > > > > I've got the following crash while running syzkaller fuzzer on > > net-next/8d70eeb84ab277377c017af6a21d0a337025dede: > > > > kasan: GPF could be caused by NULL-ptr deref or user memory

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Mon, Mar 06, 2017 at 04:35:48PM -0800, Bart Van Assche wrote: > The dma mapping operations of several architectures and also of > several I/O MMU implementations need to translate a struct > device pointer into a struct pci_dev pointer. This translation > is performed by to_pci_dev(). That

Re: [PATCH 1/2] device: Stop requiring that struct device is embedded in struct pci_dev

On Mon, Mar 06, 2017 at 04:35:48PM -0800, Bart Van Assche wrote: > The dma mapping operations of several architectures and also of > several I/O MMU implementations need to translate a struct > device pointer into a struct pci_dev pointer. This translation > is performed by to_pci_dev(). That

[PATCH] irqchip/gic-v3: Fix GICD_CTLR_ARE_NS bit field

From: Alim Akhtar As per GICv3 Architecture specification 8.9.4 field descriptions, GICD_CTLR_ARE_NS is bit[5]. This patch correct the same. Fixes: 021f6537 ("irqchip: gic-v3: Initial support for GICv3") Cc: sta...@vger.kernel.org Signed-off-by: Alim Akhtar

[PATCH] irqchip/gic-v3: Fix GICD_CTLR_ARE_NS bit field

From: Alim Akhtar As per GICv3 Architecture specification 8.9.4 field descriptions, GICD_CTLR_ARE_NS is bit[5]. This patch correct the same. Fixes: 021f6537 ("irqchip: gic-v3: Initial support for GICv3") Cc: sta...@vger.kernel.org Signed-off-by: Alim Akhtar ---

Re: [PATCH net-next 1/5] ldmvsw: better use of link up and down on ldom vswitch

On 3/6/2017 3:53 PM, Florian Fainelli wrote: On 03/06/2017 03:15 PM, Shannon Nelson wrote: When an ldom VM is bound, the network vswitch infrastructure is set up for it, but was being forced 'UP' by the userland switch configuration script. When 'UP' but not actually connected to a running

Re: [PATCH net-next 1/5] ldmvsw: better use of link up and down on ldom vswitch

On 3/6/2017 3:53 PM, Florian Fainelli wrote: On 03/06/2017 03:15 PM, Shannon Nelson wrote: When an ldom VM is bound, the network vswitch infrastructure is set up for it, but was being forced 'UP' by the userland switch configuration script. When 'UP' but not actually connected to a running

[PATCH 09/18] pstore: Replace arguments for read() API

The argument list for the pstore_read() interface is unwieldy. This changes passes the new struct pstore_record instead. The erst backend was already doing something similar internally. Signed-off-by: Kees Cook --- arch/powerpc/kernel/nvram_64.c| 61

[PATCH 09/18] pstore: Replace arguments for read() API

The argument list for the pstore_read() interface is unwieldy. This changes passes the new struct pstore_record instead. The erst backend was already doing something similar internally. Signed-off-by: Kees Cook --- arch/powerpc/kernel/nvram_64.c| 61 +++---

  1   2   3   4   5   6   7   8   9   10   >