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()
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To
** Changed in: linux (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after
I changed by error the fix from comitted to released ... Sorry !
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
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
** Tags removed: kernel-key needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage
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
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
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
Server Team, which is subscribed to vsftpd in Ubuntu.
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
** 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 you
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
Server
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
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after
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
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
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
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
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
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
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
Server Team, which is subscribed to vsftpd in Ubuntu.
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
Server Team, which is subscribed to vsftpd in Ubuntu.
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
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container
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
** Changed in: vsftpd (Ubuntu Lucid)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update
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
** 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
Server Team, which is subscribed to vsftpd in Ubuntu.
24 matches
Mail list logo
