Re: sg_io HARDENED_USERCOPY_PAGESPAN trace

On Wed, Dec 28, 2016 at 04:40:16PM -0500, Dave Jones wrote: > sg_io+0x113/0x470 Can you resolve that to a source line using a gdb?

Re: mm: fix typo of cache_alloc_zspage()

On Thu, Dec 29, 2016 at 04:34:03PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (12/29/16 15:59), Minchan Kim wrote: > [..] > > > I don't know... do we want to have it as a separate patch? > > > may be we can fold it into some other patch someday later. > > > > Xishi spent his time to make

Re: sg_io HARDENED_USERCOPY_PAGESPAN trace

On Wed, Dec 28, 2016 at 04:40:16PM -0500, Dave Jones wrote: > sg_io+0x113/0x470 Can you resolve that to a source line using a gdb?

Re: mm: fix typo of cache_alloc_zspage()

On Thu, Dec 29, 2016 at 04:34:03PM +0900, Sergey Senozhatsky wrote: > Hello, > > On (12/29/16 15:59), Minchan Kim wrote: > [..] > > > I don't know... do we want to have it as a separate patch? > > > may be we can fold it into some other patch someday later. > > > > Xishi spent his time to make

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Thu 29-12-16 15:02:04, Minchan Kim wrote: > On Wed, Dec 28, 2016 at 04:30:29PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > mm_vmscan_lru_isolate currently prints only whether the LRU we isolate > > from is file or anonymous but we do not know which LRU this is.

Re: [PATCH 3/7] mm, vmscan: show the number of skipped pages in mm_vmscan_lru_isolate

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate shows the number of requested, scanned and taken > pages. This is mostly OK but on 32b systems the number of scanned pages > is quite misleading because it includes both

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Thu 29-12-16 15:02:04, Minchan Kim wrote: > On Wed, Dec 28, 2016 at 04:30:29PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > mm_vmscan_lru_isolate currently prints only whether the LRU we isolate > > from is file or anonymous but we do not know which LRU this is. It is > > useful

Re: [PATCH 3/7] mm, vmscan: show the number of skipped pages in mm_vmscan_lru_isolate

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate shows the number of requested, scanned and taken > pages. This is mostly OK but on 32b systems the number of scanned pages > is quite misleading because it includes both the scanned and

[PATCH V2] mm: fix typo of cache_alloc_zspage()

Delete extra semicolon, it was introduced in 3783689 zsmalloc: introduce zspage structure Signed-off-by: Xishi Qiu --- mm/zsmalloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c index 9cc3c0b..2d6c92e 100644 ---

[PATCH V2] mm: fix typo of cache_alloc_zspage()

Delete extra semicolon, it was introduced in 3783689 zsmalloc: introduce zspage structure Signed-off-by: Xishi Qiu --- mm/zsmalloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c index 9cc3c0b..2d6c92e 100644 --- a/mm/zsmalloc.c +++

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Thu 29-12-16 14:33:59, Minchan Kim wrote: > On Wed, Dec 28, 2016 at 04:30:27PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > Our reclaim process has several tracepoints to tell us more about how > > things are progressing. We are, however, missing a tracepoint to

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Thu 29-12-16 14:33:59, Minchan Kim wrote: > On Wed, Dec 28, 2016 at 04:30:27PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > Our reclaim process has several tracepoints to tell us more about how > > things are progressing. We are, however, missing a tracepoint to track > > active

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > Our reclaim process has several tracepoints to tell us more about how > things are progressing. We are, however, missing a tracepoint to track > active list aging. Introduce

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > Our reclaim process has several tracepoints to tell us more about how > things are progressing. We are, however, missing a tracepoint to track > active list aging. Introduce mm_vmscan_lru_shrink_active which

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

On 12/29/2016 12:02 PM, Jaehoon Chung wrote: > Hi Randy, > > On 12/29/2016 12:34 AM, Randy Li wrote: >> This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. >> It is reported that making RK3288 can't boot from eMMC/MMC. > > Could you explain in more detail? > As you mentioned, this

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

On 12/29/2016 12:02 PM, Jaehoon Chung wrote: > Hi Randy, > > On 12/29/2016 12:34 AM, Randy Li wrote: >> This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. >> It is reported that making RK3288 can't boot from eMMC/MMC. > > Could you explain in more detail? > As you mentioned, this

Re: [PATCH v3 4/4] phy: qcom-qmp: new qmp phy driver for qcom-chipsets

Hi Stephen, On Thu, Dec 29, 2016 at 4:46 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> Qualcomm SOCs have QMP phy controller that provides support >> to a number of controller, viz. PCIe, UFS, and USB. >> Add a new driver, based on generic phy framework, for

Re: [PATCH v3 4/4] phy: qcom-qmp: new qmp phy driver for qcom-chipsets

Hi Stephen, On Thu, Dec 29, 2016 at 4:46 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> Qualcomm SOCs have QMP phy controller that provides support >> to a number of controller, viz. PCIe, UFS, and USB. >> Add a new driver, based on generic phy framework, for this >> phy controller.

Re: [PATCH 1/7] mm, vmscan: remove unused mm_vmscan_memcg_isolate

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > the trace point is not used since 925b7673cce3 ("mm: make per-memcg LRU > lists exclusive") so it can be removed. > > Signed-off-by: Michal Hocko > --- Acked-by: Hillf

Re: [PATCH 1/7] mm, vmscan: remove unused mm_vmscan_memcg_isolate

On Wednesday, December 28, 2016 11:30 PM Michal Hocko wrote: > From: Michal Hocko > > the trace point is not used since 925b7673cce3 ("mm: make per-memcg LRU > lists exclusive") so it can be removed. > > Signed-off-by: Michal Hocko > --- Acked-by: Hillf Danton

Re: mm: fix typo of cache_alloc_zspage()

Hello, On (12/29/16 15:59), Minchan Kim wrote: [..] > > I don't know... do we want to have it as a separate patch? > > may be we can fold it into some other patch someday later. > > Xishi spent his time to make the patch(review,create/send). And I want to > give a credit to him. :) sure, I

Re: mm: fix typo of cache_alloc_zspage()

Hello, On (12/29/16 15:59), Minchan Kim wrote: [..] > > I don't know... do we want to have it as a separate patch? > > may be we can fold it into some other patch someday later. > > Xishi spent his time to make the patch(review,create/send). And I want to > give a credit to him. :) sure, I

Re: [PATCH v3 RESEND 02/11] pwm: imx: remove ipg clock

On 2016-12-28 23:01, Lukasz Majewski wrote: > Hi Stefan, > >> Hi Stefan, >> >> > On 2016-12-26 23:55, Lukasz Majewski wrote: >> > > From: Sascha Hauer >> > > >> > > The use of the ipg clock was introduced with commit 7b27c160c681 >> > > ("pwm: i.MX: fix clock lookup"). >>

Re: [PATCH v3 RESEND 02/11] pwm: imx: remove ipg clock

On 2016-12-28 23:01, Lukasz Majewski wrote: > Hi Stefan, > >> Hi Stefan, >> >> > On 2016-12-26 23:55, Lukasz Majewski wrote: >> > > From: Sascha Hauer >> > > >> > > The use of the ipg clock was introduced with commit 7b27c160c681 >> > > ("pwm: i.MX: fix clock lookup"). >> > > In the commit

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

On 2016/12/29 15:13, Jaehoon Chung wrote: On 12/29/2016 12:02 PM, Jaehoon Chung wrote: Hi Randy, On 12/29/2016 12:34 AM, Randy Li wrote: This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. It is reported that making RK3288 can't boot from eMMC/MMC. Could you explain in more

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

On 2016/12/29 15:13, Jaehoon Chung wrote: On 12/29/2016 12:02 PM, Jaehoon Chung wrote: Hi Randy, On 12/29/2016 12:34 AM, Randy Li wrote: This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. It is reported that making RK3288 can't boot from eMMC/MMC. Could you explain in more

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

Linus Walleij writes: > On Thu, Dec 8, 2016 at 3:35 PM, Arvind Yadav > wrote: > >> In functions pxa2xx_build_functions, the memory allocated for >> 'functions' is live within the function only. After the >> allocation it is immediately freed

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

Linus Walleij writes: > On Thu, Dec 8, 2016 at 3:35 PM, Arvind Yadav > wrote: > >> In functions pxa2xx_build_functions, the memory allocated for >> 'functions' is live within the function only. After the >> allocation it is immediately freed with devm_kfree. There is >> no need to allocate

Re: [PATCH v3 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

Hi Stephen, On Thu, Dec 29, 2016 at 12:27 PM, Vivek Gautam wrote: > On Thu, Dec 29, 2016 at 4:31 AM, Stephen Boyd wrote: >> On 12/20, Vivek Gautam wrote: >>> PHY transceiver driver for QUSB2 phy controller that provides >>> HighSpeed

Re: [PATCH v3 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

Hi Stephen, On Thu, Dec 29, 2016 at 12:27 PM, Vivek Gautam wrote: > On Thu, Dec 29, 2016 at 4:31 AM, Stephen Boyd wrote: >> On 12/20, Vivek Gautam wrote: >>> PHY transceiver driver for QUSB2 phy controller that provides >>> HighSpeed functionality for DWC3 controller present on >>> Qualcomm

Re: mm: fix typo of cache_alloc_zspage()

Hi Sergey, On Thu, Dec 29, 2016 at 03:52:05PM +0900, Sergey Senozhatsky wrote: > On (12/29/16 15:44), Minchan Kim wrote: > > On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > > > Signed-off-by: Xishi Qiu > > > --- > > > mm/zsmalloc.c | 2 +- > > > 1 file changed,

Re: mm: fix typo of cache_alloc_zspage()

Hi Sergey, On Thu, Dec 29, 2016 at 03:52:05PM +0900, Sergey Senozhatsky wrote: > On (12/29/16 15:44), Minchan Kim wrote: > > On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > > > Signed-off-by: Xishi Qiu > > > --- > > > mm/zsmalloc.c | 2 +- > > > 1 file changed, 1 insertion(+), 1

Re: [PATCH v3 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

On Thu, Dec 29, 2016 at 4:31 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> PHY transceiver driver for QUSB2 phy controller that provides >> HighSpeed functionality for DWC3 controller present on >> Qualcomm chipsets. >> >> Signed-off-by: Vivek Gautam

Re: [PATCH v3 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

On Thu, Dec 29, 2016 at 4:31 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> PHY transceiver driver for QUSB2 phy controller that provides >> HighSpeed functionality for DWC3 controller present on >> Qualcomm chipsets. >> >> Signed-off-by: Vivek Gautam > > One comment below, but

[RFC PATCH V2] ext4: increase the protection of drop nlink and ext4 inode destroy

Because of the disk and hardware issue, the ext4 filesystem have many errors, the inode->i_nlink of ext4 becomes zero abnormally but the dentry is still positive, it will cause memory corruption after the following process: 1) Due to the inode->i_nlink is 0, this inode will be added into the

[RFC PATCH V2] ext4: increase the protection of drop nlink and ext4 inode destroy

Because of the disk and hardware issue, the ext4 filesystem have many errors, the inode->i_nlink of ext4 becomes zero abnormally but the dentry is still positive, it will cause memory corruption after the following process: 1) Due to the inode->i_nlink is 0, this inode will be added into the

Re: mm: fix typo of cache_alloc_zspage()

On (12/29/16 15:44), Minchan Kim wrote: > On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > > Signed-off-by: Xishi Qiu > > --- > > mm/zsmalloc.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c > > index

Re: mm: fix typo of cache_alloc_zspage()

On (12/29/16 15:44), Minchan Kim wrote: > On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > > Signed-off-by: Xishi Qiu > > --- > > mm/zsmalloc.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c > > index 9cc3c0b..2d6c92e

Re: mm: fix typo of cache_alloc_zspage()

On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > Signed-off-by: Xishi Qiu > --- > mm/zsmalloc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c > index 9cc3c0b..2d6c92e 100644 > --- a/mm/zsmalloc.c > +++

Re: mm: fix typo of cache_alloc_zspage()

On Thu, Dec 29, 2016 at 10:06:47AM +0800, Xishi Qiu wrote: > Signed-off-by: Xishi Qiu > --- > mm/zsmalloc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c > index 9cc3c0b..2d6c92e 100644 > --- a/mm/zsmalloc.c > +++ b/mm/zsmalloc.c > @@

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Wed, Dec 28, 2016 at 04:30:29PM +0100, Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate currently prints only whether the LRU we isolate > from is file or anonymous but we do not know which LRU this is. It is > useful to know whether the list is file or

Re: [PATCH 4/7] mm, vmscan: show LRU name in mm_vmscan_lru_isolate tracepoint

On Wed, Dec 28, 2016 at 04:30:29PM +0100, Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate currently prints only whether the LRU we isolate > from is file or anonymous but we do not know which LRU this is. It is > useful to know whether the list is file or anonymous as well.

Re: [PATCH 3/7] mm, vmscan: show the number of skipped pages in mm_vmscan_lru_isolate

On Wed, Dec 28, 2016 at 04:30:28PM +0100, Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate shows the number of requested, scanned and taken > pages. This is mostly OK but on 32b systems the number of scanned pages > is quite misleading because it includes both

Re: [PATCH 3/7] mm, vmscan: show the number of skipped pages in mm_vmscan_lru_isolate

On Wed, Dec 28, 2016 at 04:30:28PM +0100, Michal Hocko wrote: > From: Michal Hocko > > mm_vmscan_lru_isolate shows the number of requested, scanned and taken > pages. This is mostly OK but on 32b systems the number of scanned pages > is quite misleading because it includes both the scanned and

Re: [PATCH] pci: rename *host* directory to *controller*

Hi, On Wednesday 28 December 2016 10:50 PM, Joao Pinto wrote: > Às 5:17 PM de 12/28/2016, Joao Pinto escreveu: >> Às 4:41 PM de 12/28/2016, Bjorn Helgaas escreveu: >>> On Wed, Dec 28, 2016 at 01:57:13PM +, Joao Pinto wrote: Às 9:22 AM de 12/28/2016, Christoph Hellwig escreveu: > On

Re: [PATCH] pci: rename *host* directory to *controller*

Hi, On Wednesday 28 December 2016 10:50 PM, Joao Pinto wrote: > Às 5:17 PM de 12/28/2016, Joao Pinto escreveu: >> Às 4:41 PM de 12/28/2016, Bjorn Helgaas escreveu: >>> On Wed, Dec 28, 2016 at 01:57:13PM +, Joao Pinto wrote: Às 9:22 AM de 12/28/2016, Christoph Hellwig escreveu: > On

Re: [PATCH v6] soc: qcom: Add SoC info driver

On 12/29/2016 4:05 AM, Stephen Boyd wrote: > On 12/23, Imran Khan wrote: >> On 12/22/2016 6:01 AM, Stephen Boyd wrote: >>> >>> Raw numbers sounds fine, but how do we know what ODM it is to >>> understand how to parse the numbers appropriately? Perhaps the >>> smem DT entry needs to have a property

Re: [PATCH v6] soc: qcom: Add SoC info driver

On 12/29/2016 4:05 AM, Stephen Boyd wrote: > On 12/23, Imran Khan wrote: >> On 12/22/2016 6:01 AM, Stephen Boyd wrote: >>> >>> Raw numbers sounds fine, but how do we know what ODM it is to >>> understand how to parse the numbers appropriately? Perhaps the >>> smem DT entry needs to have a property

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wed, Dec 28, 2016 at 04:30:27PM +0100, Michal Hocko wrote: > From: Michal Hocko > > Our reclaim process has several tracepoints to tell us more about how > things are progressing. We are, however, missing a tracepoint to track > active list aging. Introduce

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Wed, Dec 28, 2016 at 04:30:27PM +0100, Michal Hocko wrote: > From: Michal Hocko > > Our reclaim process has several tracepoints to tell us more about how > things are progressing. We are, however, missing a tracepoint to track > active list aging. Introduce mm_vmscan_lru_shrink_active which

Re: [PATCH] ib umem: bugfix: mixed put_pid()s in ib_umem_get()

On Thu, Dec 29, 2016 at 10:24:43AM +0800, Kenneth Lee wrote: > There are two bugfixes in this patch: > > 1. When the execution go to the ib_umem_odp_get() path, pid should be put >back. > 2. When the memory allocation fail, the pid also should be put back before >exit. > > Signed-off-by:

Re: [PATCH] ib umem: bugfix: mixed put_pid()s in ib_umem_get()

On Thu, Dec 29, 2016 at 10:24:43AM +0800, Kenneth Lee wrote: > There are two bugfixes in this patch: > > 1. When the execution go to the ib_umem_odp_get() path, pid should be put >back. > 2. When the memory allocation fail, the pid also should be put back before >exit. > > Signed-off-by:

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, 28 Dec 2016 20:16:56 -0800 Linus Torvalds wrote: > On Wed, Dec 28, 2016 at 8:08 PM, Nicholas Piggin wrote: > > > > Okay. The name could be a bit better though I think, for readability. > > Just a BUILD_BUG_ON if it is not constant and

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, 28 Dec 2016 20:16:56 -0800 Linus Torvalds wrote: > On Wed, Dec 28, 2016 at 8:08 PM, Nicholas Piggin wrote: > > > > Okay. The name could be a bit better though I think, for readability. > > Just a BUILD_BUG_ON if it is not constant and correct bit numbers? > > I have a slightly edited

Re: [PATCH v3 3/4] dt-bindings: phy: Add support for QMP phy

On Thu, Dec 29, 2016 at 4:34 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> + >> +Example: >> + pcie_phy: phy@34000 { >> + compatible = "qcom,msm8996-qmp-pcie-phy"; >> + reg = <0x034000 0x48f>, >> + <0x035000

Re: [PATCH v3 3/4] dt-bindings: phy: Add support for QMP phy

On Thu, Dec 29, 2016 at 4:34 AM, Stephen Boyd wrote: > On 12/20, Vivek Gautam wrote: >> + >> +Example: >> + pcie_phy: phy@34000 { >> + compatible = "qcom,msm8996-qmp-pcie-phy"; >> + reg = <0x034000 0x48f>, >> + <0x035000 0x5bf>, >> +

[PATCH] mtd: nand: Update dependency of IFC for LS1021A

As NAND support for Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. Signed-off-by: Alison Wang --- drivers/mtd/nand/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/Kconfig

[PATCH] mtd: nand: Update dependency of IFC for LS1021A

As NAND support for Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. Signed-off-by: Alison Wang --- drivers/mtd/nand/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig index

Re: [PATCH] net: fix incorrect original ingress device index in PKTINFO

On 12/27/16 12:03 PM, David Miller wrote: > From: Wei Zhang > Date: Tue, 27 Dec 2016 17:52:24 +0800 > >> When we send a packet for our own local address on a non-loopback >> interface (e.g. eth0), due to the change had been introduced from >> commit 0b922b7a829c ("net:

Re: [PATCH] net: fix incorrect original ingress device index in PKTINFO

On 12/27/16 12:03 PM, David Miller wrote: > From: Wei Zhang > Date: Tue, 27 Dec 2016 17:52:24 +0800 > >> When we send a packet for our own local address on a non-loopback >> interface (e.g. eth0), due to the change had been introduced from >> commit 0b922b7a829c ("net: original ingress device

[PATCH] scsi: mpt3sas: fix hang on ata passthru commands

On ata passthru commands scsih_qcmd() ends up spinning in scsi_wait_for_queuecommand() indefinitely. scsih_qcmd() is called from __blk_run_queue_uncond() which first increments request_fn_active to a non-zero value. Thus, scsi_wait_for_queuecommand() never completes because its spinning waiting

[PATCH] scsi: mpt3sas: fix hang on ata passthru commands

On ata passthru commands scsih_qcmd() ends up spinning in scsi_wait_for_queuecommand() indefinitely. scsih_qcmd() is called from __blk_run_queue_uncond() which first increments request_fn_active to a non-zero value. Thus, scsi_wait_for_queuecommand() never completes because its spinning waiting

Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines

On Wed, 28 Dec 2016 15:03:02 +0100, Wolfram Sang said: > > I have absolutely no idea how to you want to achieve calling that > > i2c_new_device() registration > > without kernel patches. > > Documentation/i2c/instantiating-devices lists all supported methods. > Method 4 is userspace instantiation.

Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines

On Wed, 28 Dec 2016 15:03:02 +0100, Wolfram Sang said: > > I have absolutely no idea how to you want to achieve calling that > > i2c_new_device() registration > > without kernel patches. > > Documentation/i2c/instantiating-devices lists all supported methods. > Method 4 is userspace instantiation.

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, Dec 28, 2016 at 8:08 PM, Nicholas Piggin wrote: > > Okay. The name could be a bit better though I think, for readability. > Just a BUILD_BUG_ON if it is not constant and correct bit numbers? I have a slightly edited patch - moved the comments around and added some new

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, Dec 28, 2016 at 8:08 PM, Nicholas Piggin wrote: > > Okay. The name could be a bit better though I think, for readability. > Just a BUILD_BUG_ON if it is not constant and correct bit numbers? I have a slightly edited patch - moved the comments around and added some new comments (about

4.9-rt: uprev notes, incremental uprev, adding bisection ability

TL;DR: incremental -rt patch uprev from 4.8-rt to the new 4.9-rt covering 175 touch down points on mainline merges & tags by Linus; useful for rt developers and bugfixers to research and bisect with. If you just want the bisect points generated on your machine, then: mkdir rt-test cd

4.9-rt: uprev notes, incremental uprev, adding bisection ability

TL;DR: incremental -rt patch uprev from 4.8-rt to the new 4.9-rt covering 175 touch down points on mainline merges & tags by Linus; useful for rt developers and bugfixers to research and bisect with. If you just want the bisect points generated on your machine, then: mkdir rt-test cd

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, 28 Dec 2016 11:17:00 -0800 Linus Torvalds wrote: > On Tue, Dec 27, 2016 at 7:53 PM, Nicholas Piggin wrote: > >> > >> Yeah, that patch is disgusting, and doesn't even help x86. > > > > No, although it would help some cases (but granted

Re: [PATCH 2/2] mm: add PageWaiters indicating tasks are waiting for a page bit

On Wed, 28 Dec 2016 11:17:00 -0800 Linus Torvalds wrote: > On Tue, Dec 27, 2016 at 7:53 PM, Nicholas Piggin wrote: > >> > >> Yeah, that patch is disgusting, and doesn't even help x86. > > > > No, although it would help some cases (but granted the bitops tend to > > be problematic in this

Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits

2016-11-21 20:26 GMT+08:00 Peter Zijlstra : > On Mon, Nov 21, 2016 at 12:14:32PM +, Juri Lelli wrote: >> On 21/11/16 11:19, Peter Zijlstra wrote: > >> > So no tunables and rate limits here at all please. >> > >> > During LPC we discussed the rampup and decay issues and

Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits

2016-11-21 20:26 GMT+08:00 Peter Zijlstra : > On Mon, Nov 21, 2016 at 12:14:32PM +, Juri Lelli wrote: >> On 21/11/16 11:19, Peter Zijlstra wrote: > >> > So no tunables and rate limits here at all please. >> > >> > During LPC we discussed the rampup and decay issues and decided that we >> >

Re: [PATCH] ceph: cleanup ACCESS_ONCE -> READ_ONCE

> On 26 Dec 2016, at 17:26, Seraphime Kirkovski wrote: > > This removes the uses of ACCESS_ONCE in favor of READ_ONCE > > Signed-off-by: Seraphime Kirkovski > --- > fs/ceph/addr.c | 4 ++-- > fs/ceph/caps.c | 2 +- > fs/ceph/dir.c

Re: [PATCH] ceph: cleanup ACCESS_ONCE -> READ_ONCE

> On 26 Dec 2016, at 17:26, Seraphime Kirkovski wrote: > > This removes the uses of ACCESS_ONCE in favor of READ_ONCE > > Signed-off-by: Seraphime Kirkovski > --- > fs/ceph/addr.c | 4 ++-- > fs/ceph/caps.c | 2 +- > fs/ceph/dir.c| 2 +- > fs/ceph/inode.c | 2 +- >

Re: [1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Wed, Dec 21, 2016 at 03:49:35AM -0800, Bjorn Andersson wrote: > As per the device tree binding the apq8064 scm node requires the core > clock to be specified, so add this. > > Cc: John Stultz > Signed-off-by: Bjorn Andersson > --- >

Re: [1/5] ARM: dts: qcom: apq8064: Add missing scm clock

On Wed, Dec 21, 2016 at 03:49:35AM -0800, Bjorn Andersson wrote: > As per the device tree binding the apq8064 scm node requires the core > clock to be specified, so add this. > > Cc: John Stultz > Signed-off-by: Bjorn Andersson > --- > arch/arm/boot/dts/qcom-apq8064.dtsi | 3 +++ > 1 file

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

Hi Randy, On 12/29/2016 12:34 AM, Randy Li wrote: > This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. > It is reported that making RK3288 can't boot from eMMC/MMC. Could you explain in more detail? As you mentioned, this patch is making that RK3288 can't boot..then why? Good way

Re: [PATCH] Revert "mmc: dw_mmc-rockchip: add runtime PM support"

Hi Randy, On 12/29/2016 12:34 AM, Randy Li wrote: > This reverts commit f90142683f04bcb0729bf0df67a5e29562b725b9. > It is reported that making RK3288 can't boot from eMMC/MMC. Could you explain in more detail? As you mentioned, this patch is making that RK3288 can't boot..then why? Good way

Re: [PATCH 3/6] ubifs: Use 64bit readdir cookies

On Thu, Dec 01, 2016 at 11:02:18PM +0100, Richard Weinberger wrote: > This is the first step to support proper telldir/seekdir() > in UBIFS. > Let's report 64bit cookies in readdir(). The cookie is a combination > of the entry key plus the double hash value. Would it be possible to explain what

Re: [PATCH 3/6] ubifs: Use 64bit readdir cookies

On Thu, Dec 01, 2016 at 11:02:18PM +0100, Richard Weinberger wrote: > This is the first step to support proper telldir/seekdir() > in UBIFS. > Let's report 64bit cookies in readdir(). The cookie is a combination > of the entry key plus the double hash value. Would it be possible to explain what

Re: [PATCH 6/6] ubifs: Wire up NFS support

On Thu, Dec 01, 2016 at 11:02:21PM +0100, Richard Weinberger wrote: > Since we have 64bit readdir cookies and export operations > we can finally enable NFS export support for UBIFS. > > Signed-off-by: Richard Weinberger > --- > fs/ubifs/dir.c | 9 ++--- > fs/ubifs/super.c

Re: [PATCH 6/6] ubifs: Wire up NFS support

On Thu, Dec 01, 2016 at 11:02:21PM +0100, Richard Weinberger wrote: > Since we have 64bit readdir cookies and export operations > we can finally enable NFS export support for UBIFS. > > Signed-off-by: Richard Weinberger > --- > fs/ubifs/dir.c | 9 ++--- > fs/ubifs/super.c | 3 +++ > 2

Re: [PATCH v2 2/4] ocfs2: fix some small problems

>>> > Hi Gang, one small comment below: > > On Wed, Dec 21, 2016 at 2:20 AM, Gang He wrote: >> First, move setting fe_done = 1 in spin lock, avoid bring >> any potential race condition. Second, tune mlog message level >> from ERROR to NOTICE, since the message should not

Re: [PATCH v2 2/4] ocfs2: fix some small problems

>>> > Hi Gang, one small comment below: > > On Wed, Dec 21, 2016 at 2:20 AM, Gang He wrote: >> First, move setting fe_done = 1 in spin lock, avoid bring >> any potential race condition. Second, tune mlog message level >> from ERROR to NOTICE, since the message should not belong to >> error

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On 12/26/2016 09:24 PM, Kirill A. Shutemov wrote: > On Mon, Dec 26, 2016 at 06:06:01PM -0800, Andy Lutomirski wrote: >> On Mon, Dec 26, 2016 at 5:54 PM, Kirill A. Shutemov >> wrote: >>> This patch introduces new rlimit resource to manage maximum virtual >>>

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On 12/26/2016 09:24 PM, Kirill A. Shutemov wrote: > On Mon, Dec 26, 2016 at 06:06:01PM -0800, Andy Lutomirski wrote: >> On Mon, Dec 26, 2016 at 5:54 PM, Kirill A. Shutemov >> wrote: >>> This patch introduces new rlimit resource to manage maximum virtual >>> address available to userspace to map.

[PATCH v5 3/4] clk: rockchip: add new pll-type for rk3328

The rk3328's pll and clock are similar with rk3036's, it different with pll_mode_mask, the rk3328 soc pll mode only one bit(rk3036 soc have two bits) so these should be independent and separate from the series of rk3328s. Changes in v4: adjust the pacth 3 and 4 order. move pll_rk3328 to patch

[PATCH v5 2/4] dt-bindings: add bindings for rk3328 clock controller

Add devicetree bindings for Rockchip cru which found on Rockchip SoCs. Changes in v4: dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328 Signed-off-by: Elaine Zhang --- .../bindings/clock/rockchip,rk3328-cru.txt | 57

[PATCH v5 3/4] clk: rockchip: add new pll-type for rk3328

The rk3328's pll and clock are similar with rk3036's, it different with pll_mode_mask, the rk3328 soc pll mode only one bit(rk3036 soc have two bits) so these should be independent and separate from the series of rk3328s. Changes in v4: adjust the pacth 3 and 4 order. move pll_rk3328 to patch

[PATCH v5 2/4] dt-bindings: add bindings for rk3328 clock controller

Add devicetree bindings for Rockchip cru which found on Rockchip SoCs. Changes in v4: dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328 Signed-off-by: Elaine Zhang --- .../bindings/clock/rockchip,rk3328-cru.txt | 57 ++ 1 file changed, 57

[PATCH v5 1/4] clk: rockchip: add dt-binding header for rk3328

Add the dt-bindings header for the rk3328, that gets shared between the clock controller and the clock references in the dts. Add softreset ID for rk3328. Signed-off-by: Elaine Zhang --- include/dt-bindings/clock/rk3328-cru.h | 403 + 1

[PATCH v5 4/4] clk: rockchip: add clock controller for rk3328

Add the clock tree definition for the new rk3328 SoC. Changes in v5: fix up some code style, remove grf clk init and cru dump. Changes in v4: adjust the pacth 3 and 4 order. Changes in v3: fix up the pll parent only xin24m. Changes in v2: fix up these *_sample error description.

[PATCH v5 0/4] clk: rockchip: support clk controller for rk3328 SoC

Changes in v5: fix up some code style, remove grf clk init and cru dump. Changes in v4: dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328 adjust the pacth 3 and 4 order. move pll_rk3328 to patch 3. Changes in v3: fix up the pll type pll_rk3328 description and

[PATCH v5 0/4] clk: rockchip: support clk controller for rk3328 SoC

Changes in v5: fix up some code style, remove grf clk init and cru dump. Changes in v4: dropping the "rockchip,cru" and "syscon" properties for bindings of rk3328 adjust the pacth 3 and 4 order. move pll_rk3328 to patch 3. Changes in v3: fix up the pll type pll_rk3328 description and

[PATCH v5 1/4] clk: rockchip: add dt-binding header for rk3328

Add the dt-bindings header for the rk3328, that gets shared between the clock controller and the clock references in the dts. Add softreset ID for rk3328. Signed-off-by: Elaine Zhang --- include/dt-bindings/clock/rk3328-cru.h | 403 + 1 file changed, 403

[PATCH v5 4/4] clk: rockchip: add clock controller for rk3328

Add the clock tree definition for the new rk3328 SoC. Changes in v5: fix up some code style, remove grf clk init and cru dump. Changes in v4: adjust the pacth 3 and 4 order. Changes in v3: fix up the pll parent only xin24m. Changes in v2: fix up these *_sample error description.

[PATCH] mm: Drop "PFNs busy" printk in an expected path.

For CMA allocations, we expect to occasionally hit this error path, at which point CMA will retry. Given that, we shouldn't be spamming dmesg about it. The Raspberry Pi graphics driver does frequent CMA allocations, and during regression testing this printk was sometimes occurring 100s of times

[PATCH] mm: Drop "PFNs busy" printk in an expected path.

For CMA allocations, we expect to occasionally hit this error path, at which point CMA will retry. Given that, we shouldn't be spamming dmesg about it. The Raspberry Pi graphics driver does frequent CMA allocations, and during regression testing this printk was sometimes occurring 100s of times

[PATCH] mm: cma: print allocation failure reason and bitmap status

There are many reasons of CMA allocation failure such as EBUSY, ENOMEM, EINTR. This patch prints the error value and bitmap status to know available pages regarding fragmentation. This is an ENOMEM example with this patch. [ 11.616321] [2: Binder:711_1: 740] cma: cma_alloc: alloc failed,

[PATCH] mm: cma: print allocation failure reason and bitmap status

There are many reasons of CMA allocation failure such as EBUSY, ENOMEM, EINTR. This patch prints the error value and bitmap status to know available pages regarding fragmentation. This is an ENOMEM example with this patch. [ 11.616321] [2: Binder:711_1: 740] cma: cma_alloc: alloc failed,

  1   2   3   4   5   6   7   >