I think the debian patch had been applied in releases after Hardy. But
the daemon only resets the oom_adj value that it was originally called
with. So in Jaunty a DHCP restart script which had the oob_adj value of
-17 itself caused the same effect. See bug report #390556.
I have not checked lucid
OK, I've debugged a bit into the lucid upstart scripts:
First, I can confirm the regression.
The oom_adj patch is still in place, which is the good news. The bad
news is, that the problem is now caused by the upstart script
/etc/init/ssh.conf
Apparently the author didn't understand how the
OK, I've debugged a bit into the lucid upstart scripts:
First, I can confirm the regression.
The oom_adj patch is still in place, which is the good news. The bad
news is, that the problem is now caused by the upstart script
/etc/init/ssh.conf
Apparently the author didn't understand how the
I think the debian patch had been applied in releases after Hardy. But
the daemon only resets the oom_adj value that it was originally called
with. So in Jaunty a DHCP restart script which had the oob_adj value of
-17 itself caused the same effect. See bug report #390556.
I have not checked lucid
*** This bug is a duplicate of bug 460857 ***
https://bugs.launchpad.net/bugs/460857
** This bug has been marked a duplicate of bug 460857
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
--
[karmic] usbserial regression with MessPC Environment Sensors
I just downloaded a vanilla 2.6.31.6 kernel from kernel.org and verified
that the device works with that version.
--
[karmic] usbserial regression with MessPC Environment Sensors
https://bugs.launchpad.net/bugs/474180
You received this bug notification because you are a member of Ubuntu
Bugs,
It seems the problem is more related to the ftdi_sio module than to
usbserial. A colleague told be, that he is able to communicate on karmic
over a serial line using a USB-serial converter with a different
chipset.
--
[karmic] usbserial regression with MessPC Environment Sensors
Public bug reported:
I'm using a MessPC Environment Sensor which connects via USB emulating a
serial device. The sensor data is sent as text to the serial port.
lsusb reports the device as
Bus 005 Device 003: ID 0403:6001 Future Technology Devices
International, Ltd FT232 USB-Serial (UART) IC
** Attachment added: dmesg.log
http://launchpadlibrarian.net/35094222/dmesg.log
--
[karmic] usbserial regression with MessPC Environment Sensors
https://bugs.launchpad.net/bugs/474180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci-vnvn.log
http://launchpadlibrarian.net/35094232/lspci-vnvn.log
--
[karmic] usbserial regression with MessPC Environment Sensors
https://bugs.launchpad.net/bugs/474180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: uname-a.log
http://launchpadlibrarian.net/35094250/uname-a.log
--
[karmic] usbserial regression with MessPC Environment Sensors
https://bugs.launchpad.net/bugs/474180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: version.log
http://launchpadlibrarian.net/35094256/version.log
--
[karmic] usbserial regression with MessPC Environment Sensors
https://bugs.launchpad.net/bugs/474180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have done some more investigations on the issue. I found that the
original debian patch still exists in sshd.
The problem is caused by the DHCP initialization of my network interface
during startup. The DHCP request is processed in the background while
the OpenSSH initialization script (and
I have done some more investigations on the issue. I found that the
original debian patch still exists in sshd.
The problem is caused by the DHCP initialization of my network interface
during startup. The DHCP request is processed in the background while
the OpenSSH initialization script (and
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: openssh-server
All child processes of openssh-server inherit the oom_adj value of -17
which makes the unkillable in low memory situation. Any user logged into
the machine via ssh can cause a
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: openssh-server
All child processes of openssh-server inherit the oom_adj value of -17
which makes the unkillable in low memory situation. Any user logged into
the machine via ssh can cause a
** This bug has been flagged as a security issue
--
hardy: openssh-server oom_adj can lead to denial of service
https://bugs.launchpad.net/bugs/293000
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
** This bug has been flagged as a security issue
--
hardy: openssh-server oom_adj can lead to denial of service
https://bugs.launchpad.net/bugs/293000
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #480020
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480020
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480020
Importance: Unknown
Status: Unknown
--
hardy: openssh-server oom_adj can lead to denial of
** Bug watch added: Debian Bug tracker #480020
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480020
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480020
Importance: Unknown
Status: Unknown
--
hardy: openssh-server oom_adj can lead to denial of
As work-around I would suggest setting SSHD_OOM_ADJUST to 0 in
/etc/default/ssh. This allows the killing of ssh and child processes by
the OOM killer again.
--
hardy: openssh-server oom_adj can lead to denial of service
https://bugs.launchpad.net/bugs/293000
You received this bug notification
Public bug reported:
Binary package hint: openssh-server
The ssh init script sets the /proc/$PID/oom_adj value to -17 to avoid
being killed by the OOM killer in low memory situations. Unfortunately
all child processes of sshd inherit this setting.
So any user with ssh access can easily launch a
As work-around I would suggest setting SSHD_OOM_ADJUST to 0 in
/etc/default/ssh. This allows the killing of ssh and child processes by
the OOM killer again.
--
hardy: openssh-server oom_adj can lead to denial of service
https://bugs.launchpad.net/bugs/293000
You received this bug notification
Public bug reported:
Binary package hint: openssh-server
The ssh init script sets the /proc/$PID/oom_adj value to -17 to avoid
being killed by the OOM killer in low memory situations. Unfortunately
all child processes of sshd inherit this setting.
So any user with ssh access can easily launch a
24 matches
Mail list logo
