** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
This bug was fixed in the package linux - 3.13.0-79.123
---
linux (3.13.0-79.123) trusty; urgency=low
[ Seth Forshee ]
* SAUCE: cred: Add clone_cred() interface
- LP: #1534961, #1535150
- CVE-2016-1575 CVE-2016-1576
* SAUCE: overlayfs: Use mounter's credentials instead
This bug was fixed in the package linux-lts-trusty -
3.13.0-79.123~precise1
---
linux-lts-trusty (3.13.0-79.123~precise1) precise; urgency=low
[ Seth Forshee ]
* SAUCE: cred: Add clone_cred() interface
- LP: #1534961, #1535150
- CVE-2016-1575 CVE-2016-1576
* SAUCE: over
This bug was fixed in the package linux-lts-trusty -
3.13.0-79.123~precise1
---
linux-lts-trusty (3.13.0-79.123~precise1) precise; urgency=low
[ Seth Forshee ]
* SAUCE: cred: Add clone_cred() interface
- LP: #1534961, #1535150
- CVE-2016-1575 CVE-2016-1576
* SAUCE: over
@jsalisbury Thanks, I think that is the best path forward. The flow
dissector will stop the bunching up of activity on CPU 0 which will help
us see what other items are missing. 3.16 is better, even without it,
though. Vivid 3.19 has a form of it now. Wily 4.2 also has a form of it.
Xenial as well.
@josh
Thanks for the update. I'll continue to see if we can build a Trusty
test kernel with commit 757647e applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus
@chris,
Sorry for my confusion. If this is not a new regression then we are ok
to release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
@Chris,
I'm reviewing comment #33. Just to confirm, you do not believe this
performance issue is a regression with the 3.13.0-78.122 Trusty kernel
in -proposed? All of the Trusty kernels going back to 3.13.0-24 have
this issue?
If that is the case, this may be an entirely different bug that we
@brad-figg We are very sorry.
The bottom line is that we are not seeing good performance on 3.13 going
back for many builds, with or without the 7 patches we are requesting.
Do not hold any release for resolution of this issue. I recommend going
forward with the 7 patches in place.
The difference
@chris,
As I tried to explain yesterday we can't release a kernel with known
regressions in it. We need your help in bisecting the kernel to find the
commit that is causing the regression. The testing we are doing in-house
is not showing the regression.
--
You received this bug notification beca
Based on the numbers here, I will continue to include some patches or
suggestions we got from Haiyang, and send an update later.
You should be able to push the update as this seems to be a problem with 3.13
entire tree, then in a separate thread we can identify the missing patches.
These are the
If you find that Ubuntu-3.13.0-76.120 is good and it does not cause the
performance regression, can you test Ubuntu-3.13.0-77.121 as well? This
will shorten our bisect window.
The Ubuntu-3.13.0-77.121 kernel can be downloaded from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa
I think we should stick to testing on Trusty for now. The backport
kernel goes into Trusty(As the -updates kernel) and then into Precise.
Since we see this regression with Trusty as the userspace, we should
continue to test there.
--
You received this bug notification because you are a member of
Thanks Joe for the quick work on this.
To clarify on the distro release to use, we tested all kernels from this thread
on top of Trusty.
However, this kernel is supposed to go for Precise - 12.04.
Question is, if it's safe to continue do all the testing on Trusty, or
actually switch to Precise? I
The test kernel in comment #13 was built on top of Ubuntu-3.13.0-76.120.
It had the 7 commits listed in comment #18 applied. It did not have
the performance regression per comment #14.
The test kernel in comment #19 was built on top of Ubuntu-3.13.0-78.122
I had the 7 commits listed in comment #
The test kernel from comment #19 also has the network performance
regression.
For that reason we are looking to test this with all the mentioned 7
patches and in addition with the patch from comment #26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
@Chris, I'll investigate and get a test kernel build for you. It may be
that commit 757647e requires some prereq commits.
Also, have you had a chance to test the kernel posted in comment #19 to
see if the commits applied to the master-next tree were what introduced
the performance regression?
--
Joe, we would like to also get your input on the below.
In the trusty kernel (Ubuntu-3.13.0-77.121 -
https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/trusty/+ref/master)
we tried to include the below patch to see if that resolves the network
performance regression issue.
Patch
Brad, in regards to comment #21.
We've tested the proposed kernel v4.2.0-29.34 on Wily and the
performance is looking good. Please merge the changes.
I have a small question in regards to versioning.
When doing the install of the proposed kernel, in one place in apt-get I get
that "Selected vers
Neither my test kernel from comment #13 nor the -proposed Trusty kernel
have commit d34af82 applied. However, my test kernel did not exhibit
the performance regression. My test kernel had good results per comment
#14. @Chris, could there have been an issue with the test and maybe my
kernel did a
Actually I was referring to commit 757647e10e in comment #23, which
actually fixes a performance introduced by commit d34af82.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V]
In response to comment #18, this probably needs
http://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=757647e10e55c01fb7a9c4356529442e316a7c72
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
This fix has been applied to Wily and is in the 4.2.0-29.34 version that
is currently in -proposed. Would be nice to get that tested to verify.
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Com
Upstream commit 8599846d upstream should have put this into Wily/Xenial.
Is that in there? If so, we can close those.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus
I built a Trust -proposed test kernel with the 7 commits reverted. Can
you test this kernel and see if it still exhibits the performance
regression? The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1519897/trusty-proposed/
--
You received this bug notification bec
These were the commits applied in the test kernel posted in comment #13.
The SHA1s are different because this is the tree used to build my test
kernel.
e8aae57 Drivers: hv: vmbus: Fix a Host signaling bug
5d9beeb Drivers: hv: vmbus: Fix a siganlling host signalling issue
4763d20 Drivers: hv: vmbus
>From the ubuntu-trusty git repository:
$ git --format=oneline Ubuntu-3.13.0-77.121.. -- drivers/hv
04d1fd1012796e714f3b291fc0487e45d2fbd9ba Drivers: hv: vmbus: Fix a Host
signaling bug
952f5d0a5b0f3b032902537a1aeafdee75ac69a6 Drivers: hv: vmbus: Fix a siganlling
host signalling issue
c402db490
Do *not* merge these changes.
We're seeing a large network performance drop with this kernel, so we need to
further investigate.
What other netvsc related patches have been included in the proposed kernel?
Compared to the test kernel from comment #13.
The proposed kernel build tag is 3.13.0-78.1
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
To manage
** No longer affects: linux (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
To manage notifications about this bug go to:
h
Hi Joe,
This kernel looks good now, I was able to run the net perf against it and also
the network tests and it looks good.
Please proceed with the SRU for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I built a Trusty test kernel with commit 8599846 and all the necessary
prereqs.
Please test the following kernel and let us know your results. If we
can receive positive test feedback by January 29th, we can proceed to
submit the patches for kernel SRU review in an attempt to make the
upcoming ke
Some of the prereqs needed for Trusty and 12.04.5 would come in via bug
1454892. We are just waiting for testing on that bug. However, I can
still build a Trusty test kernel with the assumption that the prereqs
will come in via bug 1454892.
--
You received this bug notification because you are
The patch is in the mainline tree as the following commit:
8599846 - Drivers: hv: vmbus: Fix a Host signaling bug
However, it has not been tagged in an official release upstream as of
yet. It was cc'd to stable, so it will make it's way into the stable
kernels through the usual stable update pro
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux-lts-trusty (Ubuntu)
Status: New => In Progress
** Changed in: linux-lts-trusty (Ubuntu)
Importance: Undecided => High
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importance: Un
** Also affects: linux-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-lts-trusty (Ubuntu Vivid)
** No longer affects: linux-lts-trusty (Ubuntu Wily)
** No longer affects: linux-lts-trusty (Ubuntu Xenial)
--
You received this bug notification because
We have customers encountering this issue on 12.04.5. I have advised
them to be sure they are running lts-trusty. Is there an outlook on when
this fix may be available for that release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Also, it looks like it's the V1 version of the patch in Vivid. However,
it will be replace by V2 when it comes down from stable as an update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Tit
Indeed. Sorry, I should have recognized it. Too many parallel threads of
effort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
To manage
The patch is actually already in Vivid due to bug 1508706 .
** Changed in: linux (Ubuntu Vivid)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[
Ah, we hadn't started Xenial testing yet. Give me a little more time to
spin that up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
To m
Dear Joshua,
I built a Xenial test kernel with the V2 patch.
Please test the kernel and let us know your results. If we can receive
positive test feedback by December 18, we can proceed to submit the
patches for kernel SRU review in an attempt to make the upcoming kernel
SRU cycle starting on De
Yeah, at the time I submitted we had determined that the first patch
would work, but that there might be dialogue in the upstreaming. The V2
submission is okay with us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
It looks like there was a V2 to the patch mentioned in the description:
https://lkml.org/lkml/2015/11/19/795
I'll build the test kernels using the V2 patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Wily)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/151989
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: High
Sta
No longs required, this is a request to pick up an upstream submission.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Titl
49 matches
Mail list logo
