Re: [PATCH v2 02/12] scsi: ufs: add tracing support

On 2016-12-13 12:10, Steven Rostedt wrote: On Tue, 13 Dec 2016 11:48:45 -0800 Subhash Jadavani wrote: This change adds the ftrace support for following: 1. UFS initialization time 2. Clock gating states 3. Clock scaling states 4. Power management APIs latency 5. BKOPs

Re: [PATCH v2 02/12] scsi: ufs: add tracing support

On 2016-12-13 12:10, Steven Rostedt wrote: On Tue, 13 Dec 2016 11:48:45 -0800 Subhash Jadavani wrote: This change adds the ftrace support for following: 1. UFS initialization time 2. Clock gating states 3. Clock scaling states 4. Power management APIs latency 5. BKOPs enable/disable Usage:

[RFC v4 03/16] iommu: Add a new type field in iommu_resv_region

We introduce a new field to differentiate the reserved region types and specialize the apply_resv_region implementation. Legacy direct mapped regions have IOMMU_RESV_DIRECT type. We introduce 2 new reserved memory types: - IOMMU_RESV_MSI will characterize MSI regions - IOMMU_RESV_NOMAP

[RFC v4 03/16] iommu: Add a new type field in iommu_resv_region

We introduce a new field to differentiate the reserved region types and specialize the apply_resv_region implementation. Legacy direct mapped regions have IOMMU_RESV_DIRECT type. We introduce 2 new reserved memory types: - IOMMU_RESV_MSI will characterize MSI regions - IOMMU_RESV_NOMAP

[RFC v4 02/16] iommu: Rename iommu_dm_regions into iommu_resv_regions

We want to extend the callbacks used for dm regions and use them for reserved regions. Reserved regions can be - directly mapped regions - regions that cannot be iommu mapped (PCI host bridge windows, ...) - MSI regions (because they belong to another address space or because they are not

[RFC v4 02/16] iommu: Rename iommu_dm_regions into iommu_resv_regions

We want to extend the callbacks used for dm regions and use them for reserved regions. Reserved regions can be - directly mapped regions - regions that cannot be iommu mapped (PCI host bridge windows, ...) - MSI regions (because they belong to another address space or because they are not

[RFC v4 00/16] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Following LPC discussions, we now report reserved regions through iommu-group sysfs reserved_regions attribute file. Reserved regions are populated through the IOMMU get_resv_region callback (former get_dm_regions), now implemented by amd-iommu, intel-iommu and arm-smmu: - the amd-iommu reports

[RFC v4 00/16] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Following LPC discussions, we now report reserved regions through iommu-group sysfs reserved_regions attribute file. Reserved regions are populated through the IOMMU get_resv_region callback (former get_dm_regions), now implemented by amd-iommu, intel-iommu and arm-smmu: - the amd-iommu reports

Re: [RFC 1/2] powerpc/32: Unset MSR RI in exception epilogs

Le 13/12/2016 à 20:15, Segher Boessenkool a écrit : On Tue, Dec 13, 2016 at 07:19:41PM +0100, Christophe Leroy wrote: At exception prologs, once SRR0 and SRR1 have been saved, MSR RI is set to mark the interrupt as recoverable. MSR RI has to be unset before writing into SRR0 and SRR1 at

Re: [RFC 1/2] powerpc/32: Unset MSR RI in exception epilogs

Le 13/12/2016 à 20:15, Segher Boessenkool a écrit : On Tue, Dec 13, 2016 at 07:19:41PM +0100, Christophe Leroy wrote: At exception prologs, once SRR0 and SRR1 have been saved, MSR RI is set to mark the interrupt as recoverable. MSR RI has to be unset before writing into SRR0 and SRR1 at

[RFC v4 01/16] iommu/dma: Allow MSI-only cookies

IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually really simple for other users to piggyback

[RFC v4 01/16] iommu/dma: Allow MSI-only cookies

IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually really simple for other users to piggyback

Re: usb/core: warning in usb_create_ep_devs/sysfs_create_dir_ns

"On Tue, Dec 13, 2016 at 9:09 PM, Alan Stern wrote: > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > >> On Tue, Dec 13, 2016 at 7:38 PM, Alan Stern >> wrote: >> > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: >> > >> >> On Tue, Dec 13, 2016 at 4:52

Re: usb/core: warning in usb_create_ep_devs/sysfs_create_dir_ns

"On Tue, Dec 13, 2016 at 9:09 PM, Alan Stern wrote: > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > >> On Tue, Dec 13, 2016 at 7:38 PM, Alan Stern >> wrote: >> > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: >> > >> >> On Tue, Dec 13, 2016 at 4:52 PM, Alan Stern >> >> wrote: >> >> > On Tue, 13 Dec

[RFC v4 04/16] iommu: iommu_alloc_resv_region

Introduce a new helper serving the purpose to allocate a reserved region. This will be used in iommu driver implementing reserved region callbacks. Signed-off-by: Eric Auger --- v3 -> v4: - add INIT_LIST_HEAD(>list) - use int for prot param and add int type param -

[RFC v4 04/16] iommu: iommu_alloc_resv_region

Introduce a new helper serving the purpose to allocate a reserved region. This will be used in iommu driver implementing reserved region callbacks. Signed-off-by: Eric Auger --- v3 -> v4: - add INIT_LIST_HEAD(>list) - use int for prot param and add int type param - remove implementation

[RFC v4 16/16] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore

IOMMU_CAP_INTR_REMAP has been advertised in arm-smmu(-v3) although on ARM this property is not attached to the IOMMU but rather is implemented in the MSI controller (GICv3 ITS). Now vfio_iommu_type1 takes into account the MSI domain MSI remapping capability, let's correct this. Signed-off-by:

[RFC v4 16/16] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore

IOMMU_CAP_INTR_REMAP has been advertised in arm-smmu(-v3) although on ARM this property is not attached to the IOMMU but rather is implemented in the MSI controller (GICv3 ITS). Now vfio_iommu_type1 takes into account the MSI domain MSI remapping capability, let's correct this. Signed-off-by:

[RFC v4 05/16] iommu: Only map direct mapped regions

As we introduced new reserved region types which do not require mapping, let's make sure we only map direct mapped regions. Signed-off-by: Eric Auger --- v3 -> v4: - use region's type and reword commit message and title --- drivers/iommu/iommu.c | 3 +++ 1 file changed,

[RFC v4 05/16] iommu: Only map direct mapped regions

As we introduced new reserved region types which do not require mapping, let's make sure we only map direct mapped regions. Signed-off-by: Eric Auger --- v3 -> v4: - use region's type and reword commit message and title --- drivers/iommu/iommu.c | 3 +++ 1 file changed, 3 insertions(+) diff

Re: [PATCH v3 0/4] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/09/2016 03:36 PM, Florian Fainelli wrote: > This patch series builds on top of Laura's [PATCHv5 00/10] > CONFIG_DEBUG_VIRTUAL > for arm64 to add support for CONFIG_DEBUG_VIRTUAL for ARM. > > This was tested on a Brahma B15 platform (ARMv7 + HIGHMEM + LPAE). > > Note that the treewide

Re: [PATCH v3 0/4] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/09/2016 03:36 PM, Florian Fainelli wrote: > This patch series builds on top of Laura's [PATCHv5 00/10] > CONFIG_DEBUG_VIRTUAL > for arm64 to add support for CONFIG_DEBUG_VIRTUAL for ARM. > > This was tested on a Brahma B15 platform (ARMv7 + HIGHMEM + LPAE). > > Note that the treewide

[PATCH v2] memory_hotplug: zone_can_shift() returns boolean value

online_{kernel|movable} is used to change the memory zone to ZONE_{NORMAL|MOVABLE} and online the memory. To check that memory zone can be changed, zone_can_shift() is used. Currently the function returns minus integer value, plus integer value and 0. When the function returns minus or plus

[PATCH v2] memory_hotplug: zone_can_shift() returns boolean value

online_{kernel|movable} is used to change the memory zone to ZONE_{NORMAL|MOVABLE} and online the memory. To check that memory zone can be changed, zone_can_shift() is used. Currently the function returns minus integer value, plus integer value and 0. When the function returns minus or plus

[PATCH 4/5] radix tree test suite: Delete unused rcupdate.c

From: Matthew Wilcox This file was used to implement call_rcu() before liburcu implemented that function. It hasn't even been compiled since before the test suite was added to the kernel. Remove it to reduce confusion. Signed-off-by: Matthew Wilcox

[PATCH 4/5] radix tree test suite: Delete unused rcupdate.c

From: Matthew Wilcox This file was used to implement call_rcu() before liburcu implemented that function. It hasn't even been compiled since before the test suite was added to the kernel. Remove it to reduce confusion. Signed-off-by: Matthew Wilcox --- tools/testing/radix-tree/rcupdate.c |

[PATCH 5/5] Reimplement IDR and IDA using the radix tree

From: Matthew Wilcox The IDR is very similar to the radix tree. It has some functionality that the radix tree did not have (alloc next free, cyclic allocation, a callback-based for_each, destroy tree), which is readily implementable on top of the radix tree. A few small

[PATCH 5/5] Reimplement IDR and IDA using the radix tree

From: Matthew Wilcox The IDR is very similar to the radix tree. It has some functionality that the radix tree did not have (alloc next free, cyclic allocation, a callback-based for_each, destroy tree), which is readily implementable on top of the radix tree. A few small changes were needed in

[PATCH 0/5] Additional radix tree patches for 4.10

From: Matthew Wilcox Hi Andrew, One bug has popped up in testing which is reasonably hard to hit (fixed by patch 2 in this series). I needed to change the test suite to be able to catch the bug in action. The test suite was returning freed memory to glibc's malloc, but

[PATCH 0/5] Additional radix tree patches for 4.10

From: Matthew Wilcox Hi Andrew, One bug has popped up in testing which is reasonably hard to hit (fixed by patch 2 in this series). I needed to change the test suite to be able to catch the bug in action. The test suite was returning freed memory to glibc's malloc, but we have to keep a cache

[PATCH 1/5] radix tree test suite: Cache recently freed objects

From: Matthew Wilcox The kmem_cache_alloc implementation simply allocates new memory from malloc() and calls the ctor, which zeroes out the entire object. This means it cannot spot bugs where the object isn't properly reinitialised before being freed. Add a small (11

[PATCH 1/5] radix tree test suite: Cache recently freed objects

From: Matthew Wilcox The kmem_cache_alloc implementation simply allocates new memory from malloc() and calls the ctor, which zeroes out the entire object. This means it cannot spot bugs where the object isn't properly reinitialised before being freed. Add a small (11 objects) cache before

[PATCH 2/5] radix-tree: Ensure counts are initialised

From: Matthew Wilcox radix_tree_join() was freeing nodes with a non-zero ->exceptional count, and radix_tree_split() wasn't zeroing ->exceptional when it allocated the new node. Fix this by making all callers of radix_tree_node_alloc() pass in the new counts (and some

Re: page allocation stall in kernel 4.9 when copying files from one btrfs hdd to another

Hi, unfortunately I did not dump meminfo before the crash. Here is the actual meminfo as of now with the copy running for about 3 hours. MemTotal: 32806572 kB MemFree: 197336 kB MemAvailable: 31226888 kB Buffers: 52 kB Cached: 30603160 kB SwapCached:

[PATCH 3/5] radix tree test suite: Add new tag check

From: Matthew Wilcox We have a check that setting a tag on a single entry at root succeeds, but we were missing a check that clearing a tag on that same entry also succeeds. Signed-off-by: Matthew Wilcox --- tools/testing/radix-tree/tag_check.c

[PATCH 2/5] radix-tree: Ensure counts are initialised

From: Matthew Wilcox radix_tree_join() was freeing nodes with a non-zero ->exceptional count, and radix_tree_split() wasn't zeroing ->exceptional when it allocated the new node. Fix this by making all callers of radix_tree_node_alloc() pass in the new counts (and some other always-initialised

Re: page allocation stall in kernel 4.9 when copying files from one btrfs hdd to another

Hi, unfortunately I did not dump meminfo before the crash. Here is the actual meminfo as of now with the copy running for about 3 hours. MemTotal: 32806572 kB MemFree: 197336 kB MemAvailable: 31226888 kB Buffers: 52 kB Cached: 30603160 kB SwapCached:

[PATCH 3/5] radix tree test suite: Add new tag check

From: Matthew Wilcox We have a check that setting a tag on a single entry at root succeeds, but we were missing a check that clearing a tag on that same entry also succeeds. Signed-off-by: Matthew Wilcox --- tools/testing/radix-tree/tag_check.c | 3 +++ 1 file changed, 3 insertions(+) diff

Re: [PATCH 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

> This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting > cells. comments below > The protocol is quite simple and using GPIO's: GPIOs > One GPIO is used as clock (SCK) while another GPIO is read (DOUT) > > Signed-off-by: Andreas Klinger > --- >

Re: [PATCH 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

> This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting > cells. comments below > The protocol is quite simple and using GPIO's: GPIOs > One GPIO is used as clock (SCK) while another GPIO is read (DOUT) > > Signed-off-by: Andreas Klinger > --- >

Re: [PATCH v2 11/12] scsi: ufs: add trace event for ufs commands

On Tue, 13 Dec 2016 11:52:16 -0800 Subhash Jadavani wrote: > From: Lee Susman > > Use the ftrace infrastructure to conditionally trace ufs command events. > New trace event is created, which samples the following ufs command data: > - device

Re: [PATCH v2 11/12] scsi: ufs: add trace event for ufs commands

On Tue, 13 Dec 2016 11:52:16 -0800 Subhash Jadavani wrote: > From: Lee Susman > > Use the ftrace infrastructure to conditionally trace ufs command events. > New trace event is created, which samples the following ufs command data: > - device name > - optional identification string > - task tag

Re: [GIT PULL] Block core changes for 4.10

On 12/11/2016 06:52 PM, Jens Axboe wrote: > Note that this pull will throw 3 trivial merge conflicts, since we had > patches that went into mainline after 4.9-rc1 (upon which this branch is > based), and one that will not show up in block/blk-flush.c. The latter > is due to a fix that went in for

Re: [GIT PULL] Block core changes for 4.10

On 12/11/2016 06:52 PM, Jens Axboe wrote: > Note that this pull will throw 3 trivial merge conflicts, since we had > patches that went into mainline after 4.9-rc1 (upon which this branch is > based), and one that will not show up in block/blk-flush.c. The latter > is due to a fix that went in for

Re: [PATCH v1 07/12] scsi: ufs: add option to change default UFS power management level

On 2016-12-13 12:04, Rob Herring wrote: On Mon, Dec 12, 2016 at 04:54:20PM -0800, Subhash Jadavani wrote: UFS device and link can be put in multiple different low power modes hence UFS driver supports multiple different low power modes. By default UFS driver selects the default (optimal) low

Re: [PATCH v1 07/12] scsi: ufs: add option to change default UFS power management level

On 2016-12-13 12:04, Rob Herring wrote: On Mon, Dec 12, 2016 at 04:54:20PM -0800, Subhash Jadavani wrote: UFS device and link can be put in multiple different low power modes hence UFS driver supports multiple different low power modes. By default UFS driver selects the default (optimal) low

Re: usb/core: warning in usb_create_ep_devs/sysfs_create_dir_ns

On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > On Tue, Dec 13, 2016 at 7:38 PM, Alan Stern wrote: > > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > > > >> On Tue, Dec 13, 2016 at 4:52 PM, Alan Stern > >> wrote: > >> > On Tue, 13 Dec 2016, Dmitry

Re: [PATCH 1/2] iio: adc: hx711: Add DT binding for avia,hx711

> Add DT bindings for avia,hx711 > Add vendor avia to vendor list > > Signed-off-by: Andreas Klinger > --- > .../devicetree/bindings/iio/adc/avia-hx711.txt | 23 > ++ > .../devicetree/bindings/vendor-prefixes.txt| 1 + > 2 files changed, 24

Re: usb/core: warning in usb_create_ep_devs/sysfs_create_dir_ns

On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > On Tue, Dec 13, 2016 at 7:38 PM, Alan Stern wrote: > > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > > > >> On Tue, Dec 13, 2016 at 4:52 PM, Alan Stern > >> wrote: > >> > On Tue, 13 Dec 2016, Dmitry Vyukov wrote: > >> > > >> >> >> > If it is > >> >>

Re: [PATCH 1/2] iio: adc: hx711: Add DT binding for avia,hx711

> Add DT bindings for avia,hx711 > Add vendor avia to vendor list > > Signed-off-by: Andreas Klinger > --- > .../devicetree/bindings/iio/adc/avia-hx711.txt | 23 > ++ > .../devicetree/bindings/vendor-prefixes.txt| 1 + > 2 files changed, 24 insertions(+) >

Re: [PATCH 3/9] dt-bindings: stm32-dma: Fix typo regarding DMA client binding

On Tue, Dec 13, 2016 at 02:40:45PM +0100, M'boumba Cedric Madianga wrote: > Only four cells are required for dma client binding not five. > > Signed-off-by: M'boumba Cedric Madianga > Reviewed-by: Ludovic BARRE > --- >

Re: [PATCH 3/9] dt-bindings: stm32-dma: Fix typo regarding DMA client binding

On Tue, Dec 13, 2016 at 02:40:45PM +0100, M'boumba Cedric Madianga wrote: > Only four cells are required for dma client binding not five. > > Signed-off-by: M'boumba Cedric Madianga > Reviewed-by: Ludovic BARRE > --- > Documentation/devicetree/bindings/dma/stm32-dma.txt | 5 ++--- > 1 file

Re: [PATCH] keys/encrypted: Fix two crypto-on-the-stack bugs

Andy Lutomirski wrote: > I don't know whether you're right, but that sounds a bit silly to me. > This is a *tiny* amount of memory. Assuming a 1MiB kernel image in 4K pages, that gets you back a couple of pages I think - useful if you've only got a few MiB of RAM. David

Re: [PATCH v2 02/12] scsi: ufs: add tracing support

On Tue, 13 Dec 2016 11:48:45 -0800 Subhash Jadavani wrote: > This change adds the ftrace support for following: > 1. UFS initialization time > 2. Clock gating states > 3. Clock scaling states > 4. Power management APIs latency > 5. BKOPs enable/disable > > Usage: >

Re: [PATCH] keys/encrypted: Fix two crypto-on-the-stack bugs

Andy Lutomirski wrote: > I don't know whether you're right, but that sounds a bit silly to me. > This is a *tiny* amount of memory. Assuming a 1MiB kernel image in 4K pages, that gets you back a couple of pages I think - useful if you've only got a few MiB of RAM. David

Re: [PATCH v2 02/12] scsi: ufs: add tracing support

On Tue, 13 Dec 2016 11:48:45 -0800 Subhash Jadavani wrote: > This change adds the ftrace support for following: > 1. UFS initialization time > 2. Clock gating states > 3. Clock scaling states > 4. Power management APIs latency > 5. BKOPs enable/disable > > Usage: > echo 1 >

Re: [PATCH 4.8 00/33] 4.8.15-stable review

On Tue, Dec 13, 2016 at 12:32:17PM -0700, Shuah Khan wrote: > On 12/13/2016 10:16 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.15 release. > > There are 33 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 3.12 07/38] tty: audit: Fix audit source

From: Peter Hurley 3.12-stable review patch. If anyone has any objections, please let me know. === commit 6b2a3d628aa752f0ab825fc6d4d07b09e274d1c1 upstream. The data to audit/record is in the 'from' buffer (ie., the input read buffer). Fixes:

[PATCH 3.12 06/38] kernel/panic.c: turn off locks debug before releasing console lock

From: Vitaly Kuznetsov 3.12-stable review patch. If anyone has any objections, please let me know. === commit 7625b3a0007decf2b135cb47ca67abc78a7b1bc1 upstream. Commit 08d78658f393 ("panic: release stale console lock to always get the logbuf printed out")

[PATCH 3.12 05/38] mtd: blkdevs: fix potential deadlock + lockdep warnings

From: Brian Norris 3.12-stable review patch. If anyone has any objections, please let me know. === commit f3c63795e90f0c6238306883b6c72f14d5355721 upstream. Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing mtd->usecount") fixed a

[PATCH 3.12 04/38] i2c: at91: fix write transfers by clearing pending interrupt first

From: Cyrille Pitchen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 6f6ddbb09d2a5baded0e23add3ad2d9e9417ab30 upstream. In some cases a NACK interrupt may be pending in the Status Register (SR) as a result of a

Re: [PATCH v2 2/2] crypto: mediatek - add DT bindings documentation

On Tue, Dec 13, 2016 at 09:31:16AM +0800, Ryder Lee wrote: > Add DT bindings documentation for the crypto driver > > Signed-off-by: Ryder Lee > --- > .../devicetree/bindings/crypto/mediatek-crypto.txt | 32 > ++ > 1 file changed, 32 insertions(+) >

Re: [PATCH 4.8 00/33] 4.8.15-stable review

On Tue, Dec 13, 2016 at 12:32:17PM -0700, Shuah Khan wrote: > On 12/13/2016 10:16 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.15 release. > > There are 33 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 3.12 07/38] tty: audit: Fix audit source

From: Peter Hurley 3.12-stable review patch. If anyone has any objections, please let me know. === commit 6b2a3d628aa752f0ab825fc6d4d07b09e274d1c1 upstream. The data to audit/record is in the 'from' buffer (ie., the input read buffer). Fixes: 72586c6061ab ("n_tty: Fix auditing

[PATCH 3.12 06/38] kernel/panic.c: turn off locks debug before releasing console lock

From: Vitaly Kuznetsov 3.12-stable review patch. If anyone has any objections, please let me know. === commit 7625b3a0007decf2b135cb47ca67abc78a7b1bc1 upstream. Commit 08d78658f393 ("panic: release stale console lock to always get the logbuf printed out") introduced an unwanted

[PATCH 3.12 05/38] mtd: blkdevs: fix potential deadlock + lockdep warnings

From: Brian Norris 3.12-stable review patch. If anyone has any objections, please let me know. === commit f3c63795e90f0c6238306883b6c72f14d5355721 upstream. Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing mtd->usecount") fixed a race condition but due to poor

[PATCH 3.12 04/38] i2c: at91: fix write transfers by clearing pending interrupt first

From: Cyrille Pitchen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 6f6ddbb09d2a5baded0e23add3ad2d9e9417ab30 upstream. In some cases a NACK interrupt may be pending in the Status Register (SR) as a result of a previous transfer. However

Re: [PATCH v2 2/2] crypto: mediatek - add DT bindings documentation

On Tue, Dec 13, 2016 at 09:31:16AM +0800, Ryder Lee wrote: > Add DT bindings documentation for the crypto driver > > Signed-off-by: Ryder Lee > --- > .../devicetree/bindings/crypto/mediatek-crypto.txt | 32 > ++ > 1 file changed, 32 insertions(+) > create mode 100644 >

Re: [PATCH v1 07/12] scsi: ufs: add option to change default UFS power management level

On Mon, Dec 12, 2016 at 04:54:20PM -0800, Subhash Jadavani wrote: > UFS device and link can be put in multiple different low power modes hence > UFS driver supports multiple different low power modes. By default UFS > driver selects the default (optimal) low power mode (which gives moderate >

Re: [PATCH v1 07/12] scsi: ufs: add option to change default UFS power management level

On Mon, Dec 12, 2016 at 04:54:20PM -0800, Subhash Jadavani wrote: > UFS device and link can be put in multiple different low power modes hence > UFS driver supports multiple different low power modes. By default UFS > driver selects the default (optimal) low power mode (which gives moderate >

[PATCH 3.12 08/38] Revert "drivers/net: Disable UFO through virtio"

From: Vlad Yasevich 3.12-stable review patch. If anyone has any objections, please let me know. === commit e3e3c423f82a415195a7bbbfa619bfa7b20d2db6 upstream. This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that GSO functionality can

Re: [PATCH v3 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

Hari Bathini writes: > Hi Eric, > > > On Monday 12 December 2016 11:57 PM, Eric W. Biederman wrote: >> Hari Bathini writes: >> >>> With the advert of container technologies like docker, that depend >>> on namespaces for isolation, there

[PATCH 3.12 09/38] KVM: x86: drop error recovery in em_jmp_far and em_ret_far

From: Radim Krčmář 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2117d5398c81554fbf803f5fd1dc55eb78216c0c upstream. em_jmp_far and em_ret_far assumed that setting IP can only fail in 64 bit mode, but syzkaller proved

Re: page allocation stall in kernel 4.9 when copying files from one btrfs hdd to another

Hi David, It has GFP_NOFS flags, according to definition, the issue might have happened during initial DISK/IO. By the way, did you get a chance to dump the meminfo and run "top" before the system hang? It seems more info about the system running state needed to know the issue. Thanks. Xin  

[PATCH v2 01/12] scsi: ufs: dump debug info during failures

From: Dolev Raviv Inserts driver dumps for UFS Host Controller registers, Transfer Requests and Task Management Requests. The dumps will occur on driver initialization failure, ufshcd_abort() and on error handling path. Signed-off-by: Dolev Raviv

[PATCH v2 01/12] scsi: ufs: dump debug info during failures

From: Dolev Raviv Inserts driver dumps for UFS Host Controller registers, Transfer Requests and Task Management Requests. The dumps will occur on driver initialization failure, ufshcd_abort() and on error handling path. Signed-off-by: Dolev Raviv Signed-off-by: Subhash Jadavani --- Changes v1

[PATCH 3.12 08/38] Revert "drivers/net: Disable UFO through virtio"

From: Vlad Yasevich 3.12-stable review patch. If anyone has any objections, please let me know. === commit e3e3c423f82a415195a7bbbfa619bfa7b20d2db6 upstream. This reverts commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4. Now that GSO functionality can correctly track if the

Re: [PATCH v3 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

Hari Bathini writes: > Hi Eric, > > > On Monday 12 December 2016 11:57 PM, Eric W. Biederman wrote: >> Hari Bathini writes: >> >>> With the advert of container technologies like docker, that depend >>> on namespaces for isolation, there is a need for tracing support for >>> namespaces. This

[PATCH 3.12 09/38] KVM: x86: drop error recovery in em_jmp_far and em_ret_far

From: Radim Krčmář 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2117d5398c81554fbf803f5fd1dc55eb78216c0c upstream. em_jmp_far and em_ret_far assumed that setting IP can only fail in 64 bit mode, but syzkaller proved otherwise (and SDM

Re: page allocation stall in kernel 4.9 when copying files from one btrfs hdd to another

Hi David, It has GFP_NOFS flags, according to definition, the issue might have happened during initial DISK/IO. By the way, did you get a chance to dump the meminfo and run "top" before the system hang? It seems more info about the system running state needed to know the issue. Thanks. Xin  

[PATCH 3.12 11/38] USB: serial: cp210x: add ID for the Zone DPMX

From: Paul Jakma 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2ab13292d7a314fa45de0acc808e41aaad31989c upstream. The BRIM Brothers Zone DPMX is a bicycle powermeter. This ID is for the USB serial interface in its charging

[GIT PULL] ext4 updates for 4.10

The following changes since commit bc33b0ca11e3df46a4fa7639ba488c9d4911: Linux 4.9-rc4 (2016-11-05 16:23:36 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus for you to fetch changes up to

Re: [PATCH] mm-add-vfree_atomic-fix

On 12/13/2016 09:15 PM, Andy Lutomirski wrote: >>> >>> But not quite acked by me. What happened to the vfree code that >>> causes vfree_deferred to be called in a preemptable context? That >>> sounds like a bug. >> >> Not sure I understand but the above stack points to a preemptible >> context

[PATCH 3.12 10/38] usb: chipidea: move the lock initialization to core file

From: Peter Chen 3.12-stable review patch. If anyone has any objections, please let me know. === commit a5d906bb261cde5f881a949d3b0fbaa285dcc574 upstream. This can fix below dump when the lock is accessed at host mode due to it is not initialized. [

[PATCH 3.12 17/38] apparmor: fix change_hat not finding hat after policy replacement

From: John Johansen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 3d40658c977769ce2138f286cf131537bf68bdfe upstream. After a policy replacement, the task cred may be out of date and need to be updated. However

[PATCH 3.12 11/38] USB: serial: cp210x: add ID for the Zone DPMX

From: Paul Jakma 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2ab13292d7a314fa45de0acc808e41aaad31989c upstream. The BRIM Brothers Zone DPMX is a bicycle powermeter. This ID is for the USB serial interface in its charging dock for the

[GIT PULL] ext4 updates for 4.10

The following changes since commit bc33b0ca11e3df46a4fa7639ba488c9d4911: Linux 4.9-rc4 (2016-11-05 16:23:36 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus for you to fetch changes up to

Re: [PATCH] mm-add-vfree_atomic-fix

On 12/13/2016 09:15 PM, Andy Lutomirski wrote: >>> >>> But not quite acked by me. What happened to the vfree code that >>> causes vfree_deferred to be called in a preemptable context? That >>> sounds like a bug. >> >> Not sure I understand but the above stack points to a preemptible >> context

[PATCH 3.12 10/38] usb: chipidea: move the lock initialization to core file

From: Peter Chen 3.12-stable review patch. If anyone has any objections, please let me know. === commit a5d906bb261cde5f881a949d3b0fbaa285dcc574 upstream. This can fix below dump when the lock is accessed at host mode due to it is not initialized. [ 46.119638] INFO: trying to

[PATCH 3.12 17/38] apparmor: fix change_hat not finding hat after policy replacement

From: John Johansen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 3d40658c977769ce2138f286cf131537bf68bdfe upstream. After a policy replacement, the task cred may be out of date and need to be updated. However change_hat is using the stale

Re: [PATCH v4 4/4] regulator: Prevent falling too fast

Hi, On Tue, Dec 13, 2016 at 9:19 AM, Mark Brown wrote: > On Mon, Dec 12, 2016 at 01:15:02PM -0800, Matthias Kaehlcke wrote: >> El Fri, Oct 28, 2016 at 07:15:21PM +0100 Mark Brown ha dit: >> > On Mon, Sep 26, 2016 at 10:41:59AM -0700, Doug Anderson wrote: > >> > What you're

Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report

Hari Bathini writes: > Hi Eric, > > > On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote: >> Hari Bathini writes: >> >>> This patch introduces a cgroup identifier entry field in perf report to >>> identify or distinguish data

Re: [PATCH v4 4/4] regulator: Prevent falling too fast

Hi, On Tue, Dec 13, 2016 at 9:19 AM, Mark Brown wrote: > On Mon, Dec 12, 2016 at 01:15:02PM -0800, Matthias Kaehlcke wrote: >> El Fri, Oct 28, 2016 at 07:15:21PM +0100 Mark Brown ha dit: >> > On Mon, Sep 26, 2016 at 10:41:59AM -0700, Doug Anderson wrote: > >> > What you're describing to me is a

Re: [PATCH v3 3/3] perf tool: add cgroup identifier entry in perf report

Hari Bathini writes: > Hi Eric, > > > On Tuesday 13 December 2016 03:36 AM, Eric W. Biederman wrote: >> Hari Bathini writes: >> >>> This patch introduces a cgroup identifier entry field in perf report to >>> identify or distinguish data of different cgroups. It uses the unique >>> inode number

[PATCH 3.12 12/38] USB: serial: ftdi_sio: add support for TI CC3200 LaunchPad

From: Doug Brown 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9bfef729a3d11f04d12788d749a3ce6b47645734 upstream. This patch adds support for the TI CC3200 LaunchPad board, which uses a custom USB vendor ID and product

[PATCH 3.12 14/38] scsi: mpt3sas: Fix secure erase premature termination

From: Andrey Grodzovsky 3.12-stable review patch. If anyone has any objections, please let me know. === commit 18f6084a989ba1b38702f9af37a2e4049a924be6 upstream. This is a work around for a bug with LSI Fusion MPT SAS2 when perfoming secure erase. Due to the

[PATCH 3.12 16/38] cfg80211: limit scan results cache size

From: Johannes Berg 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9853a55ef1bb66d7411136046060bbfb69c714fa upstream. It's possible to make scanning consume almost arbitrary amounts of memory, e.g. by sending beacon

[PATCH 3.12 02/38] PCI: Fix devfn for VPD access through function 0

From: Alex Williamson 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9d9240756e63dd87d6cbf5da8b98ceb8f8192b55 upstream. Commit 932c435caba8 ("PCI: Add dev_flags bit to access VPD through function 0") passes

[PATCH 3.12 12/38] USB: serial: ftdi_sio: add support for TI CC3200 LaunchPad

From: Doug Brown 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9bfef729a3d11f04d12788d749a3ce6b47645734 upstream. This patch adds support for the TI CC3200 LaunchPad board, which uses a custom USB vendor ID and product ID. Channel A is

[PATCH 3.12 14/38] scsi: mpt3sas: Fix secure erase premature termination

From: Andrey Grodzovsky 3.12-stable review patch. If anyone has any objections, please let me know. === commit 18f6084a989ba1b38702f9af37a2e4049a924be6 upstream. This is a work around for a bug with LSI Fusion MPT SAS2 when perfoming secure erase. Due to the very long time the

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