Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
After applying the latest kernel package, all of my VMs started just fine as well. All i386. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100827181300.gd1...@mostlylinux.ca
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
On Fri, Aug 27, 2010 at 12:13:00PM -0600, Scott Barker wrote: After applying the latest kernel package, all of my VMs started just fine as well. All i386. Well, this is good news I suppose.. personally I'd rather have something 100% reproducing than intermittently failing :( -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100827220255.gd23...@lackof.org
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
On Mon, 23 Aug 2010 21:56:17 +0200 (CEST), Tomas Pospisek t...@sourcepole.ch wrote: On a different note: the last update to the most recent DSA kernels [2] went completely smoothly - that is all vservers restarted without a hickup. Makes me wonder if that was caused by a change in the 2.6.26-24lenny1 kernel? We'll see at the next upgrade. I noticed this too, last DSA went perfectly. Before I would get at least one guest on each machine that would exhibit this problem, this time I got none. However, I *did* get one on my amd64 box. All the others were i386 micah pgpNLGDLqcRcL.pgp Description: PGP signature
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
Thanks, I tested that [1], and it does seem to work. Hopefully this bug is being worked on by someone upstream. AFAIK it's not worked on upstream and very probably fixed in newer vserver releases. I asked on vserver's IRC channel and was told in quite clear words something along the lines of we don't care about ancient preferred fecal word of your choice kernels that Debian ships. You may want to re-inquiry @vserver. On a different note: the last update to the most recent DSA kernels [2] went completely smoothly - that is all vservers restarted without a hickup. Makes me wonder if that was caused by a change in the 2.6.26-24lenny1 kernel? We'll see at the next upgrade. I'm Cc:ing this to all bug report participants, I hope you all don't mind. *t [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570382#65 [2] http://www.debian.org/security/2010/dsa-2094 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1008232142430.6...@tpo-laptop
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
Thanks, I tested that, and it does seem to work. Hopefully this bug is being worked on by someone upstream. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100806165459.gr2...@mostlylinux.ca
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
As a workaround instead of stopping and restarting you might want to use vmount
on the affected vservers:
# vmount foo -- -a
You will get some error messages for all already correctly mounted filesystems,
but you can enter your vserver again.
Running
###
for vserver in `vserver-stat | tail -n +2 | awk '{print $8}'`; do
vmount $vserver -- -a
done
###
will fix all your vservers - broken or not (and give some more error messages).
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c503e11.1050...@dimdi.de
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
I am experiencing this problem as well. I have read through this bug report, and the most recent entry suggesting purging util-vserver does not make any sense. If you purge that package, you lose the utilities you need to start the virtual servers. If you re-install it from lenny sources, the problem persists. Just wondering if anyone has a solution for this yet, short of stopping and restarting all affected vservers after reboot. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723203102.gm1...@mostlylinux.ca
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory]
I can confirm that this manifested with the 2.6.26-21lenny3 security
upgrade in Feburary (DSA-1996). It seems like what happens is when the
system boots, it runs the /etc/init.d/util-vserver script, which
attempts to automatically start all the guests which have the 'default'
mark. Sometimes things are fine, sometimes some guests give the 'vlogin:
openpty()' error when you try to 'vserver guest enter' them. You also
will get an error trying to ssh to the guest, or anything else related
to pty.
Its not reliable which guests get this problem, sometimes its none of
them, sometimes its all of them. When you restart the machine, the only
thing you can do is attempt to enter each guest, and those which give
the openpty() problem, you need to issue a 'vserver guest stop;
vserver guest start' to get them back. This resolves it every time.
I looked to see if the guest has /dev/pts and /dev/ptmx when first
trying to enter it by doing:
vnamespace -e guest ls -l /vservers/guest/dev/{ptmx,pts}
this shows me that on an affected guests /dev/pts is empty, but has a
'0' on those that do not have a problem. The /dev/ptmx exists like
normal:
crw-rw-rw- 1 root root 5, 2 2006-11-10 16:07 /vservers/test/dev/ptmx
So the guests that have this problem have no /dev/pts/0, they have a
/dev/pts, just nothing in it. Typically /dev/pts/0 doesn't get created
until you do 'vserver guest enter' or use ssh to enter, or something
else allocates a tty. It seems like a 'vserver guest enter' doesn't
seem to be able to create it.
Looking at the /proc/mounts in the guest's namespace, with the
folliowing:
vnamespace -e guest cat /proc/mounts
I see this:
total 0
rootfs / rootfs rw 0 0
/dev/md0 / ext3 rw,errors=remount-ro,data=ordered 0 0
udev /dev tmpfs rw,size=10240k,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,gid=5,mode=620 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0
/dev/md1 /usr ext3 rw,errors=continue,data=ordered 0 0
/dev/md2 /var ext3 rw,errors=continue,data=ordered 0 0
/dev/loop3 /vservers ext3 rw,errors=continue,data=ordered 0 0
none /vservers/test/proc proc rw,nodev 0 0
/dev/loop3 /vservers/test ext3 rw,errors=continue,data=ordered 0 0
If I look at the way the initscript does the starting, I see that it is
invoked in the following way:
/usr/lib/util-vserver/vserver-wrapper start /dev/tty8 /dev/tty8 2/dev/tty8
Looking at /dev/tty8, i see a segfault in
/usr/lib/util-vserver/vserver.functions line 907. This is using the
lenny version of the user-space utilities (0.30.216~r2772-6), and line
907 is the opening curly brace as follows:
function _mountVserverInternal
{
Micah
pgpT4Z1zwWqgN.pgp
Description: PGP signature
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
Hi, Same problem here (Lenny) since we updated our linux-image-2.6.26-vserver-86 kernel to 2.6.26-21lenny3 : when the host server is rebooted, the guest vservers are started but can't be entered (or accessed by SSH), with the same error message : vlogin: openpty(): No such file or directory (or PTY allocation request failed on channel 0 with SSH). However, the problem disappeared if the guest is stopped and restarted using vserver command : # vserver foo stop # vserver foo start # vserver foo enter foo Tomas, in your case and IMHO, adding the devices didn't cure the problem, but restarting the vserver did (until the host server is restarted, of course). -- Florian Dufour INRIA - Direction des Systèmes d'Information Tél : 04 76 61 52 39 - Mél : florian.duf...@inria.fr -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9181d4.90...@inria.fr
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
Package: linux-2.6 Version: 2.6.26-21lenny3 Severity: normal After upgrading the kernel from linux-image-2.6.26-2-vserver-686 2.6.26-21 to 2.6.26-21lenny3 and rebooting we could not log into the vservers any more and got the mentioned error instead: # vserver foo enter vlogin: openpty(): No such file or directory # since we had some instance where the procedure had worked we compared /dev and added the devices that were not on the instances where it did not work and restarted the vserver instances. Now everything seemed to behave as expected. We're not sure whether adding the devices cured the problem or whether it was restarting the vserver instances or both. We add the following devices under /var/lib/vserver/foo lrwxrwxrwx 1 root root 13 fd - /proc/self/fd lrwxrwxrwx 1 root root4 stderr - fd/2 lrwxrwxrwx 1 root root4 stdin - fd/0 lrwxrwxrwx 1 root root4 stdout - fd/1 Additionally /var/lib/vserver/foo/dev/[u]random had different permissions (only owner had write permussion). So we added group and other write permissions: # chmod og+w /var/lib/vserver/foo/dev/*random crw-rw-rw- 1 root root 1, 8 random crw-rw-rw- 1 root root 1, 9 urandom *t -- Package-specific info: ** Version: Linux version 2.6.26-2-vserver-686 (Debian 2.6.26-21lenny3) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Feb 10 10:39:33 UTC 2010 ** Command line: root=/dev/sda6 ro console=tty0 ** Not tainted ** Kernel log: [4.249273] scsi: waiting for bus probes to complete ... [5.596939] scsi[0]: scanning scsi channel 1 [virtual] for logical drives [5.596939] scsi 0:1:0:0: Direct-Access MegaRAID LD 0 RAID1 69G 521S PQ: 0 ANSI: 2 [5.632088] scsi 0:0:6:0: Attached scsi generic sg0 type 3 [5.632195] scsi 0:1:0:0: Attached scsi generic sg1 type 0 [5.636929] Driver 'sd' needs updating - please use bus_type methods [5.636929] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [5.636929] sd 0:1:0:0: [sda] Write Protect is off [5.636929] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [5.636929] sd 0:1:0:0: [sda] Asking for cache data failed [5.636929] sd 0:1:0:0: [sda] Assuming drive cache: write through [5.636929] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [5.636929] sd 0:1:0:0: [sda] Write Protect is off [5.636929] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [5.636929] sd 0:1:0:0: [sda] Asking for cache data failed [5.636929] sd 0:1:0:0: [sda] Assuming drive cache: write through [5.636929] sda: sda1 sda2 sda5 sda6 sda7 sda8 [5.654206] sd 0:1:0:0: [sda] Attached SCSI disk [5.908237] device-mapper: uevent: version 1.0.3 [5.908681] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [5.931368] PM: Starting manual resume from disk [5.956270] kjournald starting. Commit interval 5 seconds [5.956270] EXT3-fs: mounted filesystem with ordered data mode. [7.046533] udevd version 125 started [7.403059] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [7.651747] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [7.667746] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [7.835942] EDAC MC: Ver: 2.1.0 Feb 10 2010 [7.839944] Contact your BIOS vendor to see if the E752x error registers can be safely un-hidden [7.891943] input: Power Button (FF) as /class/input/input0 [7.916333] ACPI: Power Button (FF) [PWRF] [8.555946] ACPI Exception (video-1631): AE_NOT_FOUND, Evaluating _DOD [20080321] [8.555946] input: Video Bus as /class/input/input1 [8.575975] ACPI: Video Device [EVGA] (multi-head: no rom: yes post: no) [8.581115] input: PC Speaker as /class/input/input2 [8.719815] usb-storage: device scan complete [8.727946] scsi 1:0:0:0: Direct-Access Seagate FreeAgent102C PQ: 0 ANSI: 4 [8.727946] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) [8.731946] sd 1:0:0:0: [sdb] Write Protect is off [8.731946] sd 1:0:0:0: [sdb] Mode Sense: 1c 00 00 00 [8.731946] sd 1:0:0:0: [sdb] Assuming drive cache: write through [8.731946] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) [8.735945] sd 1:0:0:0: [sdb] Write Protect is off [8.735945] sd 1:0:0:0: [sdb] Mode Sense: 1c 00 00 00 [8.735945] sd 1:0:0:0: [sdb] Assuming drive cache: write through [8.735945] sdb: sdb1 [8.735945] sd 1:0:0:0: [sdb] Attached SCSI disk [8.735945] sd 1:0:0:0: Attached scsi generic sg2 type 0 [8.885172] intel_rng: FWH not detected [8.971590] Error: Driver 'pcspkr' is already registered, aborting... [9.779221] Adding 3903752k swap on /dev/sda5. Priority:-1 extents:1 across:3903752k [ 50.071401] EXT3 FS on sda6, internal journal [ 50.317679] ipmi message handler version 39.2 [ 50.320128] IPMI System Interface driver. [ 50.320194] ipmi_si: Trying
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory
I experienced similar behaviour, however I saw different results when using vserver foo start and when using /etc/init.d/util-vserver start, with only the latter exhibiting the problem. The problem appears to be caused by secure-mount segfaulting (as you can see in your logs) when mounting /dev/pts. Changing the vserver's fstab file to include the options rw,noexec,nosuid for the devpts entry seems to fix the problem. Here's the entry from my fstab in case it helps anybody: none/dev/ptsdevpts rw,noexec,nosuid,gid=5,mode=620 0 0 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100218145733.ga20...@hercules.pureserver.info
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory]
Unfortunately it seems my fix does not work. The problem is not
consistently reproducible, hence my belief I had fixed it.
I tried backporting the util-vserver package from squeeze
(0.30.216-pre2864-1) and had exactly the same problem.
The problem appears to be caused by failure of old_mmap() in
secure-mount. Here is the strace output of a failed secure-mount:
execve(/usr/lib/util-vserver/secure-mount,
[/usr/lib/util-vserver/secure-mou..., -a, --chroot, --fstab,
/etc/vservers/XXX/fstab, --rootfs, no], [/* 31 vars */]) = 0
open(., O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 3
open(/, O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 4
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
open(/etc/vservers/XXX/fstab, O_RDONLY|O_LARGEFILE) = 5
_llseek(5, 0, [393], SEEK_END) = 0
_llseek(5, 0, [0], SEEK_SET)= 0
read(5, none\t/proc\t\tproc\tdefaults\t\t0 0\nno..., 394) = 393
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0xb28408086038) = 0x40001000
chdir(/) = 0
fchdir(3) = 0
chroot(.) = 0
chdir(/proc) = 0
open(., O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 6
fchdir(4) = 0
chroot(.) = 0
fchdir(6) = 0
close(6)= 0
mount(none, ., proc, MS_NODEV, ) = 0
fchdir(3) = 0
chroot(.) = 0
open(/etc/mtab, O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0644) = 6
fcntl(6, F_SETLKW, {type=F_WRLCK, whence=SEEK_CUR, start=0, len=0}) = 0
write(6, none..., 4) = 4
write(6, ..., 1) = 1
write(6, /proc..., 5) = 5
write(6, ..., 1) = 1
write(6, proc..., 4) = 4
write(6, ..., 1) = 1
write(6, defaults..., 8) = 8
write(6, 0 0\n..., 5)= 5
close(6)= 0
fchdir(4) = 0
chroot(.) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0xb28408086038) = -1 ENOMEM (Cannot allocate memory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
I have also tried using ulimit to turn off any potential limits which
might be causing this but without success.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100218172405.ga6...@hercules.pureserver.info
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory]
(I'm including Micah Anderson, maintainer of util-vserver in the Cc: in the hope that maybe the symptoms mentioned here may ring a bell with him. I hope you don't mind Micah.) Dan Gardner wrote on Feb 18 : I experienced similar behaviour, however I saw different results when using vserver foo start and when using /etc/init.d/util-vserver start, with only the latter exhibiting the problem. The problem appears to be caused by secure-mount segfaulting (as you can see in your logs) when mounting /dev/pts. Changing the vserver's fstab file to include the options rw,noexec,nosuid for the devpts entry seems to fix the problem. Here's the entry from my fstab in case it helps anybody: none/dev/ptsdevpts rw,noexec,nosuid,gid=5,mode=620 0 0 I checked the kernel's changelog and there doesn't seem to be no mention of changing anything related to vserver (there is a xen change though - no idea if it touches common infrastructure). However the util-vserver changelog mentions as of release 0.30.216~r2842-1 (which is in sid only) the removal of several secure-mount /dev related patches [1]. Since I am on lenny I still have the older 0.30.216~r2772-6 release of util-vserver. Don't know if the problems we see have anything to do with the code touched by those patches. *t [1] http://packages.debian.org/changelogs/pool/main/u/util-vserver/util-vserver_0.30.216-pre2864-1/changelog#versionversion0.30.216_r2842-1 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1002181744080.6...@tpo-laptop
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory]
On Thu, Feb 18, 2010 at 05:24:05PM +, Dan Gardner wrote: Unfortunately it seems my fix does not work. The problem is not consistently reproducible, hence my belief I had fixed it. I tried backporting the util-vserver package from squeeze (0.30.216-pre2864-1) and had exactly the same problem. The problem appears to be caused by failure of old_mmap() in secure-mount. Here is the strace output of a failed secure-mount: did you ask the vserver guys on their irc channel for support on aboves? afair they are quite responsive there. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100218175412.gd12...@baikonur.stro.at
Bug#570382: after upgrade: vlogin: openpty(): No such file or directory]
On Thu, 18 Feb 2010, Dan Gardner wrote:
The problem appears to be caused by failure of old_mmap() in
secure-mount. Here is the strace output of a failed secure-mount:
execve(/usr/lib/util-vserver/secure-mount,
[/usr/lib/util-vserver/secure-mou..., -a, --chroot, --fstab,
/etc/vservers/XXX/fstab, --rootfs, no], [/* 31 vars */]) = 0
open(., O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 3
open(/, O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 4
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
open(/etc/vservers/XXX/fstab, O_RDONLY|O_LARGEFILE) = 5
_llseek(5, 0, [393], SEEK_END) = 0
_llseek(5, 0, [0], SEEK_SET)= 0
read(5, none\t/proc\t\tproc\tdefaults\t\t0 0\nno..., 394) = 393
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0xb28408086038) = 0x40001000
chdir(/) = 0
fchdir(3) = 0
chroot(.) = 0
chdir(/proc) = 0
open(., O_RDONLY|O_LARGEFILE|O_DIRECTORY) = 6
fchdir(4) = 0
chroot(.) = 0
fchdir(6) = 0
close(6)= 0
mount(none, ., proc, MS_NODEV, ) = 0
fchdir(3) = 0
chroot(.) = 0
open(/etc/mtab, O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0644) = 6
fcntl(6, F_SETLKW, {type=F_WRLCK, whence=SEEK_CUR, start=0, len=0}) = 0
write(6, none..., 4) = 4
write(6, ..., 1) = 1
write(6, /proc..., 5) = 5
write(6, ..., 1) = 1
write(6, proc..., 4) = 4
write(6, ..., 1) = 1
write(6, defaults..., 8) = 8
write(6, 0 0\n..., 5)= 5
close(6)= 0
fchdir(4) = 0
chroot(.) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0xb28408086038) = -1 ENOMEM (Cannot allocate memory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
The last parameter to mmap should be the offset where the caller wants
data to be initialized (AFAIU). So what's that absurd value
(0xb28408086038) there? That's way out in the stratosphere. Well
whatever, I don't want to pretend I understand anything about the mmap
syscall interface.
However, 2.6.26-21lenny1 messed with mmap. From Debian's changelog:
linux-2.6 (2.6.26-21lenny1) stable-security; urgency=high
[ dann frazier ]
...
* Fix several issues with mmap/mremap (CVE-2010-0291)
...
-- dann frazier da...@debian.org Fri, 29 Jan 2010 17:20:16 -0700
CVE-2010-0291 [1] references this discussion [2] which discusses tricky
implications of the patch on virtualisation [3] - which is exactly
the place where we are standing: vserver. So I think I can see stuff
peeling off the space shuttle however don't know how to fix it. Contacting
NASA at vserver-ML additionally to the Debian engineers sounds like a good
idea.
*t
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0291
[2] http://marc.info/?l=linux-archm=126004438008670w=2
[3] http://marc.info/?l=linux-archm=126012243613146w=2
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/alpine.deb.2.00.1002182147160.10...@tpo-laptop
