ed 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
>
ed 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
>
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 resid
96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 40
2 files changed, 51 insertions(+)
diff --git a/drivers/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h
index e055176
Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
Commit 96c1d05 does not apply cleanly to v3.14.y, so I performed a backport,
which is in email 1/1.
Sincerely,
Joseph Salisbury
Nick Meier (1):
Drivers: hv: vmbus: Add support for VMBus panic notifier
-Hartman
(backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 40
2 files changed, 51 insertions(+)
diff --git a/drivers/hv
Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
Commit 96c1d05 does not apply cleanly to v3.13.y-ckt, so I performed a
backport, which is
in email 1/1.
Sincerely,
Joseph Salisbury
Nick Meier (1):
Drivers: hv: vmbus: Add support for VMBus panic
On 06/16/2015 04:41 PM, Greg KH wrote:
> On Tue, Jun 16, 2015 at 04:10:46PM -0400, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider including upstream commits
>> 96c1d0581d00f7abe033350edb021a9d947d8d81 and
>> 5ef5b6927f14f29cacd78fa1fb861661a5367f1
96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
Conflicts:
drivers/hv/vmbus_drv.c
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 40
2 files changed, 51 insertions(+)
diff --git a/drivers/hv/hyperv_vmbus.h b
-Hartman
(Backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 35 +++
2 files changed, 46 insertions(+)
diff --git a/drivers/hv/hyperv_vmbus.h b
Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
Commit 96c1d05 does not apply cleanly to v3.13.y-ckt, so I performed a
backport, which is
in email 1/1.
Sincerely,
Joseph Salisbury
Nick Meier (2):
Drivers: hv: vmbus: Add support for VMBus panic
-Hartman
(backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 35 +++
2 files changed, 46 insertions(+)
diff --git a/drivers/hv/hyperv_vmbus.h b
/bugs/1439780
commit dc45708ca9988656d706940df5fd102672c5de92
Author: K. Y. Srinivasan
Date: Fri May 1 11:03:02 2015 -0700
storvsc: Set the SRB flags correctly when no data transfer is needed
Sincerely,
Joseph Salisbury
___
devel mailing
On 06/05/2015 01:51 PM, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> dc45708ca9988656d706940df5fd102672c5de92 in the next v3.18.y, v4.0.y and
> 3.19.y-ckt stable releases. It was
> included in the mainline tree as of v4.1-rc5. It h
On 09/27/2013 06:50 AM, Jiri Kosina wrote:
> On Wed, 25 Sep 2013, Joseph Salisbury wrote:
>
>> After further testing reverting the following commit does in fact
>> resolve the bug:
>>
>> commit b1a1442a23776756b254b69786848a94d92445ba
>> Author: Jiri Kosina
&g
On 09/24/2013 05:29 AM, Jiri Kosina wrote:
> On Mon, 16 Sep 2013, Joseph Salisbury wrote:
>
>>>> Can you explain a little further? Mark commit a4a23f6 as bad? An
>>>> initial bisect already reported that was the first bad commit, so it
>>>> can'
On 09/24/2013 05:29 AM, Jiri Kosina wrote:
> On Mon, 16 Sep 2013, Joseph Salisbury wrote:
>
>>>> Can you explain a little further? Mark commit a4a23f6 as bad? An
>>>> initial bisect already reported that was the first bad commit, so it
>>>> can'
On 09/24/2013 05:29 AM, Jiri Kosina wrote:
> On Mon, 16 Sep 2013, Joseph Salisbury wrote:
>
>>>> Can you explain a little further? Mark commit a4a23f6 as bad? An
>>>> initial bisect already reported that was the first bad commit, so it
>>>> can'
On 09/16/2013 05:05 PM, Dan Carpenter wrote:
> On Mon, Sep 16, 2013 at 04:49:29PM -0400, Joseph Salisbury wrote:
>> On 09/16/2013 04:38 PM, Dan Carpenter wrote:
>>> On Mon, Sep 16, 2013 at 01:42:35PM -0400, Joseph Salisbury wrote:
>>>> Reverting the patch changes the
On 09/16/2013 04:38 PM, Dan Carpenter wrote:
> On Mon, Sep 16, 2013 at 01:42:35PM -0400, Joseph Salisbury wrote:
>> Reverting the patch changes the driver back to useing kzalloc() and
>> memcpy() instead of kmemdup. Doing so has uncovered another bug, which
>> causes an oop
Hi Thomas,
A bug was opened against the Ubuntu kernel[0]. After a kernel bisect,
it was found that reverting the following commit resolved
this bug:
commit a4a23f6d68ad2c86ee8df6a6f89c9d315c0a761c
Author: Thomas Meyer
Date: Sat Jun 1 11:40:31 2013 +0200
HID: hyperv: convert alloc+memcpy
Author: K. Y. Srinivasan
Date: Wed Jan 23 17:42:45 2013 -0800
Drivers: hv: Execute shutdown in a thread context
Sincerely,
Joseph Salisbury
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman
22 matches
Mail list logo
