[REGRESSION][v6.8-rc1] virtio-pci: Introduce admin virtqueue

Hi Feng, During testing, a kernel bug was identified with the suspend/resume functionality on instances running in a public cloud [0].  This bug is a regression introduced in v6.8-rc1.  After a kernel bisect, the following commit was identified as the cause of the regression:   

[PATCH 2/2] drivers: hv: Create a consistent pattern for checking Hyper-V hypercall status

From: Joseph Salisbury There is not a consistent pattern for checking Hyper-V hypercall status. Existing code uses a number of variants. The variants work, but a consistent pattern would improve the readability of the code, and be more conformant to what the Hyper-V TLFS says about hypercall

[PATCH 1/2] x86/hyperv: Move hv_do_rep_hypercall to asm-generic

From: Joseph Salisbury This patch makes no functional changes. It simply moves hv_do_rep_hypercall() out of arch/x86/include/asm/mshyperv.h and into asm-generic/mshyperv.h hv_do_rep_hypercall() is architecture independent, so it makes sense that it should be in the architecture independent

[tip: x86/hyperv] x86/hyperv: Remove aliases with X64 in their name

The following commit has been merged into the x86/hyperv branch of tip: Commit-ID: dfc53baae3c6a165a35735b789e3e083786271d6 Gitweb: https://git.kernel.org/tip/dfc53baae3c6a165a35735b789e3e083786271d6 Author:Joseph Salisbury AuthorDate:Sat, 26 Sep 2020 07:26:26 -07:00

[PATCH] x86/hyperv: Remove aliases with X64 in their name

From: Joseph Salisbury In the architecture independent version of hyperv-tlfs.h, commit c55a844f46f958b removed the "X64" in the symbol names so they would make sense for both x86 and ARM64. That commit added aliases with the "X64" in the x86 version of hyperv-tlfs.h so th

[PATCH][v2] Drivers: hv: Change flag to write log level in panic msg to false

() to not include the log level, enabling more information that *is* useful to fit in the page. Requesting in stable kernels, since many kernels running in production are stable releases. Cc: sta...@vger.kernel.org Signed-off-by: Joseph Salisbury --- drivers/hv/vmbus_drv.c | 2 +- 1 file changed

RE: [PATCH] Drivers: hv: Change flag to write log level in panic msg to false

-Original Message- From: Michael Kelley Sent: Friday, June 26, 2020 6:24 PM To: Joseph Salisbury ; KY Srinivasan ; Haiyang Zhang ; Stephen Hemminger ; sas...@kernel.org; wei@kernel.org Cc: linux-hyp...@vger.kernel.org; linux-kernel@vger.kernel.org; sta...@vger.kernel.org Subject

RE: [PATCH] Drivers: hv: Change flag to write log level in panic msg to false

Thanks for the feedback, Michael. I'll send a v2. Thanks, Joe -Original Message- From: Michael Kelley Sent: Friday, June 26, 2020 4:53 PM To: Joseph Salisbury ; KY Srinivasan ; Haiyang Zhang ; Stephen Hemminger ; sas...@kernel.org; wei@kernel.org Cc: linux-hyp

[PATCH] Drivers: hv: Change flag to write log level in panic msg to false

unning in production are stable releases. Cc: sta...@vger.kernel.org Signed-off-by: Joseph Salisbury --- drivers/hv/vmbus_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c index 9147ee9d5f7d..d69f4efa3719 100644 --- a/driv

RE: [PATCH] drivers: hid: Add a module description line

Thanks for the feedback. I'll probably update each patch subject with the module names as well. I'll send a v2 for all three. Thanks, Joe -Original Message- From: Michael Kelley Sent: Monday, April 22, 2019 11:16 PM To: Joseph Salisbury ; KY Srinivasan ; Haiyang Zhang ; Stephen

[PATCH] drivers: hv: Add a module description line

Signed-off-by: Joseph Salisbury --- drivers/hv/vmbus_drv.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c index aa25f3bcbdea..1cb9408b0d40 100644 --- a/drivers/hv/vmbus_drv.c +++ b/drivers/hv/vmbus_drv.c @@ -2174,6 +2174,7 @@ static void

[PATCH] drivers: input: serio: Add a module desription

Signed-off-by: Joseph Salisbury --- drivers/input/serio/hyperv-keyboard.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/input/serio/hyperv-keyboard.c b/drivers/input/serio/hyperv-keyboard.c index a8b9be3e28db..7935e52b5435 100644 --- a/drivers/input/serio/hyperv-keyboard.c +++ b

[PATCH] drivers: hid: Add a module description line

Signed-off-by: Joseph Salisbury --- drivers/hid/hid-hyperv.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c index 704049e62d58..d3311d714d35 100644 --- a/drivers/hid/hid-hyperv.c +++ b/drivers/hid/hid-hyperv.c @@ -614,5 +614,7 @@ static

[Regression] libata: sata_down_spd_limit should return if driver has not recorded sstatus speed

Hi David, A kernel bug report was opened against Ubuntu [0].  This bug is a regression introduced in v4.15-rc4.  The following commit was identified as the cause of the regression:     2dc0b46b5ea3 ("libata: sata_down_spd_limit should return if driver has not recorded sstatus speed") I was

[Regression] libata: sata_down_spd_limit should return if driver has not recorded sstatus speed

Hi David, A kernel bug report was opened against Ubuntu [0].  This bug is a regression introduced in v4.15-rc4.  The following commit was identified as the cause of the regression:     2dc0b46b5ea3 ("libata: sata_down_spd_limit should return if driver has not recorded sstatus speed") I was

[Regression] usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201

Hi Daniel, A kernel bug report was opened against Ubuntu [0].  It was found the following patch introduced the regression: da9970668948 ("usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201") The bug reporter claims there is a typo in the patch that caused the regression.  I built a test

[Regression] usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201

Hi Daniel, A kernel bug report was opened against Ubuntu [0].  It was found the following patch introduced the regression: da9970668948 ("usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201") The bug reporter claims there is a typo in the patch that caused the regression.  I built a test

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/04/2018 07:14 AM, Rafael J. Wysocki wrote: > On Thursday, May 3, 2018 11:29:18 PM CEST Rafael J. Wysocki wrote: >> On Thu, May 3, 2018 at 9:11 PM, Bjorn Helgaas <helg...@kernel.org> wrote: >>> On Thu, May 03, 2018 at 02:29:02PM -0400, Joseph Salisbury wrote: >

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/04/2018 07:14 AM, Rafael J. Wysocki wrote: > On Thursday, May 3, 2018 11:29:18 PM CEST Rafael J. Wysocki wrote: >> On Thu, May 3, 2018 at 9:11 PM, Bjorn Helgaas wrote: >>> On Thu, May 03, 2018 at 02:29:02PM -0400, Joseph Salisbury wrote: >>>> On 05/02/2018 06:

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote: > On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas <helg...@kernel.org> wrote: >> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote: >>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury >>> <j

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote: > On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote: >> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote: >>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury >>> wrote: >>>> On 04/16

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote: > On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas <helg...@kernel.org> wrote: >> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote: >>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury >>> <j

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote: > On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote: >> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote: >>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury >>> wrote: >>>> On 04/16

[REGRESSION] drm/amd/dc: Add dc display driver (v2)

Hi Harry, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found the following commit introduced the bug: commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c Author: Harry Wentland Date:   Tue Sep 12 15:58:20 2017 -0400     drm/amd/dc: Add

[REGRESSION] drm/amd/dc: Add dc display driver (v2)

Hi Harry, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found the following commit introduced the bug: commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c Author: Harry Wentland Date:   Tue Sep 12 15:58:20 2017 -0400     drm/amd/dc: Add dc display driver (v2)

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote: > On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: >>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury >>> &l

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote: > On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury > wrote: >> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: >>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury >>> wrote: >>>> Hi Rafael, >&g

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote: > On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: >>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury >>> &l

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote: > On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury > wrote: >> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: >>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury >>> wrote: >>>> Hi Rafael, >&g

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: > On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> Hi Rafael, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that

Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote: > On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury > wrote: >> Hi Rafael, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following tw

[Regression] PCI / PM: Simplify device wakeup settings code

Hi Rafael, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following two commits resolved this bug: 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration") 0847684cfc5f("PCI / PM: Simplify device wakeup settings

[Regression] PCI / PM: Simplify device wakeup settings code

Hi Rafael, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following two commits resolved this bug: 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration") 0847684cfc5f("PCI / PM: Simplify device wakeup settings

[PATCH] bcache: decouple emitting a cached_dev CHANGE uevent

rnel.org Signed-off-by: Ryan Harper <ryan.har...@canonical.com> Signed-off-by: Joseph Salisbury <joseph.salisb...@canonical.com> --- drivers/md/bcache/bcache.h | 1 + drivers/md/bcache/super.c | 53 +- 2 files changed, 44 insertions(+), 10 deleti

[PATCH] bcache: decouple emitting a cached_dev CHANGE uevent

r Signed-off-by: Joseph Salisbury --- drivers/md/bcache/bcache.h | 1 + drivers/md/bcache/super.c | 53 +- 2 files changed, 44 insertions(+), 10 deletions(-) diff --git a/drivers/md/bcache/bcache.h b/drivers/md/bcache/bcache.h index 02619ca..8ed7e7a 100644

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/17/2018 05:55 PM, Thomas Gleixner wrote: > On Wed, 17 Jan 2018, Joseph Salisbury wrote: >> On 01/16/2018 01:59 PM, Thomas Gleixner wrote: >> >> Testing of your patch shows that your patch resolves the bug.  Thanks >> for the assistance!  Is this something y

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/17/2018 05:55 PM, Thomas Gleixner wrote: > On Wed, 17 Jan 2018, Joseph Salisbury wrote: >> On 01/16/2018 01:59 PM, Thomas Gleixner wrote: >> >> Testing of your patch shows that your patch resolves the bug.  Thanks >> for the assistance!  Is this something y

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > On Tue, 16 Jan 2018, Yu, Fenghua wrote: >>> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Is this a Haswell specific issue? >> >> I run the following test forever without issue on Broadwell and 4.15.0-rc6 >> with rdt mounted: >> for ((;;))

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > On Tue, 16 Jan 2018, Yu, Fenghua wrote: >>> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Is this a Haswell specific issue? >> >> I run the following test forever without issue on Broadwell and 4.15.0-rc6 >> with rdt mounted: >> for ((;;))

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > On Tue, 16 Jan 2018, Yu, Fenghua wrote: >>> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Is this a Haswell specific issue? >> >> I run the following test forever without issue on Broadwell and 4.15.0-rc6 >> with rdt mounted: >> for ((;;))

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > On Tue, 16 Jan 2018, Yu, Fenghua wrote: >>> From: Thomas Gleixner [mailto:t...@linutronix.de] >> Is this a Haswell specific issue? >> >> I run the following test forever without issue on Broadwell and 4.15.0-rc6 >> with rdt mounted: >> for ((;;))

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

, Fenghua can you please look at that ASAP? >> >> On Sun, 14 Jan 2018, Thomas Gleixner wrote: >> >>> On Fri, 12 Jan 2018, Joseph Salisbury wrote: >>> >>>> Hi Vikas, >>>> >>>> A kernel bug report was opened against Ubuntu [0].  Aft

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

that ASAP? >> >> On Sun, 14 Jan 2018, Thomas Gleixner wrote: >> >>> On Fri, 12 Jan 2018, Joseph Salisbury wrote: >>> >>>> Hi Vikas, >>>> >>>> A kernel bug report was opened against Ubuntu [0].  After a k

[REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

Hi Vikas, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 24247aeeabe99eab13b798c2dec066dd6f07 Author: Vikas Shivappa Date:   Tue Aug 15 18:00:43 2017 -0700

[REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

Hi Vikas, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 24247aeeabe99eab13b798c2dec066dd6f07 Author: Vikas Shivappa Date:   Tue Aug 15 18:00:43 2017 -0700     x86/intel_rdt/cqm: Improve

[REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

Hi Eric, A kernel bug report was opened against Ubuntu [0].  It was found that reverting the following commit resolved this bug: commit b2504a5dbef3305ef41988ad270b0e8ec289331c Author: Eric Dumazet Date:   Tue Jan 31 10:20:32 2017 -0800     net: reduce

[REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

Hi Eric, A kernel bug report was opened against Ubuntu [0].  It was found that reverting the following commit resolved this bug: commit b2504a5dbef3305ef41988ad270b0e8ec289331c Author: Eric Dumazet Date:   Tue Jan 31 10:20:32 2017 -0800     net: reduce skb_warn_bad_offload() noise     The

[REGRESSION][v4.13.y][v4.14.y] scsi: libsas: allow async aborts

Hi Christoph, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following commit resolved this bug: 909657615d9b ("scsi: libsas: allow async aborts")   The regression was introduced as of v4.12-rc1, and it still exists in 4.14

[REGRESSION][v4.13.y][v4.14.y] scsi: libsas: allow async aborts

Hi Christoph, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following commit resolved this bug: 909657615d9b ("scsi: libsas: allow async aborts")   The regression was introduced as of v4.12-rc1, and it still exists in 4.14

[REGRESSION][v4.11-rc7] drm/nouveau: initial support (display-only) for GP107

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit da2ba564a6dcf46df4f828624ff55531ff11d5b0 Author: Ben Skeggs Date: Thu Apr 6 10:35:26 2017 +1000 drm/nouveau:

[REGRESSION][v4.11-rc7] drm/nouveau: initial support (display-only) for GP107

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit da2ba564a6dcf46df4f828624ff55531ff11d5b0 Author: Ben Skeggs Date: Thu Apr 6 10:35:26 2017 +1000 drm/nouveau: initial support

Re: ipsec doesn't route TCP with 4.11 kernel

On 04/27/2017 06:29 PM, Don Bowman wrote: > On 26 April 2017 at 15:06, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> Hi Don, >> >> Can you see if this bug started happening in v4.11-rc3? Since your >> running Ubuntu, a kernel is already availab

Re: ipsec doesn't route TCP with 4.11 kernel

On 04/27/2017 06:29 PM, Don Bowman wrote: > On 26 April 2017 at 15:06, Joseph Salisbury > wrote: >> Hi Don, >> >> Can you see if this bug started happening in v4.11-rc3? Since your >> running Ubuntu, a kernel is already available here: >> http://kernel.ubunt

Re: ipsec doesn't route TCP with 4.11 kernel

Hi Don, Can you see if this bug started happening in v4.11-rc3? Since your running Ubuntu, a kernel is already available here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/ If v4.11-rc2 is good and -rc3 is bad, I can help you bisect between the two. Thanks, Joe On 04/25/2017

Re: ipsec doesn't route TCP with 4.11 kernel

Hi Don, Can you see if this bug started happening in v4.11-rc3? Since your running Ubuntu, a kernel is already available here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/ If v4.11-rc2 is good and -rc3 is bad, I can help you bisect between the two. Thanks, Joe On 04/25/2017

Re: [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

nivasan <k...@microsoft.com> > Reviewed-by: Christoph Hellwig <h...@lst.de> > Signed-off-by: Martin K. Petersen <martin.peter...@oracle.com> > > -Original Message- > From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com] > Sent: Monday, March

Re: [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

with REPORTLUN and that works correctly. > > Patch needs to go in current 4.11, it is safe but not necessary in older > kernels. > > Signed-off-by: Stephen Hemminger > Reviewed-by: K. Y. Srinivasan > Reviewed-by: Christoph Hellwig >

Re: [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

nivasan <k...@microsoft.com> > Reviewed-by: Christoph Hellwig <h...@lst.de> > Signed-off-by: Martin K. Petersen <martin.peter...@oracle.com> > > -Original Message- > From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com] > Sent: Monday, March

Re: [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

with REPORTLUN and that works correctly. > > Patch needs to go in current 4.11, it is safe but not necessary in older > kernels. > > Signed-off-by: Stephen Hemminger > Reviewed-by: K. Y. Srinivasan > Reviewed-by: Christoph Hellwig >

[REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

Hi Long Li, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 40630f462824ee24bc00d692865c86c3828094e0 Author: Long Li Date: Wed Dec 14 18:46:03 2016 -0800 scsi:

[REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi: storvsc: properly set residual data length on errors

Hi Long Li, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 40630f462824ee24bc00d692865c86c3828094e0 Author: Long Li Date: Wed Dec 14 18:46:03 2016 -0800 scsi: storvsc: properly set

[REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit aeaa881f9b17823028b464893b89c42db797b717 Author: Ben Gamari Date: Tue Oct 4 11:43:30 2016 -0700 Input: ALPS

[REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit aeaa881f9b17823028b464893b89c42db797b717 Author: Ben Gamari Date: Tue Oct 4 11:43:30 2016 -0700 Input: ALPS - set DualPoint flag

Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

On 02/02/2017 03:36 PM, Laura Abbott wrote: > On 02/02/2017 12:17 PM, Joseph Salisbury wrote: >> Hi Matt, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit reso

Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

On 02/02/2017 03:36 PM, Laura Abbott wrote: > On 02/02/2017 12:17 PM, Joseph Salisbury wrote: >> Hi Matt, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit reso

Re: [REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

On 02/02/2017 03:57 PM, Greg KH wrote: > On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote: >> On 02/02/2017 01:23 PM, Greg KH wrote: >>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote: >>>> Hello, >>>

Re: [REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

On 02/02/2017 03:57 PM, Greg KH wrote: > On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote: >> On 02/02/2017 01:23 PM, Greg KH wrote: >>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote: >>>> Hello, >>>

Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

On 02/02/2017 03:36 PM, Laura Abbott wrote: > On 02/02/2017 12:17 PM, Joseph Salisbury wrote: >> Hi Matt, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit reso

Re: [REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

On 02/02/2017 03:36 PM, Laura Abbott wrote: > On 02/02/2017 12:17 PM, Joseph Salisbury wrote: >> Hi Matt, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit reso

[REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

Hi Matt, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 1297667083d5442aafe3e337b9413bf02b114edb Author: Matt Fleming Date: Mon Sep 19 13:09:09 2016 +0100

[REGRESSION][v4.9.y][v4.10.y] x86/efi: Only map RAM into EFI page tables if in mixed-mode

Hi Matt, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 1297667083d5442aafe3e337b9413bf02b114edb Author: Matt Fleming Date: Mon Sep 19 13:09:09 2016 +0100 x86/efi: Only map RAM into EFI

[REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

On 02/02/2017 01:23 PM, Greg KH wrote: > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote: >> Hello, >> >> Please consider reverting commit >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release. > What release can I remove it from? &g

[REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

On 02/02/2017 01:23 PM, Greg KH wrote: > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote: >> Hello, >> >> Please consider reverting commit >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release. > What release can I remove it from? &g

Subject: [REVERT][v4.x.y] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

in the following thread: https://lkml.org/lkml/2017/1/6/467 Sincerely, Joseph Salisbury

Subject: [REVERT][v4.x.y] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

in the following thread: https://lkml.org/lkml/2017/1/6/467 Sincerely, Joseph Salisbury

[Regression 4.7-rc1] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

Hi Luke, A kernel bug report was opened against Ubuntu [0]. This bug was fixed by the following commit in v4.7-rc1: commit 4c63c2454eff996c5e27991221106eb511f7db38 Author: Luke Dashjr Date: Thu Oct 29 08:22:21 2015 + btrfs: bugfix: handle

[Regression 4.7-rc1] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl

Hi Luke, A kernel bug report was opened against Ubuntu [0]. This bug was fixed by the following commit in v4.7-rc1: commit 4c63c2454eff996c5e27991221106eb511f7db38 Author: Luke Dashjr Date: Thu Oct 29 08:22:21 2015 + btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/18/2016 07:56 AM, Vincent Guittot wrote: > Le Tuesday 18 Oct 2016 à 12:34:12 (+0200), Peter Zijlstra a écrit : >> On Tue, Oct 18, 2016 at 11:45:48AM +0200, Vincent Guittot wrote: >>> On 18 October 2016 at 11:07, Peter Zijlstra wrote: So aside from funny BIOSes,

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/18/2016 07:56 AM, Vincent Guittot wrote: > Le Tuesday 18 Oct 2016 à 12:34:12 (+0200), Peter Zijlstra a écrit : >> On Tue, Oct 18, 2016 at 11:45:48AM +0200, Vincent Guittot wrote: >>> On 18 October 2016 at 11:07, Peter Zijlstra wrote: So aside from funny BIOSes, this should also show up

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

>> On 13 October 2016 at 20:49, Dietmar Eggemann <dietmar.eggem...@arm.com> >>>> wrote: >>>>> On 13/10/16 17:48, Vincent Guittot wrote: >>>>>> On 13 October 2016 at 17:52, Joseph Salisbury >>>>>> <joseph.salisb...@canonical

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

at 20:49, Dietmar Eggemann >>>> wrote: >>>>> On 13/10/16 17:48, Vincent Guittot wrote: >>>>>> On 13 October 2016 at 17:52, Joseph Salisbury >>>>>> wrote: >>>>>>> On 10/13/2016 06:58 AM, Vincent Guittot wrote: >>>

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/13/2016 06:58 AM, Vincent Guittot wrote: > Hi, > > On 12 October 2016 at 18:21, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> On 10/12/2016 08:20 AM, Vincent Guittot wrote: >>> On 8 October 2016 at 13:49, Mike Galbraith <efa...@gmx.de>

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/13/2016 06:58 AM, Vincent Guittot wrote: > Hi, > > On 12 October 2016 at 18:21, Joseph Salisbury > wrote: >> On 10/12/2016 08:20 AM, Vincent Guittot wrote: >>> On 8 October 2016 at 13:49, Mike Galbraith wrote: >>>> On Sat, 2016-10-08 at 13:37 +

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

eter Zijlstra <pet...@infradead.org> wrote: >>>> >>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote: >>>>>> Hello Peter, >>>>>> >>>>>> A kernel bug report was opened against Ubuntu [0]. Aft

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote: >>>>>> Hello Peter, >>>>>> >>>>>> A kernel bug report was opened against Ubuntu [0]. After a >>>>>> kernel >>>>>> bisect, it

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

eter Zijlstra <pet...@infradead.org> wrote: >>>> >>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote: >>>>>> Hello Peter, >>>>>> >>>>>> A kernel bug report was opened against Ubuntu [0]. Aft

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote: >>>>>> Hello Peter, >>>>>> >>>>>> A kernel bug report was opened against Ubuntu [0]. After a >>>>>> kernel >>>>>> bisect, it

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/07/2016 03:57 PM, Linus Torvalds wrote: > On Fri, Oct 7, 2016 at 12:38 PM, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On 10/07/2016 03:57 PM, Linus Torvalds wrote: > On Fri, Oct 7, 2016 at 12:38 PM, Joseph Salisbury > wrote: >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found that reverting the following commit resolved this bug: > Hmm. Interesting,

[v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

Hello Peter, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 3d30544f02120b884bba2a9466c87dba980e3be5 Author: Peter Zijlstra Date: Tue Jun 21 14:27:50 2016 +0200

[v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

Hello Peter, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 3d30544f02120b884bba2a9466c87dba980e3be5 Author: Peter Zijlstra Date: Tue Jun 21 14:27:50 2016 +0200 sched/fair: Apply more

[Regression][3.18-rc1 -> mainline] PCI: Configure *all* devices, not just hot-added ones

Hi Bjorn, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 1302fcf0d03e6ea74846c7fee14736306ab2ce4b Author: Bjorn Helgaas Date: Sat Aug 30 07:23:01 2014 -0600 PCI:

[Regression][3.18-rc1 -> mainline] PCI: Configure *all* devices, not just hot-added ones

Hi Bjorn, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 1302fcf0d03e6ea74846c7fee14736306ab2ce4b Author: Bjorn Helgaas Date: Sat Aug 30 07:23:01 2014 -0600 PCI: Configure *all* devices,

[PATCH 1/1][V3] usb: quirks: Add no-lpm quirk for Elan

BugLink: http://bugs.launchpad.net/bugs/1498667 As reported in BugLink, this device has an issue with Linux Power Management so adding a quirk. This quirk was reccomended by Alan Stern: http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html Signed-off-by: Joseph Salisbury <joseph.sal

[PATCH 1/1][V3] usb: quirks: Add no-lpm quirk for Elan

BugLink: http://bugs.launchpad.net/bugs/1498667 As reported in BugLink, this device has an issue with Linux Power Management so adding a quirk. This quirk was reccomended by Alan Stern: http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html Signed-off-by: Joseph Salisbury Cc: stable

Re: [PATCH 1/1][V2] usb: quirks: Add no-lpm quirk for Elan

On 07/06/2016 09:02 PM, Greg KH wrote: > On Wed, Jul 06, 2016 at 08:58:14PM -0400, Joseph Salisbury wrote: >> BugLink: http://bugs.launchpad.net/bugs/1498667 >> >> As reported in BugLink, this device has an issue with Linux Power >> Management so adding a quirk.

Re: [PATCH 1/1][V2] usb: quirks: Add no-lpm quirk for Elan

On 07/06/2016 09:02 PM, Greg KH wrote: > On Wed, Jul 06, 2016 at 08:58:14PM -0400, Joseph Salisbury wrote: >> BugLink: http://bugs.launchpad.net/bugs/1498667 >> >> As reported in BugLink, this device has an issue with Linux Power >> Management so adding a quirk.

[PATCH 1/1][V2] usb: quirks: Add no-lpm quirk for Elan

BugLink: http://bugs.launchpad.net/bugs/1498667 As reported in BugLink, this device has an issue with Linux Power Management so adding a quirk. This quirk was reccomended by Alan Stern: http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html Signed-off-by: Joseph Salisbury <joseph.sal

[PATCH 1/1][V2] usb: quirks: Add no-lpm quirk for Elan

BugLink: http://bugs.launchpad.net/bugs/1498667 As reported in BugLink, this device has an issue with Linux Power Management so adding a quirk. This quirk was reccomended by Alan Stern: http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html Signed-off-by: Joseph Salisbury Cc: stable

Re: [PATCH 1/1] usb: quirks: Add no-lpm quirk for Elan Microelectronics Touchpad

On 07/06/2016 07:10 PM, Greg KH wrote: > On Wed, Jul 06, 2016 at 05:53:47PM -0400, Joseph Salisbury wrote: >> BugLink: http://bugs.launchpad.net/bugs/1498667 >> >> As reported in BugLink, this device has an issue with Linux Power Management >> so >> adding a q

  1   2   3   4   5   6   >