Re: Linux 4.14.39

diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index 0f9089416b4c..88ad78c6f605 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt @@ -1940,6 +1940,9 @@ ARM 32-bit VFP control registers have the following id bit patterns:

Re: Linux 4.14.39

diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt index 0f9089416b4c..88ad78c6f605 100644 --- a/Documentation/virtual/kvm/api.txt +++ b/Documentation/virtual/kvm/api.txt @@ -1940,6 +1940,9 @@ ARM 32-bit VFP control registers have the following id bit patterns:

Linux 4.14.39

I'm announcing the release of the 4.14.39 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web

Linux 4.14.39

I'm announcing the release of the 4.14.39 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web

[RFC] perf record: dead code perf_event__synthesize_id_index()

Hi, It looks like perf_event__synthesize_id_index() is dead code in the current tip tree. I don't see any invocation of the function anywhere in perf.I understand why you'd want to keep the rest of the code related to PERF_RECORD_ID_INDEX because some perf.data file may have this user-level

[RFC] perf record: dead code perf_event__synthesize_id_index()

Hi, It looks like perf_event__synthesize_id_index() is dead code in the current tip tree. I don't see any invocation of the function anywhere in perf.I understand why you'd want to keep the rest of the code related to PERF_RECORD_ID_INDEX because some perf.data file may have this user-level

Re: [PATCH v2 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Fri, Apr 13, 2018 at 7:50 PM, David Collins wrote: > +- vdd_l26-supply > +- vdd_lvs1_lvs2-supply > +- vdd_lvs1_lvs2-supply > + Usage: optional (PM8998 only) > + Value type: > + Definition: phandle of the parent supply regulator of one or

Re: [PATCH v2 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Fri, Apr 13, 2018 at 7:50 PM, David Collins wrote: > +- vdd_l26-supply > +- vdd_lvs1_lvs2-supply > +- vdd_lvs1_lvs2-supply > + Usage: optional (PM8998 only) > + Value type: > + Definition: phandle of the parent supply regulator of one or more of > the > +

[PATCH v2] mfd: qcom-spmi-pmic: Add support for pm8005,pm8998,pmi8998

Add the compatibles and PMIC ids for the pm8005, pm8998, and pmi8998 PMICS found on MSM8998 and SDM845 based platforms. Cc: Reviewed-by: Rob Herring Reviewed-by: Doug Anderson Signed-off-by: Stephen Boyd

[PATCH v2] mfd: qcom-spmi-pmic: Add support for pm8005,pm8998,pmi8998

Add the compatibles and PMIC ids for the pm8005, pm8998, and pmi8998 PMICS found on MSM8998 and SDM845 based platforms. Cc: Reviewed-by: Rob Herring Reviewed-by: Doug Anderson Signed-off-by: Stephen Boyd --- Changes from v1: * Picked up review tags * Reordered lists to be based on id

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for pm8005,pm8998,pmi8998

Quoting Doug Anderson (2018-04-23 22:26:29) > > > static const struct of_device_id pmic_spmi_id_table[] = { > > { .compatible = "qcom,spmi-pmic", .data = (void *)COMMON_SUBTYPE }, > > @@ -54,7 +57,10 @@ static const struct of_device_id pmic_spmi_id_table[] = { > > { .compatible =

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for pm8005,pm8998,pmi8998

Quoting Doug Anderson (2018-04-23 22:26:29) > > > static const struct of_device_id pmic_spmi_id_table[] = { > > { .compatible = "qcom,spmi-pmic", .data = (void *)COMMON_SUBTYPE }, > > @@ -54,7 +57,10 @@ static const struct of_device_id pmic_spmi_id_table[] = { > > { .compatible =

Re: Linux messages full of `random: get_random_u32 called from`

On Wed, May 02, 2018 at 07:09:11AM -0500, Justin Forbes wrote: > Yes, Fedora libgcrypt is carrying a patch which makes it particularly > painful for us, we have reached out to the libgcrypt maintainer to > follow up on that end. But as I said before, even without that code > path (no dracut-fips)

Re: Linux messages full of `random: get_random_u32 called from`

On Wed, May 02, 2018 at 07:09:11AM -0500, Justin Forbes wrote: > Yes, Fedora libgcrypt is carrying a patch which makes it particularly > painful for us, we have reached out to the libgcrypt maintainer to > follow up on that end. But as I said before, even without that code > path (no dracut-fips)

Re: [PATCH v1 0/2] Add ltdc & dsi support on stm32mp157c

hi On 04/24/2018 09:54 AM, yannick fertre wrote: This patch-set adds display controller & DSI controller support to stm32mp157c SOC. Version 1: - Initial commit yannick fertre (2): ARM: dts: stm32: add ltdc support on stm32mp157c ARM: dts: stm32: add dsi support on stm32mp157c

Re: [PATCH v1 0/2] Add ltdc & dsi support on stm32mp157c

hi On 04/24/2018 09:54 AM, yannick fertre wrote: This patch-set adds display controller & DSI controller support to stm32mp157c SOC. Version 1: - Initial commit yannick fertre (2): ARM: dts: stm32: add ltdc support on stm32mp157c ARM: dts: stm32: add dsi support on stm32mp157c

Re: [PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

On Wednesday, May 02, 2018 05:49:31 PM Daniel Lezcano wrote: > On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote: > > Entry for Index 941 has one zero too much. Fix it. > > > > Signed-off-by: Bartlomiej Zolnierkiewicz > > Good catch :) Thanks.

Re: [PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

On Wednesday, May 02, 2018 05:49:31 PM Daniel Lezcano wrote: > On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote: > > Entry for Index 941 has one zero too much. Fix it. > > > > Signed-off-by: Bartlomiej Zolnierkiewicz > > Good catch :) Thanks. :) > I'm curious, how did

[PATCH] modified: arch/x86/mm/pageattr.c

fix mistypo cehck -> check Signed-off-by: DongJoo Seo --- arch/x86/mm/pageattr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c index 3bded76e..3b4cf12 100644 --- a/arch/x86/mm/pageattr.c +++

[PATCH] modified: arch/x86/mm/pageattr.c

fix mistypo cehck -> check Signed-off-by: DongJoo Seo --- arch/x86/mm/pageattr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c index 3bded76e..3b4cf12 100644 --- a/arch/x86/mm/pageattr.c +++ b/arch/x86/mm/pageattr.c @@

Re: [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter()

On Tue, May 1, 2018 at 8:34 PM Linus Torvalds wrote: > On Tue, May 1, 2018 at 8:22 PM Dan Williams > wrote: > > All that to say that having a typical RAM page covering poisoned pmem > > would complicate the 'clear badblocks'

Re: [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter()

On Tue, May 1, 2018 at 8:34 PM Linus Torvalds wrote: > On Tue, May 1, 2018 at 8:22 PM Dan Williams > wrote: > > All that to say that having a typical RAM page covering poisoned pmem > > would complicate the 'clear badblocks' implementation. > Ugh, ok. > I guess the good news is that your

Re: [PATCH] swiotlb: Fix inversed DMA_ATTR_NO_WARN test

On Wed, May 02, 2018 at 04:31:09PM +0200, Michel Dänzer wrote: > > No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface > > for dma allocations and just cause problems. I actually plan to > > get rid of the gfp_t argument in dma_alloc_attrs sooner, and only > > allow either

Re: [PATCH] swiotlb: Fix inversed DMA_ATTR_NO_WARN test

On Wed, May 02, 2018 at 04:31:09PM +0200, Michel Dänzer wrote: > > No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface > > for dma allocations and just cause problems. I actually plan to > > get rid of the gfp_t argument in dma_alloc_attrs sooner, and only > > allow either

Re: [PATCH v2 0/5] Add STM32F7 I2C Support on STM32MP157C

Hi, On 04/23/2018 11:48 AM, Pierre-Yves MORDRET wrote: This patch adds STM32MP157C I2C support on STM32MP157C with configs and device tree. In the same way I2C4 is enabled for STM32MP157C ED1 Daughter bord. I2C2/5 is enabled on STM32MP157C EV1 Daughter board on Evaluation board. --- Version

Re: [PATCH v2 0/5] Add STM32F7 I2C Support on STM32MP157C

Hi, On 04/23/2018 11:48 AM, Pierre-Yves MORDRET wrote: This patch adds STM32MP157C I2C support on STM32MP157C with configs and device tree. In the same way I2C4 is enabled for STM32MP157C ED1 Daughter bord. I2C2/5 is enabled on STM32MP157C EV1 Daughter board on Evaluation board. --- Version

Re: [PATCH 1/5] random: fix crng_ready() test

Hi Ted, On Fri, Apr 13, 2018 at 3:30 AM, Theodore Ts'o wrote: > The crng_init variable has three states: > > 0: The CRNG is not initialized at all > 1: The CRNG has a small amount of entropy, hopefully good enough for >early-boot, non-cryptographical use cases > 2: The CRNG is

Re: [PATCH 1/5] random: fix crng_ready() test

Hi Ted, On Fri, Apr 13, 2018 at 3:30 AM, Theodore Ts'o wrote: > The crng_init variable has three states: > > 0: The CRNG is not initialized at all > 1: The CRNG has a small amount of entropy, hopefully good enough for >early-boot, non-cryptographical use cases > 2: The CRNG is fully

Re: [PATCH] kbuild: replace hardcoded bison in cmd_bison_h with $(YACC)

2018-04-24 20:07 GMT+09:00 Masahiro Yamada : > Commit 73a4f6dbe70a ("kbuild: add LEX and YACC variables") missed to > update cmd_bison_h somehow. > > Signed-off-by: Masahiro Yamada > --- Applied to linux-kbuild/fixes. >

Re: [PATCH] kbuild: replace hardcoded bison in cmd_bison_h with $(YACC)

2018-04-24 20:07 GMT+09:00 Masahiro Yamada : > Commit 73a4f6dbe70a ("kbuild: add LEX and YACC variables") missed to > update cmd_bison_h somehow. > > Signed-off-by: Masahiro Yamada > --- Applied to linux-kbuild/fixes. > scripts/Makefile.lib | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH] genksyms: fix typo in parse.tab.{c,h} generation rules

2018-04-24 20:08 GMT+09:00 Masahiro Yamada : > From: Mauro Rossi > > 'quet' is replaced by 'quiet' in scripts/genksyms/Makefile > > Signed-off-by: Mauro Rossi > Signed-off-by: Masahiro Yamada

Re: [PATCH] genksyms: fix typo in parse.tab.{c,h} generation rules

2018-04-24 20:08 GMT+09:00 Masahiro Yamada : > From: Mauro Rossi > > 'quet' is replaced by 'quiet' in scripts/genksyms/Makefile > > Signed-off-by: Mauro Rossi > Signed-off-by: Masahiro Yamada > --- Applied to linux-kbuild/fixes. > scripts/genksyms/Makefile | 4 ++-- > 1 file changed, 2

Re: [PATCH] kbuild/debian: Use KBUILD_BUILD_* when set

2018-05-02 20:30 GMT+09:00 Riku Voipio : > On 23 April 2018 at 22:50, Mathieu Malaterre wrote: >> Be nice to the user and check env vars KBUILD_BUILD_USER & >> KBUILD_BUILD_HOST when those are set. > > mkdebian sets the maintainer address as "$name

Re: [PATCH] kbuild/debian: Use KBUILD_BUILD_* when set

2018-05-02 20:30 GMT+09:00 Riku Voipio : > On 23 April 2018 at 22:50, Mathieu Malaterre wrote: >> Be nice to the user and check env vars KBUILD_BUILD_USER & >> KBUILD_BUILD_HOST when those are set. > > mkdebian sets the maintainer address as "$name <$email>", but this > patch only sets the email

Re: [PATCH v2 4/5] dt-bindings: devfreq: rk3399_dmc: remove interrupts as is not required.

Hi Rob, Thanks for the review. On 27/04/18 22:00, Rob Herring wrote: > On Tue, Apr 24, 2018 at 10:37:41AM +0200, Enric Balletbo i Serra wrote: >> In ATF we already wait for DDR dvfs finish, so don't need to do this in >> kernel, so remove the interrupts properties as is not longer required. > >

Re: [PATCH v2 4/5] dt-bindings: devfreq: rk3399_dmc: remove interrupts as is not required.

Hi Rob, Thanks for the review. On 27/04/18 22:00, Rob Herring wrote: > On Tue, Apr 24, 2018 at 10:37:41AM +0200, Enric Balletbo i Serra wrote: >> In ATF we already wait for DDR dvfs finish, so don't need to do this in >> kernel, so remove the interrupts properties as is not longer required. > >

[PATCH] x86/mm: Introduce 'no5vl kernel parameter

The kernel parameter allows to force kernel to use 4-level paging even if hardware and kernel support 5-level paging. The option may be useful to workaround regressions related to 5-level paging. Signed-off-by: Kirill A. Shutemov ---

[PATCH] x86/mm: Introduce 'no5vl kernel parameter

The kernel parameter allows to force kernel to use 4-level paging even if hardware and kernel support 5-level paging. The option may be useful to workaround regressions related to 5-level paging. Signed-off-by: Kirill A. Shutemov --- Documentation/admin-guide/kernel-parameters.txt | 3 +++

Re: [PATCH 0/6 resend] statfs: handle mount propagation

On Wed, May 02, 2018 at 05:42:33PM +0200, Christian Brauner wrote: > Hey, > > This is the second resend of this patchset. I'm not sure whether it has > simply been overlooked but the number of people get_maintainer.pl was > rather small and seemed a little random so I added Linus and Christoph, >

Re: [PATCH 0/6 resend] statfs: handle mount propagation

On Wed, May 02, 2018 at 05:42:33PM +0200, Christian Brauner wrote: > Hey, > > This is the second resend of this patchset. I'm not sure whether it has > simply been overlooked but the number of people get_maintainer.pl was > rather small and seemed a little random so I added Linus and Christoph, >

[PATCH] x86/boot/compressed: Exclude 'top_pgtable' from relocation

startup_64() copies kernel (including .data section) to the new place. It's required for safe in-place decompression. This is a problem if the original place is referenced: by mistake I've put 'top_pgtable' into .data section and the address is loaded into CR3. If the original place gets

[PATCH] x86/boot/compressed: Exclude 'top_pgtable' from relocation

startup_64() copies kernel (including .data section) to the new place. It's required for safe in-place decompression. This is a problem if the original place is referenced: by mistake I've put 'top_pgtable' into .data section and the address is loaded into CR3. If the original place gets

Re: [RFC PATCH for 4.18 00/14] Restartable Sequences

On Wed, May 2, 2018 at 9:03 AM Mathieu Desnoyers < mathieu.desnoy...@efficios.com> wrote: > - On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com wrote: > [...] > > > > I think a small enhancement to rseq would let us build a perfect userspace > > mutex, one that spins on

Re: [RFC PATCH for 4.18 00/14] Restartable Sequences

On Wed, May 2, 2018 at 9:03 AM Mathieu Desnoyers < mathieu.desnoy...@efficios.com> wrote: > - On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com wrote: > [...] > > > > I think a small enhancement to rseq would let us build a perfect userspace > > mutex, one that spins on

New patchwork instance for linux-mm

I went ahead and requested a patchwork instance on patchwork.kernel.org and it's up and running https://patchwork.kernel.org/project/linux-mm/list/ Hopefully someone else will find this useful. It's a nice way to view Acks/Tested-by for those who pay attention to such things. Thanks, Laura P.S.

New patchwork instance for linux-mm

I went ahead and requested a patchwork instance on patchwork.kernel.org and it's up and running https://patchwork.kernel.org/project/linux-mm/list/ Hopefully someone else will find this useful. It's a nice way to view Acks/Tested-by for those who pay attention to such things. Thanks, Laura P.S.

Re: [PATCH 07/11] irqchip: stm32: add stm32mp1 support with hierarchy domain

Hi Rob On 05/01/2018 04:56 PM, Rob Herring wrote: On Thu, Apr 26, 2018 at 06:18:30PM +0200, Ludovic Barre wrote: From: Ludovic Barre Exti controller has been differently integrated on stm32mp1 SoC. A parent irq has only one external interrupt. A hierachy domain could

Re: [PATCH 07/11] irqchip: stm32: add stm32mp1 support with hierarchy domain

Hi Rob On 05/01/2018 04:56 PM, Rob Herring wrote: On Thu, Apr 26, 2018 at 06:18:30PM +0200, Ludovic Barre wrote: From: Ludovic Barre Exti controller has been differently integrated on stm32mp1 SoC. A parent irq has only one external interrupt. A hierachy domain could be used. Handlers are

Re: [RFC PATCH for 4.18 00/14] Restartable Sequences

- On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com wrote: [...] > > I think a small enhancement to rseq would let us build a perfect userspace > mutex, one that spins on lock-acquire only when the lock owner is running > and that sleeps otherwise, freeing userspace from both

Re: [RFC PATCH for 4.18 00/14] Restartable Sequences

- On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com wrote: [...] > > I think a small enhancement to rseq would let us build a perfect userspace > mutex, one that spins on lock-acquire only when the lock owner is running > and that sleeps otherwise, freeing userspace from both

[PATCH 05/11] scsi: hisi_sas: check sas_dev gone earlier in hisi_sas_abort_task()

From: Xiang Chen It is possible to dereference a NULL-pointer in hisi_sas_abort_task() in special scenario when the device has been removed. If an SMP task times-out, it will call hisi_sas_abort_task() to recover. And currently there is a check in

[PATCH 05/11] scsi: hisi_sas: check sas_dev gone earlier in hisi_sas_abort_task()

From: Xiang Chen It is possible to dereference a NULL-pointer in hisi_sas_abort_task() in special scenario when the device has been removed. If an SMP task times-out, it will call hisi_sas_abort_task() to recover. And currently there is a check in hisi_sas_abort_task() to avoid the situation of

[PATCH 06/11] scsi: hisi_sas: stop controller timer for reset

We should only have the timer enabled after PHY up after controller reset, so disable prior to reset. Signed-off-by: John Garry Signed-off-by: Xiaofei Tan --- drivers/scsi/hisi_sas/hisi_sas_main.c | 3 +++ 1 file changed, 3 insertions(+) diff

[PATCH 06/11] scsi: hisi_sas: stop controller timer for reset

We should only have the timer enabled after PHY up after controller reset, so disable prior to reset. Signed-off-by: John Garry Signed-off-by: Xiaofei Tan --- drivers/scsi/hisi_sas/hisi_sas_main.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/scsi/hisi_sas/hisi_sas_main.c

[PATCH 00/11] hisi_sas: some misc patches

This patchset introduces some misc changes for the driver. These include: - fixes for potential problems related to SCSI EH and device removal races - fix protection info size for all hw versions - some SoC bug workarounds - minor optimisations - other more minor things John Garry (2): scsi:

[PATCH 00/11] hisi_sas: some misc patches

This patchset introduces some misc changes for the driver. These include: - fixes for potential problems related to SCSI EH and device removal races - fix protection info size for all hw versions - some SoC bug workarounds - minor optimisations - other more minor things John Garry (2): scsi:

[PATCH 04/11] scsi: hisi_sas: fix PI memory size

From: Xiang Chen There are 28 bytes of protection information record of SSP for v3 hw, 16 bytes for v2 hw, and probably 24 for v1 hw (forgotten now). So use a value big enough in hisi_sas_command_table_ssp.prot to cover all cases. Signed-off-by: Xiang Chen

[PATCH 04/11] scsi: hisi_sas: fix PI memory size

From: Xiang Chen There are 28 bytes of protection information record of SSP for v3 hw, 16 bytes for v2 hw, and probably 24 for v1 hw (forgotten now). So use a value big enough in hisi_sas_command_table_ssp.prot to cover all cases. Signed-off-by: Xiang Chen Signed-off-by: John Garry ---

[PATCH 03/11] scsi: hisi_sas: check host frozen before calling "done" function

From: Xiang Chen When the host is frozen in SCSI EH state, at any point after the LLDD sets SAS_TASK_STATE_DONE for the sas_task task state, libsas may free the task; see sas_scsi_find_task(). This puts the LLDD in a difficult position, in that once it sets

[PATCH 03/11] scsi: hisi_sas: check host frozen before calling "done" function

From: Xiang Chen When the host is frozen in SCSI EH state, at any point after the LLDD sets SAS_TASK_STATE_DONE for the sas_task task state, libsas may free the task; see sas_scsi_find_task(). This puts the LLDD in a difficult position, in that once it sets SAS_TASK_STATE_DONE for the task

Re: [PATCH 2/3] seccomp: Audit attempts to modify the actions_logged sysctl

On 05/01/2018 12:25 PM, Paul Moore wrote: > On Tue, May 1, 2018 at 12:41 PM, Steve Grubb wrote: >> On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote: >>> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote: The decision to log a seccomp action

Re: [PATCH 2/3] seccomp: Audit attempts to modify the actions_logged sysctl

On 05/01/2018 12:25 PM, Paul Moore wrote: > On Tue, May 1, 2018 at 12:41 PM, Steve Grubb wrote: >> On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote: >>> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote: The decision to log a seccomp action will always be subject to the value

[PATCH 08/11] scsi: hisi_sas: config ATA de-reset as an constrained command for v3 hw

From: Xiang Chen As a unconstrained command, a command can be sent to SATA disk even if SATA disk status is BUSY, ERR or DRQ. If an ATA reset assert is successful but ATA reset de-assert fails, then it will retry the reset de-assert. If reset de- assert retry is

[PATCH 08/11] scsi: hisi_sas: config ATA de-reset as an constrained command for v3 hw

From: Xiang Chen As a unconstrained command, a command can be sent to SATA disk even if SATA disk status is BUSY, ERR or DRQ. If an ATA reset assert is successful but ATA reset de-assert fails, then it will retry the reset de-assert. If reset de- assert retry is successful, we think it is okay

[PATCH 07/11] scsi: hisi_sas: update PHY linkrate after a controller reset

From: Xiang Chen After the controller is reset, we currently may not honour the PHY max linkrate set via sysfs, in that after a reset we always revert to max linkrate of 12Gbps, ignoring the value set via sysfs. This patch modifies to policy to set the programmed PHY

[PATCH 07/11] scsi: hisi_sas: update PHY linkrate after a controller reset

From: Xiang Chen After the controller is reset, we currently may not honour the PHY max linkrate set via sysfs, in that after a reset we always revert to max linkrate of 12Gbps, ignoring the value set via sysfs. This patch modifies to policy to set the programmed PHY linkrate, honouring the max

[PATCH 11/11] scsi: hisi_sas: workaround a v3 hw hilink bug

From: Xiaofei Tan There is an SoC bug of v3 hw development version. When hot- unplugging a directly attached disk, the PHY down interrupt may not happen. It is very easy to appear on some boards. When this issue occurs, the controller will receive many invalid dword

[PATCH 11/11] scsi: hisi_sas: workaround a v3 hw hilink bug

From: Xiaofei Tan There is an SoC bug of v3 hw development version. When hot- unplugging a directly attached disk, the PHY down interrupt may not happen. It is very easy to appear on some boards. When this issue occurs, the controller will receive many invalid dword frames, and the "alos"

[PATCH 09/11] scsi: hisi_sas: remove redundant handling to event95 for v3

From: Xiaofei Tan Event95 is used for DFX purpose. The relevant bit for this interrupt in the ENT_INT_SRC_MSK3 register has been disabled, so remove the processing. Signed-off-by: Xiaofei Tan Signed-off-by: John Garry ---

[PATCH 09/11] scsi: hisi_sas: remove redundant handling to event95 for v3

From: Xiaofei Tan Event95 is used for DFX purpose. The relevant bit for this interrupt in the ENT_INT_SRC_MSK3 register has been disabled, so remove the processing. Signed-off-by: Xiaofei Tan Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 9 + 1 file changed,

[PATCH 02/11] scsi: hisi_sas: Add some checks to avoid free'ing a sas_task twice

From: Xiang Chen If the SCSI host enters EH, any pending IO will be processed by SCSI EH. However it is possible that SCSI EH will try to abort the IO and also at the same time the IO completes in the driver. In this situation there is a small changes of freeing the

[PATCH 02/11] scsi: hisi_sas: Add some checks to avoid free'ing a sas_task twice

From: Xiang Chen If the SCSI host enters EH, any pending IO will be processed by SCSI EH. However it is possible that SCSI EH will try to abort the IO and also at the same time the IO completes in the driver. In this situation there is a small changes of freeing the sas_task twice. Then if

[PATCH 10/11] scsi: hisi_sas: add readl poll timeout helper wrappers

It is common to use readl poll timeout helpers in the driver, so create custom wrappers. Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 28 ++-- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git

[PATCH 10/11] scsi: hisi_sas: add readl poll timeout helper wrappers

It is common to use readl poll timeout helpers in the driver, so create custom wrappers. Signed-off-by: John Garry --- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 28 ++-- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c

[PATCH 01/11] scsi: hisi_sas: optimise the usage of DQ locking

From: Xiang Chen In the DQ tasklet processing it is not necessary to take the DQ lock, as there is no contention between adding slots to the CQ and removing slots from the matching DQ. In addition, since we run each DQ in a separate tasklet context, there would be no

[PATCH 01/11] scsi: hisi_sas: optimise the usage of DQ locking

From: Xiang Chen In the DQ tasklet processing it is not necessary to take the DQ lock, as there is no contention between adding slots to the CQ and removing slots from the matching DQ. In addition, since we run each DQ in a separate tasklet context, there would be no possible contention between

Re: [PATCH v4 00/14] Copy Offload in NVMe Fabrics with P2P PCI Memory

Hi Christian, On 5/2/2018 5:51 AM, Christian König wrote: it would be rather nice to have if you could separate out the functions to detect if peer2peer is possible between two devices. This would essentially be pci_p2pdma_distance() in the existing patchset. It returns the sum of the

Re: [PATCH v4 00/14] Copy Offload in NVMe Fabrics with P2P PCI Memory

Hi Christian, On 5/2/2018 5:51 AM, Christian König wrote: it would be rather nice to have if you could separate out the functions to detect if peer2peer is possible between two devices. This would essentially be pci_p2pdma_distance() in the existing patchset. It returns the sum of the

Linux 4.16.7

I'm announcing the release of the 4.16.7 kernel. All users of the 4.16 kernel series must upgrade. The updated 4.16.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.16.y and can be browsed at the normal kernel.org git web browser:

Linux 4.16.7

I'm announcing the release of the 4.16.7 kernel. All users of the 4.16 kernel series must upgrade. The updated 4.16.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.16.y and can be browsed at the normal kernel.org git web browser:

[PATCH v2 3/4] seccomp: Audit attempts to modify the actions_logged sysctl

The decision to log a seccomp action will always be subject to the value of the kernel.seccomp.actions_logged sysctl, even for processes that are being inspected via the audit subsystem, in an upcoming patch. Therefore, we need to emit an audit record on attempts at writing to the actions_logged

[PATCH v2 3/4] seccomp: Audit attempts to modify the actions_logged sysctl

The decision to log a seccomp action will always be subject to the value of the kernel.seccomp.actions_logged sysctl, even for processes that are being inspected via the audit subsystem, in an upcoming patch. Therefore, we need to emit an audit record on attempts at writing to the actions_logged

[PATCH v2 4/4] seccomp: Don't special case audited processes when logging

Seccomp logging for "handled" actions such as RET_TRAP, RET_TRACE, or RET_ERRNO can be very noisy for processes that are being audited. This patch modifies the seccomp logging behavior to treat processes that are being inspected via the audit subsystem the same as processes that aren't under

[PATCH v2 4/4] seccomp: Don't special case audited processes when logging

Seccomp logging for "handled" actions such as RET_TRAP, RET_TRACE, or RET_ERRNO can be very noisy for processes that are being audited. This patch modifies the seccomp logging behavior to treat processes that are being inspected via the audit subsystem the same as processes that aren't under

[PATCH v2 2/4] seccomp: Configurable separator for the actions_logged string

The function that converts a bitmask of seccomp actions that are allowed to be logged is currently only used for constructing the display string for the kernel.seccomp.actions_logged sysctl. That string wants a space character to be used for the separator between actions. A future patch will make

[PATCH v2 2/4] seccomp: Configurable separator for the actions_logged string

The function that converts a bitmask of seccomp actions that are allowed to be logged is currently only used for constructing the display string for the kernel.seccomp.actions_logged sysctl. That string wants a space character to be used for the separator between actions. A future patch will make

[PATCH v2 1/4] seccomp: Separate read and write code for actions_logged sysctl

Break the read and write paths of the kernel.seccomp.actions_logged sysctl into separate functions to maintain readability. An upcoming change will need to audit writes, but not reads, of this sysctl which would introduce too many conditional code paths on whether or not the 'write' parameter

[PATCH v2 1/4] seccomp: Separate read and write code for actions_logged sysctl

Break the read and write paths of the kernel.seccomp.actions_logged sysctl into separate functions to maintain readability. An upcoming change will need to audit writes, but not reads, of this sysctl which would introduce too many conditional code paths on whether or not the 'write' parameter

[PATCH v2 0/4] Better integrate seccomp logging and auditing

Seccomp received improved logging controls in v4.14. Applications can opt into logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters. They can also debug filter matching with the new SECCOMP_RET_LOG action.

[PATCH v2 0/4] Better integrate seccomp logging and auditing

Seccomp received improved logging controls in v4.14. Applications can opt into logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters. They can also debug filter matching with the new SECCOMP_RET_LOG action.

Re: [RFC resend 1/2] modpost: delete stale comment

2018-03-23 6:05 GMT+09:00 Rasmus Villemoes : > Commit (7840fea200cd "kbuild: Fix computing srcversion for modules") > fixed the comment above parse_source_files to refer to the new source_ > line, but left this one behind that could still give the impression that >

Re: [RFC resend 1/2] modpost: delete stale comment

2018-03-23 6:05 GMT+09:00 Rasmus Villemoes : > Commit (7840fea200cd "kbuild: Fix computing srcversion for modules") > fixed the comment above parse_source_files to refer to the new source_ > line, but left this one behind that could still give the impression that > drivers/net/dummy.c appears in

Re: [PATCH 0/4] ARM: dts: Add cryptographic support for stm32mp157c

Hi Lionel, On 04/23/2018 05:19 PM, Lionel Debieve wrote: Patches serie add support or RNG, CRYP and CRC IPs for stm32mp157c SoC and add RNG default support for ev1 board. Lionel Debieve (4): ARM: dts: stm32: Add RNG support on stm32mp157c ARM: dts: stm32: Enable RNG for stm32mp157c-ed1

Re: [PATCH 0/4] ARM: dts: Add cryptographic support for stm32mp157c

Hi Lionel, On 04/23/2018 05:19 PM, Lionel Debieve wrote: Patches serie add support or RNG, CRYP and CRC IPs for stm32mp157c SoC and add RNG default support for ev1 board. Lionel Debieve (4): ARM: dts: stm32: Add RNG support on stm32mp157c ARM: dts: stm32: Enable RNG for stm32mp157c-ed1

Re: [PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote: > Entry for Index 941 has one zero too much. Fix it. > > Signed-off-by: Bartlomiej Zolnierkiewicz Good catch :) I'm curious, how did you spot it ? > --- > v2: > - Fix patch description. > >

Re: [PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote: > Entry for Index 941 has one zero too much. Fix it. > > Signed-off-by: Bartlomiej Zolnierkiewicz Good catch :) I'm curious, how did you spot it ? > --- > v2: > - Fix patch description. > >

[PATCH v2 RESEND 1/2] mm: introduce memory.min

Memory controller implements the memory.low best-effort memory protection mechanism, which works perfectly in many cases and allows protecting working sets of important workloads from sudden reclaim. But its semantics has a significant limitation: it works only as long as there is a supply of

[PATCH v2 RESEND 1/2] mm: introduce memory.min

Memory controller implements the memory.low best-effort memory protection mechanism, which works perfectly in many cases and allows protecting working sets of important workloads from sudden reclaim. But its semantics has a significant limitation: it works only as long as there is a supply of

[PATCH v2 RESEND 2/2] mm: ignore memory.min of abandoned memory cgroups

If a cgroup has no associated tasks, invoking the OOM killer won't help release any memory, so respecting the memory.min can lead to an infinite OOM loop or system stall. Let's ignore memory.min of unpopulated cgroups. Signed-off-by: Roman Gushchin Cc: Johannes Weiner

[PATCH v2 RESEND 2/2] mm: ignore memory.min of abandoned memory cgroups

If a cgroup has no associated tasks, invoking the OOM killer won't help release any memory, so respecting the memory.min can lead to an infinite OOM loop or system stall. Let's ignore memory.min of unpopulated cgroups. Signed-off-by: Roman Gushchin Cc: Johannes Weiner Cc: Michal Hocko Cc:

<    4   5   6   7   8   9   10   11   12   13   >