This bug was fixed in the package linux - 2.6.32-38.83
---
linux (2.6.32-38.83) lucid-proposed; urgency=low
[Herton R. Krzesinski]
* Release Tracking Bug
- LP: #911405
[ Upstream Kernel Changes ]
* Revert "clockevents: Set noop handler in clockevents_exchange_device()"
Verified. Tag updated to verification-done-lucid
** Tags removed: verification-needed-lucid
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unabl
We need to get this kernel tested so that it can be included on the next
Lucid point release DVD. Please test if you can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start
** Tags removed: kernel-key needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifications about
This bug is awaiting verification that the kernel in -proposed solves
the problem (2.6.32-38.83). Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-lucid' to 'verification-done-lucid'.
If verification is not done by one week
I changed by error the fix from comitted to released ... Sorry !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifi
** Changed in: linux (Ubuntu Lucid)
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.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notificati
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifications abou
** Patch added: "(V2) UBUNTU: SAUCE: netns: Add quota for number of NET_NS
instances."
https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/790863/+attachment/2639885/+files/0001-UBUNTU-SAUCE-netns-Add-quota-for-number-of-NET_NS-in.patch
--
You received this bug notification because yo
The final patch has a non-zero initial value for max_netns_count, plus
it prints a warning once when the number of allocated network name
spaces exceeds max_netns_count.
** Changed in: linux (Ubuntu Lucid)
Status: In Progress => Fix Committed
--
You received this bug notification because
So far so good. My container is running fine along with everything
else. I'll keep running this build and report if I see any issues, but
I think it's good. Let me know if there's anything else I need to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Tim,
Thanks for getting a test version out! I've been swamped the last few
weeks but I can test it out this weekend and post my results. I also
admit I thought this was a VSFTP patch (from Jamie's note) when I
skimmed it the first time, not a new kernel. Oops :)
--
You received this bug notif
>> Where have all my testers gone? This patch isn't going in without some
>> feedback.
Hmm.. Half a year... To Debian I guess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable
Ok, my containers do start up again and seem to behave ok. I'm happy to
test this for a more extended period of time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc
Where have all my testers gone? This patch isn't going in without some
feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
vsftpd (2.2.2-3ubuntu6.3) lucid-security; urgency=low
* SECURITY UPDATE: remote DoS via network namespaces
- debian/patches/12-CVE-2011-2189.patch: only use network namespaces
on 2.6.36 and higher kernels
- patch based on Debian's patch
- CVE-2011-2189
** Changed in: vsftpd (
This parameter must be set before LXC containers starts? It can be
setted via sysctl.conf?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2
Don't forget to do something like:
echo 4096 | sudo tee /proc/sys/net/core/netns_max
before attempting to fork with CLONE_NEWNET.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable
Test kernels at http://kernel.ubuntu.com/~rtg/790863.1
Corresponding sources at git://kernel.ubuntu.com/rtg/ubuntu-lucid.git
config-ns-790863, tag 790863.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: linux (Ubuntu Lucid)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lucid)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Tetsuo - I'll forward your patch for review on the Ubuntu kernel team
mailling list. If accepted, then I'm OK with restoring CONFIG_NET_NS.
The most common OOM cause (vsftpd) will have been ameliorated with the
application of the patch for CVE-2011-2189 , and your patch should
prohibit fatal OOM co
** Changed in: vsftpd (Ubuntu Lucid)
Status: Triaged => 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/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To m
vsftpd needs this patch from Debian's 10-remote-dos.patch 2.3.4-1.
vsftpd in precise already has this.
** Also affects: vsftpd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: vsftpd (Ubuntu Lu
I posted this topic to netdev ML.
http://www.spinics.net/lists/netdev/msg180263.html
According to Eric W. Biederman, Debian has tweaked
vsftpd to not use network namespaces on 2.6.32.
By combining tweaking vsftpd and this patch, I think
we might be able to reenable CONFIG_NET_NS.
What do you thi
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifications about this bug go to:
https://bugs.l
Does vsftpd retry without CLONE_NEWNET if attempt with CLONE_NEWNET failed?
If yes, reenabling CONFIG_NET_NS with this (untested) patch might help.
Even if no, reenabling CONFIG_NET_NS with this patch with
adequate initial value (e.g. 64) assigned to max_netns_count might help.
** Patch added: "u
Stefan,
I have to agree with Henrik regarding the logic seeming backwards, but I
suppose that's because the "solution" hurt me.
Did Serge Hallyn ever take a look at it? I got the impression someone
was going to try to backport part of the fix, but it sounds like that
path was rejected.
Regardin
Earlier this year the LTS-backport kernels didn't have a valid header
package, thus breaking dkms-based kernel modules, see bug #824080 . It
took over a month to fix that, not giving much of an impression that
LTS-backport kernels are really supported.
--
You received this bug notification becaus
Stefan,
I'd like to use your argumentation, but in reverse.
Disabling NET_NS is what is _causing_ a regression. Quick setup with
slow tear-down is a _current_ behaviour of the LTS release. If the users
of this LTS release wants to have another behaviour with vsftpd, then
_they_ should seek to use
The reasoning behind that can be found in bug #720095. Basically vsftp
was found to be one case of using NET_NS and the way network namespaces
work in 2.6.32 they can be quickly created but take an awful long time
on teardown. So a quick sequence of cloning a process with a new network
namespace an
I've been pinned at 2.6.32-31 since this began. I experimented with the
various backports but each caused more problems than it solved.
Bad answer Canonical. Sigh. At least 12.04 is only 6 months away, plus
3 months to stabilize.
By the way, where exactly was this decision documented? I'd lik
Serge Hallyn wrote:
> @Joseph,
>
> re-enabling CONFIG_NET_NS has been rejected. As I understand it,
> because backport kernels are supported on LTS releases, that is seen as
> the right path for those requiring network namespaces.
At least one other person on this ticket asserted that the backpo
@Joseph,
re-enabling CONFIG_NET_NS has been rejected. As I understand it,
because backport kernels are supported on LTS releases, that is seen as
the right path for those requiring network namespaces.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifications about this bug go to:
https://b
We were looking into using Ubuntu 10.04 + LXC for our SAAS services, but
because of this bug are now looking at Debian Squeeze. Come on
Canonical, some statement from a Ubuntu dev would go a long way here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
The Maverick and Natty kernels also "work" for some people. However,
depending on the rest of your configuration, installing backported
kernels can break other things. Definitely not the ideal answer. The
fact that Maverick backport was broken for a month is an example.
I'd complain about how l
Whilst I find the substitution of a possible regression for a definite
regression a bit of a bizarre choice on Canonical's part (especially as
it's entirely possible to disable the possible regression with a compile
flag to the package in question), a workaround that should work is to
install the n
Is there a way to find out if the existance of this bug report leads to
anything? Has it been noticed, considered, discussed, rejected?
Anything? If its not being done, someone should close this bug and
explain it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment removed: ".etc.asound.conf.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+attachment/2149515/+files/.etc.asound.conf.txt
** Attachment removed: "AlsaDevices.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+attachment/2149516/+files/AlsaDevi
Also, the 2.6.35 backport is broken at the moment, see bug #847828.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage not
Using 2.6.38 backport is NOT a workaround. See #843892.
The only way to fix this is reverting #720095 and fixing that in
userspace (i.e. in vsftp)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
I still can't lxc-start in 2.6.32-33
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage notifications about this bug go to
Reading through the discussion on the kernel list, I think the flawed
logic in this decision was: "Let's avoid a POTENTIAL regression due to
lots of lines of code changed by introducing a DEFINITE regression". I
think we've all been there. Still, not a great call.
--
You received this bug notif
Holy shit! How can you (Canonical) do this with LTS?!?!? What's a crap?
@Ulli Horlacher thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc containe
Seriously guys... What the heck were you thinking? The whole reason
people choose to run an LTS is to avoid this kind of thing.
I can downgrade for now, but please fix soon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I have the same problem. A workaround for me was:
apt-get install linux-image-server-lts-backport-maverick
Nevertheless the default linux kernel should not break other packages on
a LTS system!
My server is a virtualization host for many LXC VMs and after a
"aptitude upgrade" I was not able any
I guess you referr to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720095 instead of
https://bugs.launchpad.net/bugs/788602.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unab
Thanks very much for reporting this bug.
This has unfortunately been caused by the resolution to bug 788602. I'm
not sure how feasible it is to do a more complete solution which fixes
bug 788602 with CONFIG_NET_NS enabled, but it seems important to me to
find it.
If noone else wants to tackle th
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
50 matches
Mail list logo
