[Kernel-packages] [Bug 1826447] [NEW] Azure: Backport vIOMMU driver (increase vCPU limits)

[Stephen A. Zarkos]

Public bug reported:

Description:

To support VM instances with >255 vCPUS, we need the patch set below
backported to the Azure 4.18 kernel. These patches include -

  - New Hyper-V IOMMU driver. This driver will be Hyper-V specific.
  - Minor update to the Hyper-V specific virtual PCI code. Need to expand the 
size of an array to allow for a larger number of vCPUs.

There are very large VM instance sizes coming to Azure in 2019, and
Ubuntu will require the following patches in order to function properly:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller
/pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1826447

Title:
   Azure: Backport vIOMMU driver (increase vCPU limits)

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Description:

  To support VM instances with >255 vCPUS, we need the patch set below
  backported to the Azure 4.18 kernel. These patches include -

- New Hyper-V IOMMU driver. This driver will be Hyper-V specific.
- Minor update to the Hyper-V specific virtual PCI code. Need to expand the 
size of an array to allow for a larger number of vCPUs.

  There are very large VM instance sizes coming to Azure in 2019, and
  Ubuntu will require the following patches in order to function
  properly:

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller
  /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1803173] Re: cloud-init disables user on azure at second reboot

[Stephen A. Zarkos]

Thanks All.

A newer Azure Agent which no longer touches cloud-init data is already
in the pipeline.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1803173

Title:
  cloud-init disables user on azure at second reboot

Status in cloud-init:
  Invalid
Status in linux package in Ubuntu:
  Triaged
Status in walinuxagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Environment:

  platform: Azure
  arm image: Canonical UbuntuServer 16.04-DAILY-LTS latest

  Steps:

  Deploy VM with user/pass authentication
  Install latest linux-next-upstream kernel (for example 4.19.0-4db9d11bcbef, 
where 4db9d11bcbef is the git tag from the linux-next latest tree: 
https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/)
  reboot (all good)
  reboot again
  cloud-init disables the username password authentication
  I checked the cloud-init logs and found:

  2018-11-01 16:45:28,566 - init.py[INFO]: User already exists, skipping.
  2018-11-01 16:45:28,570 - util.py[DEBUG]: Running command ['passwd', '-l', 
''] with allowed return codes [0] (shell=False, capture=True)
  2018-11-01 16:45:28,793 - util.py[DEBUG]: Reading from /etc/sudoers 
(quiet=False)
  2018-11-01 16:45:28,795 - util.py[DEBUG]: Read 781 bytes from /etc/sudoers
  2018-11-01 16:45:28,796 - util.py[DEBUG]: Writing to 
/etc/sudoers.d/90-cloud-init-users - ab: [None] 51 bytes
  2018-11-01 16:45:28,797 - handlers.py[DEBUG]: finish: 
init-network/config-users-groups: SUCCESS: config-users-groups ran successfully

  This issue is very bad one, as it can render your vm inaccessible on Azure.
  I think this problem is due to the new kernel installation.

  Initial bug report:
  https://github.com/Azure/WALinuxAgent/issues/1386

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1803173/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-azure source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  New

Bug description:
  == SRU Justification ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
  regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
  commit db5ff909798, which was added to mailine in v4.15-rc9.

  This commit has already been added to Bionic via upstream stable udpates.  
Xenial
  also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
  via the 4.4.48 stable updates(See bug lp1663657).

  
  == Fix ==
  commit db5ff909798ef0099004ad50a0ff5fde92426fd1
  Author: Xinyu Lin 
  Date:   Sun Dec 17 20:13:39 2017 +0800

  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable to fix a regression, so it
  received extra upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Description ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  At a high level the root cause of this problem is that the device only
  supports commands with a transfer size up to 512KB.  This worked fine
  with older versions of Linux but newer versions are attempting
  commands with a transfer size of 1280KB which is problematic for this
  device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

FYI, we are looking for this in the default Xenial kernel as well.
There are some bare metal systems in use that wouldn't be able to use
the Azure kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  In Progress
Status in linux-azure source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  New

Bug description:
  == SRU Justification ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
  regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
  commit db5ff909798, which was added to mailine in v4.15-rc9.

  This commit has already been added to Bionic via upstream stable udpates.  
Xenial
  also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
  via the 4.4.48 stable updates(See bug lp1663657).

  
  == Fix ==
  commit db5ff909798ef0099004ad50a0ff5fde92426fd1
  Author: Xinyu Lin 
  Date:   Sun Dec 17 20:13:39 2017 +0800

  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable to fix a regression, so it
  received extra upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Description ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  At a high level the root cause of this problem is that the device only
  supports commands with a transfer size up to 512KB.  This worked fine
  with older versions of Linux but newer versions are attempting
  commands with a transfer size of 1280KB which is problematic for this
  device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

Hi,

The team has tested the kernel in comment #5 and confirmed that it
resolves the issue.  Thanks!

BTW, we need this patch in Xenial as well since we are using the LTS.

Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

I'll double check, but I don't think it's needed in linux-image-azure.
Do you have a link to the test kernel packages?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

No longs, this is an upstream fix from the vendor.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743053] [NEW] libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

Public bug reported:

Some SSD drives made by LiteOn can crash the kernel due to bad drivers.
A fix for this issue has been submitted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

LITEON EP1 has the same timeout issues as CX1 series devices.

Revert max_sectors to the value of 1024.

'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices")'

Signed-off-by: Xinyu Lin 
Signed-off-by: Tejun Heo 
Cc: sta...@vger.kernel.org


At a high level the root cause of this problem is that the device only supports 
commands with a transfer size up to 512KB.  This worked fine with older 
versions of Linux but newer versions are attempting commands with a transfer 
size of 1280KB which is problematic for this device (LITEON EP1-KB480)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  New

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

Hi Joseph,

We've tested your previous Xenial test kernel from comment #5. Have
there been any changes that we need to test again, or can we test when
the kernel moves to proposed?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

Test case from comment #3 passed using the -proposed kernel for Xenial
and Yakkey.

** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Related bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539

  This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
  kernels. Can you please pull this patch back to Xenial+?

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1669941] Re: CIFS: Call echo service immediately after socket reconnect

[Stephen A. Zarkos]

** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1669941

Title:
  CIFS: Call echo service immediately after socket reconnect

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When using Azure Files, a "Host is down" error can occur with the
  Linux CIFS client when the client has been idle for an extended period
  of time.  Commit 4fcd1813e640 mostly resolved this issue and is
  already integrated into the Xenial kernel.

  The following additional patch is needed to fully resolve a related
  corner case. Please take this commit to the Xenial kernel and later:

  Call echo service immediately after socket reconnect
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b8c600120fc87d53642476f48c8055b38d6e14c7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669941/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

Hi,

The test looks good, here are my repro steps:

 1) Create an Ubuntu 16.04 VM in Azure
 2) Attach 128GB data disk
 3) Partition and format the disk
# wipefs --all /dev/sdc
# sgdisk -Z /dev/sdc
# sgdisk -n '1:2048::264191' /dev/sdc
# mkfs.ext4 /dev/sdc1

Expected result: mkfs should return very quickly because
lazy_itable_init is enabled.

Actual test results:

  - Kernel 4.4.0-71.92: mkfs blocks and formatting takes about
8-minutes.

  - Kernel 4.4.0-73.94~lp1682215: mkfs returns immediately.


Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Related bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539

  This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
  kernels. Can you please pull this patch back to Xenial+?

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1682215] [NEW] [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

Public bug reported:

Related bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539

This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
kernels. Can you please pull this patch back to Xenial+?

https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

author
Ming Lei 
2016-12-17 10:49:09 (GMT)
committer
Jens Axboe 
2017-01-12 03:47:08 (GMT)
commit
729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
tree
ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
parent
1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
block: relax check on sg gap
If the last bvec of the 1st bio and the 1st bvec of the next
bio are physically contigious, and the latter can be merged
to last segment of the 1st bio, we should think they don't
violate sg gap(or virt boundary) limit.

Both Vitaly and Dexuan reported lots of unmergeable small bios
are observed when running mkfs on Hyper-V virtual storage, and
performance becomes quite low. This patch fixes that performance
issue.

The same issue should exist on NVMe, since it sets virt boundary too.

Reported-by: Vitaly Kuznetsov 
Reported-by: Dexuan Cui 
Tested-by: Dexuan Cui 
Cc: Keith Busch 
Signed-off-by: Ming Lei 
Signed-off-by: Jens Axboe 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

Status in linux package in Ubuntu:
  New

Bug description:
  Related bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539

  This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
  kernels. Can you please pull this patch back to Xenial+?

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

No logs needed.  Thanks.

** Description changed:

  There has been work upstream to enable encryption support for SMB3
- connections. This is particularly useful with the Azure Files feature as
- encryption is required to connected to an Azure Files storage share from
- on-prem or from a different region.
+ connections. This is a particularly valuable (and commonly requested)
+ feature with the Azure Files service as encryption is required to
+ connect to an Azure Files storage share from on-prem or from a different
+ Azure region.
  
  The relevant commits are as follows:
  
  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5
  
- CIFS: Allow to switch on encryption with seal mount option 
+ CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31
  
  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad
  
  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840
  
  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e
  
  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e
  
  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e
  
  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398
  
  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb
  
  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85
  
  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6
  
  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef
  
  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf
  
  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e
  
  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5
  
  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7
  
  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a
  
  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1
  
  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
 

[Kernel-packages] [Bug 1670508] [NEW] CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

Public bug reported:

There has been work upstream to enable encryption support for SMB3
connections. This is particularly useful with the Azure Files feature as
encryption is required to connected to an Azure Files storage share from
on-prem or from a different region.

The relevant commits are as follows:

CIFS: Fix possible use after free in demultiplex thread
Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

CIFS: Allow to switch on encryption with seal mount option 
Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

CIFS: Add capability to decrypt big read responses
Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

CIFS: Decrypt and process small encrypted packets
Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

CIFS: Add copy into pages callback for a read operation
Commit d70b9104b1ca586f73aaf59426756cec3325a40e

CIFS: Add mid handle callback
Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

CIFS: Add transform header handling callbacks
Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

CIFS: Encrypt SMB3 requests before sending
Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

CIFS: Enable encryption during session setup phase
Commit cabfb3680f78981d26c078a26e5c748531257ebb

CIFS: Add capability to transform requests before sending
Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

CIFS: Separate RFC1001 length processing for SMB2 read
Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

CIFS: Separate SMB2 sync header processing
Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

CIFS: Send RFC1001 length in a separate iov
Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

CIFS: Make send_cancel take rqst as argument
Commit fb2036d817584df42504910fe104f68517e8990e

CIFS: Make SendReceive2() takes resp iov
Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

CIFS: Separate SMB2 header structure
Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

cifs: Add soft dependencies
Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

cifs: Only select the required crypto modules
Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

cifs: Simplify SMB2 and SMB311 dependencies
Commit c1ecea87471bbb614f8121e00e5787f363140365

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is particularly useful with the Azure Files feature
  as encryption is required to connected to an Azure Files storage share
  from on-prem or from a different region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option 
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1669941] [NEW] CIFS: Call echo service immediately after socket reconnect

[Stephen A. Zarkos]

Public bug reported:

When using Azure Files, a "Host is down" error can occur with the Linux
CIFS client when the client has been idle for an extended period of
time.  Commit 4fcd1813e640 mostly resolved this issue and is already
integrated into the Xenial kernel.

The following additional patch is needed to fully resolve a related
corner case. Please take this commit to the Xenial kernel and later:

Call echo service immediately after socket reconnect
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b8c600120fc87d53642476f48c8055b38d6e14c7

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1669941

Title:
  CIFS: Call echo service immediately after socket reconnect

Status in linux package in Ubuntu:
  New

Bug description:
  When using Azure Files, a "Host is down" error can occur with the
  Linux CIFS client when the client has been idle for an extended period
  of time.  Commit 4fcd1813e640 mostly resolved this issue and is
  already integrated into the Xenial kernel.

  The following additional patch is needed to fully resolve a related
  corner case. Please take this commit to the Xenial kernel and later:

  Call echo service immediately after socket reconnect
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b8c600120fc87d53642476f48c8055b38d6e14c7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669941/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

It seems the Utopic kernel is impacted as well, I tested
3.16.0-62-generic released on 2/27.  I thought that kernel was EOL.  Can
we revert the fix here as well?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

Status in cloud-init package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in cloud-init source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.

  This recent kernel patch in the Ubuntu kernel incorrectly modifies the
  endianness for some SMBIOS fields, which has the effect causing cloud-
  init to think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.

  This recent kernel patch in the Ubuntu kernel corrects the endianness
  for some SMBIOS fields, but also has the effect causing cloud-init to
  think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

  The impact is that cloud-init attempts to reprovision the VM, often
  causing the customer to lose access to their VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] [NEW] Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

Public bug reported:

On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance.  If this ID ever changes, then cloud-
init will attempt to reprovision the VM.

This recent kernel patch in the Ubuntu kernel corrects the endianness
for some SMBIOS fields, but also has the effect causing cloud-init to
think that the system-uuid has changed:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

The impact is that cloud-init attempts to reprovision the VM, often
causing the customer to lose access to their VM.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

Status in linux package in Ubuntu:
  New

Bug description:
  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.

  This recent kernel patch in the Ubuntu kernel corrects the endianness
  for some SMBIOS fields, but also has the effect causing cloud-init to
  think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

  The impact is that cloud-init attempts to reprovision the VM, often
  causing the customer to lose access to their VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-trusty verification-done-vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498206

Title:
  Fix CPU lockup on Hyper-V/Azure

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  Description of problem:
  Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at 
boot, and the console keeps printing logs like "soft lockup - CPU#14 stuck for 
23s!"

  This particular issue can be resolved with the following patch upstream: 
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

  Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
  Azure) and reboot many times, monitoring the console until the "soft
  lockup - CPU" error is seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1508706] Re: Networking hangs on azure using hv_netvsc; bisected

[Stephen A. Zarkos]

KY has pushed a patch to LKML that resolves this issue:
https://lkml.org/lkml/2015/11/18/690

This patch needs to be applied to the Vivid kernel and beyond.  This is
a critical patch, can you please take this patch as sauce for now so we
can get it out as quickly as possible?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1508706

Title:
  Networking hangs on azure using hv_netvsc; bisected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  Running Ubuntu instances on azure, testing basic networking between two 
instances.  This involves configuring VXLAN between the two instances and 
running iperf and rsync of the kernel tree between the instances, e.g.,

  ip link add vxlan0 type vxlan id 999 local 10.88.0.12 remote 10.88.0.11 dev 
eth0
  ip l set vxlan0 up
  ip addr add 242.0.0.12/8 dev vxlan0

  After some time (sometimes instantly, sometimes up to 30 minutes of
  activity), the networking will hang.  This hang takes two forms:  a
  complete loss of connectivity (all network, even the ssh session used
  to log in), or just a loss of connectivity between instances (the ssh
  session remains active).  Sometimes for the latter case, the ssh
  session will then later hang.

  This first appeared when testing with the Ubuntu 3.19 kernel, and I
  subsequently bisected this to:

  commit effa2012d207f78cbc5a8360e62d420a8860b7e9
  Author: KY Srinivasan 
  Date:   Mon May 11 15:39:46 2015 -0700

  hv_netvsc: Use the xmit_more skb flag to optimize signaling the
  host

  BugLink: http://bugs.launchpad.net/bugs/1454892

  Based on the information given to this driver (via the xmit_more skb 
flag),
  we can defer signaling the host if more packets are on the way. This will 
help
  make the host more efficient since it can potentially process a larger 
batch of
  packets. Implement this optimization.

  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 
  Acked-by: Tim Gardner 
  Acked-by: Brad Figg 
  Signed-off-by: Brad Figg 

  I also tested the mainline kernel (net-next); it fails with the
  equivalent commit:

  commit 82fa3c776e5abba7ed6e4b4f4983d14731c37d6a
  Author: KY Srinivasan 
  Date:   Mon May 11 15:39:46 2015 -0700

  hv_netvsc: Use the xmit_more skb flag to optimize signaling the
  host

  For both kernel trees, I also tested the prior commit and it did not
  exhibit the failure after many hours.  For ubuntu, this was

  commit a4aeb290bd75af5e16a6144a418291476ac6140c
  Author: K. Y. Srinivasan 
  Date:   Wed Mar 18 12:29:29 2015 -0700

  Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl()

  and for mainline it was

  commit 9eea92226407e7a117ef1ceef45380ebd000a0e2
  Author: Alexei Starovoitov 
  Date:   Mon May 11 15:19:48 2015 -0700

  pktgen: fix packet generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508706/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

HI Joseph,

Can we please raise the priority of this to get it into Trusty and Vivid
as soon as possible?  We are seeing more repros of this issue on Azure.

Thanks,
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498206

Title:
  Fix CPU lockup on Hyper-V/Azure

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Description of problem:
  Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at 
boot, and the console keeps printing logs like "soft lockup - CPU#14 stuck for 
23s!"

  This particular issue can be resolved with the following patch upstream: 
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

  Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
  Azure) and reboot many times, monitoring the console until the "soft
  lockup - CPU" error is seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498206] [NEW] Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

Public bug reported:

Description of problem:
Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at boot, 
and the console keeps printing logs like "soft lockup - CPU#14 stuck for 23s!"

This particular issue can be resolved with the following patch upstream: 
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
Azure) and reboot many times, monitoring the console until the "soft
lockup - CPU" error is seen.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498206

Title:
  Fix CPU lockup on Hyper-V/Azure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description of problem:
  Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at 
boot, and the console keeps printing logs like "soft lockup - CPU#14 stuck for 
23s!"

  This particular issue can be resolved with the following patch upstream: 
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

  Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
  Azure) and reboot many times, monitoring the console until the "soft
  lockup - CPU" error is seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

No logs required.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1498206

Title:
  Fix CPU lockup on Hyper-V/Azure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description of problem:
  Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at 
boot, and the console keeps printing logs like "soft lockup - CPU#14 stuck for 
23s!"

  This particular issue can be resolved with the following patch upstream: 
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

  Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
  Azure) and reboot many times, monitoring the console until the "soft
  lockup - CPU" error is seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

Testing complete, no issues found.  Thanks!

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

Our team has tested the Vivid proposed kernel and found no regressions.
Performance is comparable to previous test kernels.

Thanks!


** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

Hi Joseph,

Do you know will these patches will be available in the next kernel
maintenance release?

Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

@Joseph, I swear I thought I responded to this bug, sorry for the delay.
We have finished testing the Trusty kernel you posted at
http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty, and confirmed
performance is better.

Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

We tested the Utopic kernel and it works fine now.  No crashes or issues
and performance is better.

Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

We'll test this new kernel.  It appears the directory
/~jsalisbury/lp1445195/utopic is empty, but it looks like the kernel
was placed in the /~jsalisbury/lp1445195 directory instead.  I assume
this is the correct kernel, but to be safe can you confirm?

Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

Both these test kernels for Trusty and Utopic worked as well.

Thanks,
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1463584

Title:
  [Hyper-V] Add support for VMBus panic notifier handler

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Please take these patches to our Hyper-V VMBus driver to enable kernel
  crash notification:

  Drivers: hv: vmbus: Add support for VMBus panic notifier handler
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

  Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13

  
  In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

The test team has tested the Vivid kernel and confirmed that it works as
expected.  So let's please ack these patches for the next Vivid kernel.

The Utopic kernel provided crashes at boot time, so we're unable to test
that.  Can you help us debug that issue?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Wily:
  Triaged

Bug description:
  Storage driver performance updates for vivid

  K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve information about the capability of the target
scsi: storvsc: Fix a bug in copy_from_bounce_buffer()
scsi: storvsc: Don't assume that the scatterlist is not chained
scsi: storvsc: Set the tablesize based on the information given by the host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1463584] Re: Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

No logs required.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1463584

Title:
  Add support for VMBus panic notifier handler

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please take these patches to our Hyper-V VMBus driver to enable kernel
  crash notification:

  Drivers: hv: vmbus: Add support for VMBus panic notifier handler
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

  Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13

  
  In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1463584] Re: Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

Test case on Hyper-V:
  - Run: echo c  /proc/sysrq-trigger
  - If the Panic Notifier code is present, an event 18590 should be logged.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1463584

Title:
  Add support for VMBus panic notifier handler

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please take these patches to our Hyper-V VMBus driver to enable kernel
  crash notification:

  Drivers: hv: vmbus: Add support for VMBus panic notifier handler
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

  Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13

  
  In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1463584] [NEW] Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

Public bug reported:

Please take these patches to our Hyper-V VMBus driver to enable kernel
crash notification:

Drivers: hv: vmbus: Add support for VMBus panic notifier handler
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13


In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-hyper-v

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1463584

Title:
  Add support for VMBus panic notifier handler

Status in linux package in Ubuntu:
  New

Bug description:
  Please take these patches to our Hyper-V VMBus driver to enable kernel
  crash notification:

  Drivers: hv: vmbus: Add support for VMBus panic notifier handler
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

  Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
  
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13

  
  In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

Hi,

OK, sorry for the delay and misunderstanding.  I tested linux-
image-3.2.0-80-generic from precise-proposed and confirmed that it also
has the patch and the issue is resolved.

Thanks again,
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

Hi,

I confirmed the fix in comment #4.  Is there something I should click on
here to validate the fix?

Thanks,
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

Hi Joseph,

We've tested this kernel and no longer see this issue.  I think we are
OK to proceed.

Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

Thanks for this, we will take this kernel and test.  The issue is
intermittent and would likely only show up during stress tests, so it
may take a few days for results.

Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Triaged

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417313] [NEW] [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

Public bug reported:

This issue impacts Ubuntu 12.04.

Whenever a device is unregistered in vmbus_device_unregister
(drivers/hv/vmbus_drv.c), the device name in the log message may contain
garbage as the memory has already been freed by the time pr_info is
called.  Log example:

  [ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

By logging the message just before calling device_unregister, the
correct device name is printed:

  [ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered


This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

Status in linux package in Ubuntu:
  New

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1400947] [NEW] Upstream bugfixes for hv_vmbus

[Stephen A. Zarkos]

Public bug reported:

Please take these upstream patches for the Hyper-V VMBus driver.  In
some cases we are seeing crashes due to these bugs on Hyper-V and Azure.


commit 72c6b71c245dac8f371167d97ef471b367d0b66b
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:34 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl()


commit b29ef3546aecb253a5552b198cef23750d56e1e4
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Thu Aug 28 18:29:52 2014 -0700

Drivers: hv: vmbus: Cleanup hv_post_message()


commit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:33 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_close_internal()


commit 45d727cee9e200f5b351528b9fb063b69cf702c8
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:35 2014 -0700

Drivers: hv: vmbus: Fix a bug in vmbus_open()

commit 66be653083057358724d56d817e870e53fb81ca7
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:32 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()


commit fdeebcc62279119dbeafbc1a2e39e773839025fd
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:31 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_post_msg()

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1400947

Title:
  Upstream bugfixes for hv_vmbus

Status in linux package in Ubuntu:
  New

Bug description:
  Please take these upstream patches for the Hyper-V VMBus driver.  In
  some cases we are seeing crashes due to these bugs on Hyper-V and
  Azure.

  
  commit 72c6b71c245dac8f371167d97ef471b367d0b66b
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Wed Aug 27 16:25:34 2014 -0700

  Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl()

  
  commit b29ef3546aecb253a5552b198cef23750d56e1e4
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Thu Aug 28 18:29:52 2014 -0700

  Drivers: hv: vmbus: Cleanup hv_post_message()

  
  commit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Wed Aug 27 16:25:33 2014 -0700

  Drivers: hv: vmbus: Cleanup vmbus_close_internal()

  
  commit 45d727cee9e200f5b351528b9fb063b69cf702c8
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Wed Aug 27 16:25:35 2014 -0700

  Drivers: hv: vmbus: Fix a bug in vmbus_open()

  commit 66be653083057358724d56d817e870e53fb81ca7
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Wed Aug 27 16:25:32 2014 -0700

  Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()

  
  commit fdeebcc62279119dbeafbc1a2e39e773839025fd
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Wed Aug 27 16:25:31 2014 -0700

  Drivers: hv: vmbus: Cleanup vmbus_post_msg()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400947/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1354397] Re: Latest fixes from storvsc scsi drivers for Hyper-V/Azure

[Stephen A. Zarkos]

Hi,

The Azure test team has completed testing the proposed kernel package
for Trusty and verified that all fixes work as expected.  Please mark
this as verification complete.

Thanks!
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1354397

Title:
  Latest fixes from storvsc  scsi drivers for Hyper-V/Azure

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  A number of significant fixes have landed upstream for Hyper-V/Azure
  clouds.  The upstream devs for this recommend we apply the below list
  of patches:

  commit 26b9fd8b3452dcf0a8862e307ee23f442f63fb51
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Fri Jul 18 17:11:27 2014 +0200

  sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O
  timeout

  commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:26 2014 -0700

  Drivers: scsi: storvsc: Change the limits to reflect the values on
  the host

  commit 52f9614dd8294e95d2c0929c2d4f64b077ae486f
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:27 2014 -0700

  Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported
  by the Host

  commit 8caf92d80526f3d7cc96831ec18b384ebcaccdf0
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:28 2014 -0700

  Drivers: scsi: storvsc: Filter commands based on the storage
  protocol version

  commit adb6f9e1a8c6af1037232b59edb11277471537ea
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:29 2014 -0700

  Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol
  version

  commit 56b26e69c8283121febedd12b3cc193384af46b9
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:30 2014 -0700

  Drivers: scsi: storvsc: Implement a eh_timed_out handler

  commit f885fb73f64154690c2158e813de56363389ffec
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:31 2014 -0700

  drivers: scsi: storvsc: Set srb_flags in all cases

  commit 3533f8603d28b77c62d75ec899449a99bc6b77a1
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:32 2014 -0700

  drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure

  commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Mon Jul 21 16:06:01 2014 -0700

  Drivers: add blist flags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1354397] Re: Latest fixes from storvsc scsi drivers for Hyper-V/Azure

[Stephen A. Zarkos]

Andy, thanks for taking these.  All these changes passed our tests
except for TRIM.

It looks like we'll need to take a closer look at how to fix TRIM
upstream.  We probably will not get that upstream before kernel freeze.
Do you think it be possible to re-base your original patch to re-enable
SPC-3 in Hyper-V so that we don't regress this feature
(http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commit;h=ff2c5fa3fa9adf0b919b9425e71a8ba044c31a7d)?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1354397

Title:
  Latest fixes from storvsc  scsi drivers for Hyper-V/Azure

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Released

Bug description:
  A number of significant fixes have landed upstream for Hyper-V/Azure
  clouds.  The upstream devs for this recommend we apply the below list
  of patches:

  commit 26b9fd8b3452dcf0a8862e307ee23f442f63fb51
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Fri Jul 18 17:11:27 2014 +0200

  sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O
  timeout

  commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:26 2014 -0700

  Drivers: scsi: storvsc: Change the limits to reflect the values on
  the host

  commit 52f9614dd8294e95d2c0929c2d4f64b077ae486f
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:27 2014 -0700

  Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported
  by the Host

  commit 8caf92d80526f3d7cc96831ec18b384ebcaccdf0
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:28 2014 -0700

  Drivers: scsi: storvsc: Filter commands based on the storage
  protocol version

  commit adb6f9e1a8c6af1037232b59edb11277471537ea
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:29 2014 -0700

  Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol
  version

  commit 56b26e69c8283121febedd12b3cc193384af46b9
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:30 2014 -0700

  Drivers: scsi: storvsc: Implement a eh_timed_out handler

  commit f885fb73f64154690c2158e813de56363389ffec
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:31 2014 -0700

  drivers: scsi: storvsc: Set srb_flags in all cases

  commit 3533f8603d28b77c62d75ec899449a99bc6b77a1
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:32 2014 -0700

  drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure

  commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Mon Jul 21 16:06:01 2014 -0700

  Drivers: add blist flags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1354397] Re: Latest fixes from storvsc scsi drivers for Hyper-V/Azure

[Stephen A. Zarkos]

Thanks Srikanth.  These logs look typical of some of our stress tests.
Can you confirm that the other tests passed, including the new fix
upstream to enable unmap/trim?

Thanks,
Steve

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1354397

Title:
  Latest fixes from storvsc  scsi drivers for Hyper-V/Azure

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress
Status in “linux” source package in Utopic:
  In Progress

Bug description:
  A number of significant fixes have landed upstream for Hyper-V/Azure
  clouds.  The upstream devs for this recommend we apply the below list
  of patches:

  commit 26b9fd8b3452dcf0a8862e307ee23f442f63fb51
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Fri Jul 18 17:11:27 2014 +0200

  sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O
  timeout

  commit 4cd83ecdac20d30725b4f96e5d7814a1e290bc7e
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:26 2014 -0700

  Drivers: scsi: storvsc: Change the limits to reflect the values on
  the host

  commit 52f9614dd8294e95d2c0929c2d4f64b077ae486f
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:27 2014 -0700

  Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported
  by the Host

  commit 8caf92d80526f3d7cc96831ec18b384ebcaccdf0
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:28 2014 -0700

  Drivers: scsi: storvsc: Filter commands based on the storage
  protocol version

  commit adb6f9e1a8c6af1037232b59edb11277471537ea
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:29 2014 -0700

  Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol
  version

  commit 56b26e69c8283121febedd12b3cc193384af46b9
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:30 2014 -0700

  Drivers: scsi: storvsc: Implement a eh_timed_out handler

  commit f885fb73f64154690c2158e813de56363389ffec
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:31 2014 -0700

  drivers: scsi: storvsc: Set srb_flags in all cases

  commit 3533f8603d28b77c62d75ec899449a99bc6b77a1
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Sat Jul 12 09:48:32 2014 -0700

  drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure

  commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6
  Author: K. Y. Srinivasan k...@microsoft.com
  Date:   Mon Jul 21 16:06:01 2014 -0700

  Drivers: add blist flags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp