[Bug 1554227] Re: DHCP unicast requests are not responded to
** Changed in: nova Status: New => Confirmed ** Changed in: nova (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1554227 Title: DHCP unicast requests are not responded to To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1554227/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554540] [NEW] DHCP unicast requests are not responding
Public bug reported: Issue: We run nova-network in VLAN+multi_host mode on Kilo and notice that only one dnsmasq process (either the oldest or newest) on the hypervisor responds to unicast BOOTPREQUESTS. dhclient on VMs will retry until it eventually gives up and broadcasts the request, which is then responded to. Depending on the timing of the DHCP broadcast request, VMs can briefly lose connectivity as they attempt rebinding. According to http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12, it seems that passing "--interface" argument, in addition to "--bind- interfaces" is necessary for dnsmasq to work correctly in VLAN mode. Reproduce steps: 1. Create two tenants 2. Create a VM under each tenant, forcing the VMs to run on a single hypervisor. I tested with a vanilla Ubuntu cloud image, but any other image that uses dhclient should also work. 3. On the hypervisor, run dhcpdump -i for each tenant's bridge interface. On at least one of them, you should see unicast BOOTPREQUEST with no corresponding BOOTPREPLY. dnsmasq will reply when the request eventually hits 255.255.255.255. Nova/Openstack/dnsmasq versions: ii nova-api 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - API frontend ii nova-common 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - common files ii nova-compute 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node base ii nova-compute-libvirt 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node libvirt support ii nova-compute-qemu 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node (QEmu) ii nova-network 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - Network manager ii nova-novncproxy 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - NoVNC proxy ii python-nova 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute Python libraries ii python-nova-adminclient 0.1.8-0ubuntu2 amd64 client for administering Openstack Nova ii python-novaclient 1:2.22.0-0ubuntu2~cloud0 all client library for OpenStack Compute API ii dnsmasq-base 2.68-1ubuntu0.1 amd64 Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-utils 2.68-1ubuntu0.1 amd64 Utilities for manipulating DHCP lease ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1554540 Title: DHCP unicast requests are not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1554540/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554540] Re: DHCP unicast requests are not responding
Upstream bug for OpenStack Compute (nova): https://bugs.launchpad.net/nova/+bug/1554227 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1554540 Title: DHCP unicast requests are not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1554540/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] Re: openipmi package compile without SSL
** Changed in: openipmi (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] Re: openipmi package compile without SSL
** Changed in: openipmi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] Re: openipmi package compile without SSL
Debian package for unstable # filename: openipmi-2.0.21/debian/changelog openipmi (2.0.21-1) unstable; urgency=medium ... * enabled openssl. closes: #775847 ... -- Noël Köthe Thu, 25 Feb 2016 12:06:21 +0100 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] Re: openipmi package compile without SSL
Following a discussion with the Debian distribution maintenance software "Noël Köthe ". SSL support has been enabled by debian upstream maintainer and has now landed in unstable in openipmi-2.0.21. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] Re: openipmi package compile without SSL
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546735] [NEW] openipmi package compile without SSL
Public bug reported: It has been brought to my attention by the community that package "openipmi" is build without openssl. Taken from "openipmi-2.0.18" source code: -- filename:debian/rules --- 23 config.status: configure 24 dh_testdir 25 dh_autotools-dev_updateconfig 26 # Add here commands to configure the package. 27 CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) \ 28 --build=$(DEB_BUILD_GNU_TYPE) \ 29 --prefix=/usr \ ==> 30 --without-openssl \ 31 --mandir=\$${prefix}/share/man \ 32 --infodir=\$${prefix}/share/info \ 33 --disable-rpath -- This prevent some third applications to work as expected such as Zabbix[1] There is debian bug[2] filed on 20 Jan 2015 16:57:01 UTC [1] - https://support.zabbix.com/browse/ZBX-6139 [2] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775847 ** Affects: openipmi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I confirmed the package "4.2.6.p5+dfsg-3ubuntu8.2" solve the bug in Ubuntu Wily # With port <123 using ntpdate (without patch) 11 Feb 20:30:09 ntpdate[2348]: no server suitable for synchronization found # With port <123 using ntpdate (including patch) 11 Feb 20:32:18 ntpdate[3243]: adjust time server 10.10.10.107 offset 0.002017 sec Eric ** Tags added: verification-done-wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I confirmed the package"4.2.6.p3+dfsg-1ubuntu3.9" solved the problem in Ubuntu Precise NTP Version : 1:4.2.6.p3+dfsg-1ubuntu3.1 With no IPTABLES rule ==> Working $ ntpdate x.x.x.x 11 Feb 16:15:19 ntpdate[1243]: adjust time server x.x.x.x offset 0.190571 sec With IPTABLES rule ==> Not working $ iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source y.y.y.y:100-122 $ntpdate x.x.x.x 11 Feb 16:15:36 ntpdate[1253]: no server suitable for synchronization found With ntp (precise-proposed) + IPTABLE rules ==> Now working NTP version: 1:4.2.6.p3+dfsg-1ubuntu3.9 $ iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source y.y.y.y:100-122 $ ntpdate x.x.x.x 11 Feb 16:21:26 ntpdate[1986]: adjust time server x.x.x.x offset 0.005394 sec Eric ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Tags removed: verification-done ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
It has been brought to my attention ... -- I confirm that the proposed testfix package resolved the issue on Trusty. The test were made on test machines where the client had an iptable postrouting nat forcing the source port to be under 123. - ntpdate command performed on the client machine was successful - tcpdump on the server side confirmed that the source port was under 123. -- ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-done ** Tags added: verification-done-trusty ** Tags removed: verification-done-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: ==> NTP server = y.y.y.y ntp.conf configured to be a server. ==> NTP client = x.x.x.x "ntpdate" used to submmit requests #iptable setup to force src port to be lower than 123 iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 + + ## On the client, set to force src port < 123 (without patch) + + $ ntpdate y.y.y.y + ntpdate[]: no server suitable for synchronization found + + ## On the client, set to force src port < 123 (with patch) + + $ ntpdate y.y.y.y + ntpdate[]: adjust time server y.y.y.y offset -0.028483 sec [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: ==> NTP server = y.y.y.y ntp.conf configured to be a server. ==> NTP client = x.x.x.x "ntpdate" used to submmit requests - #iptable setup to force src port to be lower than 123 + #iptable setup to force src port to be lower than 123 iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 ## On the client, set to force src port < 123 (without patch) $ ntpdate y.y.y.y ntpdate[]: no server suitable for synchronization found ## On the client, set to force src port < 123 (with patch) $ ntpdate y.y.y.y ntpdate[]: adjust time server y.y.y.y offset -0.028483 sec [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. + + Setup: + ==> NTP server = y.y.y.y + ntp.conf configured to be a server. + + ==> NTP client = x.x.x.x + "ntpdate" used to submmit requests + + #iptable setup to force src port to be lower than 123 + iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source 10.55.15.154:100-122 [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: - ==> NTP server = y.y.y.y - ntp.conf configured to be a server. - - ==> NTP client = x.x.x.x - "ntpdate" used to submmit requests + ==> NTP server = y.y.y.y + ntp.conf configured to be a server. - #iptable setup to force src port to be lower than 123 - iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source 10.55.15.154:100-122 + ==> NTP client = x.x.x.x + "ntpdate" used to submmit requests + + #iptable setup to force src port to be lower than 123 + iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Precise (12.04) Package version : 4.2.6.p3+dfsg-1ubuntu3.9 -- ** Patch added: "precise_ntp_4.2.6.p3+dfsg-1ubuntu3.9" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1479652/+attachment/4556380/+files/lp1479652_precise_3.9.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Wily (15.10) Package version : 4.2.6.p5+dfsg-3ubuntu8.2 -- ** Patch added: "wily_4.2.6.p5+dfsg-3ubuntu8.2" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652/+attachment/4556354/+files/lp1479652_wily_8.2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Trusty (14.04) Package version : ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8 -- Note: kick-d is currently working on a merge for Xenial, including this patch. I'm including the .debdiffs for the other distributions (W/T/P) for once the merge for Xenial will be completed. ** Patch added: "trusty_ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652/+attachment/4556319/+files/lp1479652_trusty_14.04.8.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: + [Impact] + + If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. + This is occurring in our environment due to NAT. + + [Test Case] + + The problem can easily be reproduced by having an iptable postrouting + nat forcing the source port to be under 123 set on the client. + + [Regression Potential] + + The patch comes from upstream + [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + + A testfix[1] package has been provided to the community before the SRU + process to bring more confidence for the patch. Positive feedbacks has + been given by the community to confirm the patch addressed the bug + [comment #7] + + [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 + + [Original description] + [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] - If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. - This is occurring in our environment due to NAT. + If an NTP client sends a request with a source port less than 123, the + packet is silently ignored by ntpd. This is occurring in our environment + due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream + The patch comes from upstream [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream - [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I have build a test package for the community to validate it solve the bug before starting the SRU process [1]. The goal of this testfix is only to confirm that this solve the bug and it is not a final solution. Here's what has been brought to my attention about the test package I have provided. --- I confirm that the proposed testfix package resolved the issue. The test were made on test machines where the client had an iptable postrouting nat forcing the source port to be under 123. - ntpdate command performed on the client machine was successful - tcpdump on the server side confirmed that the source port was under 123. Please advise for the next steps Thank-you --- [1] - https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Changed in: ntp (Ubuntu Xenial) Status: New => In Progress ** Changed in: ntp (Ubuntu Wily) Status: New => In Progress ** Changed in: ntp (Ubuntu Precise) Status: New => In Progress ** Changed in: ntp (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Changed in: ntp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Wily) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Xenial) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Vivid ** Patch added: "Rebase Vivid debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508498/+files/lp1481388_rebase_vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Trusty ** Patch added: "Rebase Trusty debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508494/+files/lp1481388_rebase_trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Precise ** Patch added: "Rebase Precise debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508496/+files/lp1481388_rebase_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Patch removed: "debdiff for precise" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4452908/+files/lp1481388_precise.debdiff ** Patch removed: "debdiff for trusty" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4453392/+files/lp1481388_trusty.debdiff ** Patch removed: "debdiff for vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456186/+files/lp1481388_vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Hi Mathew, I have the knowledge of the code, I will rebase the debdiffs for V/T/P Note: I checked and Xenial has the patch already. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Good evening Mathew, Does it mean I need to re-do the debdiffs ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Good evening Chris, This bug has been brought to my attention by someone in the community. Unfortunately, I never had a confirmation from him if the fix solve his issue or not... but as state in comment #5 & #11, I've been able to reproduce the problem and make sure it addressed the situation. The reproducer is basically to lower down the value of "net.core.[m-r]mem_default" and adding multiples network interface + static route. FYI, the same fix has been also applied in Debian ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795315 Let me know if you need anything else. Thanks ! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
Source version has been modified for version "1:1.0.17-1ubuntu2.1". Thanks ! ** Patch added: "debdiff for Precise-2" https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+attachment/4482207/+files/lp1498697-precise-2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
As per our irc conversation, I'm removing the "2nd debdiff for Vivid" and arges will re-upload the fix with the original patch I posted for Vivid. Sorry for the confusion, and thanks Brian for you feedbacks on this. ** Patch removed: "2nd debdiff for Vivid" https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1498697/+attachment/4480119/+files/lp1498697_vivid2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
Hi Brian, I got a discussion with arges yesterday about it. vivid version of tgt didn't build with this error : sbuild-build-depends-tgt-dummy : Depends: libibverbs-dev (>= 1.1.8-1ubuntu1.1) but 1.1.8-1ubuntu1 is to be installed I think it has something to do with this LP patch : LP: https://bugs.launchpad.net/bugs/1409904 PPA: https://launchpad.net/~inaddy/+archive/ubuntu/lp1409904/ This is why the version of libibverbs-dev changed in the Vivid upload. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
2nd debdiff for Vivid (Fixing the unmet depencies of "libibverbs-dev") ** Patch added: "2nd debdiff for Vivid" https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1498697/+attachment/4480119/+files/lp1498697_vivid2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Precise ** Changed in: tgt (Ubuntu Precise) Status: New => In Progress ** Changed in: tgt (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: tgt (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Patch added: "debdiff for Precise" https://bugs.launchpad.net/ubuntu/vivid/+source/tgt/+bug/1498697/+attachment/4474355/+files/lp1498697_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Vivid ** Changed in: tgt (Ubuntu Vivid) Status: New => Confirmed ** Changed in: tgt (Ubuntu Vivid) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: tgt (Ubuntu Vivid) Importance: Undecided => High ** Changed in: tgt (Ubuntu Vivid) Status: Confirmed => In Progress ** Patch added: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+attachment/4473745/+files/lp1409904_vivid.debdiff ** Changed in: tgt (Ubuntu Vivid) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Trusty ** Description changed: + SRU JUSTIFICATION + + [Impact] + + * tgtadm returns inconsistents results. Some targets are not +listed during one run, but are shown by a run immediately after. + + [Test Case] + + * With large number of targets : + + # ./tgtadm -L iscsi --mode target --op show | fgrep -c Target + 564 + + # dpkg -l | fgrep tgt + ii tgt 1:1.0.43-0ubuntu4 amd64 Linux SCSI target user-space tools + + # cat /etc/lsb-release + DISTRIB_ID=Ubuntu + DISTRIB_RELEASE=14.04 + DISTRIB_CODENAME=trusty + DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" + + + Buggy 1.0.43 version: + + # for i in {1..100} ; do diff -u <(/usr/sbin/tgtadm -L iscsi --mode target --op show | fgrep Target) <(/usr/sbin/tgtadm -L iscsi --mode target --op show | fgrep Target) ; sleep 1 ; done + --- /dev/fd/63 2015-09-22 23:05:38.648448562 + + +++ /dev/fd/62 2015-09-22 23:05:38.648448562 + + @@ -560,3 +560,5 @@ + Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 + Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 + Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 + +Target 580: iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45 + +Target 581: iqn.2010-10.org.openstack:volume-ddcebcc4-eb13-459e-be1d-2068ee03a4c6 + --- /dev/fd/63 2015-09-22 23:05:40.720506264 + + +++ /dev/fd/62 2015-09-22 23:05:40.720506264 + + @@ -560,3 +560,4 @@ + Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 + Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 + Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 + +Target 580: iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45 + --- /dev/fd/63 2015-09-22 23:05:41.752535004 + + +++ /dev/fd/62 2015-09-22 23:05:41.752535004 + + @@ -560,3 +560,5 @@ + Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 + Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 + Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 + +Target 580: iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45 + +Target 581: iqn.2010-10.org.openstack:volume-ddcebcc4-eb13-459e-be1d-2068ee03a4c6 + --- /dev/fd/63 2015-09-22 23:05:43.828592816 + + +++ /dev/fd/62 2015-09-22 23:05:43.828592816 + + @@ -560,4 +560,3 @@ + Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 + Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 + Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 + -Target 580: iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45 + + [Regression Potential] + + * None expected, the patch comes from tgt upstream repo and it is + already implemented in Ubuntu Wily and Debian. + + [Other Info] + + * The fix has been tested by the community and the fix resolved the issue. For more details see Comment #4 + + [Original Description] + With a large number of targets tgtadm --mode target --op show returns inconsistent results. Some targets are not listed during one run, but are shown by a run immediately after. I grabbed the binary from the wily package and I am getting consistent results, so somewhere between 1.0.43 and 1.0.57 upstream seems to have patched the bug. Can we get 1.0.57 (or whatever version has the fix) backported to trusty? # ./tgtadm -L iscsi --mode target --op show | fgrep -c Target 564 # dpkg -l | fgrep tgt ii tgt 1:1.0.43-0ubuntu4 amd64 Linux SCSI target user-space tools - # cat /etc/lsb-release + # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" Buggy 1.0.43 version: # for i in {1..100} ; do diff -u <(/usr/sbin/tgtadm -L iscsi --mode target --op show | fgrep Target) <(/usr/sbin/tgtadm -L iscsi --mode target --op show | fgrep Target) ; sleep 1 ; done --- /dev/fd/632015-09-22 23:05:38.648448562 + +++ /dev/fd/622015-09-22 23:05:38.648448562 + @@ -560,3 +560,5 @@ - Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 - Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 - Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 + Target 574: iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922 + Target 578: iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2 + Target 579: iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65 +Target 580: iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45 +Target 581: iqn.
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags added: verification-done ** Changed in: tgt (Ubuntu Trusty) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
I'm providing a hotfix[1] for Trusty (14.04) on a ppa[2], based on the upstream commit : 6c4ffa0[3], for the community to test and provide feedbacks before starting the SRU process. This hotfix is only for testing purpose. [1] Version : 1:1.0.43-0ubuntu4.1~14.04.1+20150923lp1498697~1 [2] https://launchpad.net/~eric-desrochers-z/+archive/ubuntu/tgt1498697 [2] 6c4ffa0 tgtadm: fix a bug to read the response buffer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Changed in: tgt (Ubuntu Trusty) Importance: Undecided => High ** Changed in: tgt (Ubuntu Trusty) Status: New => Confirmed ** Changed in: tgt (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Simon, you may want to add a few ethernet interfaces and static routes. I was able to reproduce it with ~6 network interface. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Wily) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for wily ** Patch added: "debdiff for wily" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456187/+files/lp1481388_wily.debdiff ** Changed in: ntp (Ubuntu Wily) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for vivid ** Patch added: "debdiff for vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456186/+files/lp1481388_vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Patch removed: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4455714/+files/lp1481388_vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for Vivid ** Patch added: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1481388/+attachment/4455714/+files/lp1481388_vivid.debdiff ** Changed in: ntp (Ubuntu Vivid) Status: Confirmed => In Progress ** Changed in: ntp (Ubuntu Vivid) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for trusty ** Patch added: "1:4.2.6.p5+dfsg-3ubuntu2.14.04.4" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1481388/+attachment/4453392/+files/lp1481388_trusty.debdiff ** Changed in: ntp (Ubuntu Trusty) Status: Confirmed => In Progress ** Changed in: ntp (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
I also noticed the situation can be reproduced at boot if the value of "net.core.rmem_default" is too low. I reproduced it by only lowering the "net.core.rmem_default = 2000" value with 6 network interface at boot. ntpd[851]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 ntpd[851]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 ntpd[851]: Listen and drop on 1 v6wildcard :: UDP 123 ntpd[851]: Listen normally on 2 eth1 192.168.1.10 UDP 123 ntpd[851]: Listen normally on 3 eth2 192.168.2.10 UDP 123 ntpd[851]: Listen normally on 4 eth3 192.168.3.10 UDP 123 ntpd[851]: Listen normally on 5 eth4 192.168.4.10 UDP 123 ntpd[851]: Listen normally on 6 eth5 192.168.5.10 UDP 123 ntpd[851]: Listen normally on 7 eth6 192.168.6.10 UDP 123 ntpd[851]: peers refreshed ntpd[851]: Listening on routing socket on fd #24 for interface updates ntpd[851]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for ntp.ubuntu.com 1 ntpd[864]: signal_no_reset: signal 17 had flags 400 ===> ntpd[851]: i/o error on routing socket No buffer space available - disabling <=== -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise ** Description changed: + [Impact] + + * User experienced repeated segfaults at the same instruction pointer + + i/o error on routing socket No buffer space available - disabling + segfault at 31 ip 0031 sp 79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000] + + The remove_ and delete_ functions remove the current element from the + asyncio_reader_list, and free it, respectively. + + We then return back to the loop at the top, wherein the asyncio_reader variable still points at the now-freed element, whose contents are (in theory) now scrambled + by having link pointers, etc, from internal malloc state overlaying the data. + + [Test Case] + + You can easily reproduce the bug by : + + - Lowering the sysctl value net.core.rmem_max + + $ sysctl -w net.core.wmem_max= + This sets the max OS send buffer size for all types of connections. + + - Adding multiple network interfaces and static routes. + + [Regression Potential] + + None expected since the fix is already available upstream + (https://github.com/ntp-project/ntp.git) and Debian package. + + If after installing the patch, user are receiving this kind of message in /var/log/syslog : "routing socket reports: No buffer space available". + The next step, would be to increase the "net.core.rmem_max" and "net.core.wmem_max" values equally until the "routing socket reports: No buffer space available" message no longer showed up. + + [Other Info] + + NTP upstream (https://github.com/ntp-project/ntp.git) + [Bug 2224] Use-after-free in routing socket code after dropping root. - Commit: d6df9d3 + [Bug 2890] Ignore ENOBUFS on routing netlink socket. - Commit: db47bd4 + + The use-after-free bug has been fix in Debian release (closes: #795315) + Will submit the ignore-ENOBUFS-on-routing-netlink-socket in Debian in the next days. + + [Original Description] + We have 1 server (among hundreds) that its ntp service is crashing. A few minute/seconds after a start attempts we can see the following in syslog: ntpd[2729]: peers refreshed ntpd[2729]: Listening on routing socket on fd #49 for interface updates ntpd[2729]: i/o error on routing socket No buffer space available - disabling kernel: [157516.495224] ntpd[2729]: segfault at 31 ip 0031 sp 79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000] OS: Ubuntu 12.04.4 LTS Kernel: 3.11.0-19-generic I tried to compare it to other servers, and the only thing I could find that is different is that while it's up (before it crashes) I can see the following when running "lsof | grep ntp": ntpd 2729 ntp 49u sock 0,7 0t0 2473952565 can't identify protocol. ** Tags added: verification-done ** Changed in: ntp (Ubuntu Precise) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise ** Patch added: "debdiff for precise" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+attachment/4452908/+files/lp1481388_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: ntp (Ubuntu Vivid) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: ntp (Ubuntu Precise) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
I was able to reproduce the problem on PRECISE (12.04) by lowering the kernel parameter value "net.core.rmem_max". And then test my .deb build on my PPA[1] with the following upstream commits : - d6df9d3 [Bug 2224] Use-after-free in routing socket code after dropping root. - db47bd4 [Bug 2890] Ignore ENOBUFS on routing netlink socket. What the patch does ? === The program first "read" from the fd. On success, the number of bytes written into buf is returned. On error, the call returns −1 and sets errno If the call returns -1, then there is a verification to validate if the errno == ENOBUFS and then send to syslog the following message : "routing socket reports: No buffer space available" Otherwise, if errno is NOT ENOBUFS, then it close the socket (remove_asyncio_reader(reader);) and free the memory space (delete_asyncio_reader(reader);) And send to syslog the following message : i/o error on routing socket No buffer space available - disabling Before this patch, no matter what was the errno, it was automatically close() and free() without validation if ENOBUFS or not. To summarize, the patch allow the program to not close() and free() the socket when the a errno == ENOBUFS occur, but still send a message in syslog to notify the administrator. === If after installing the patch, you are receiving this kind of message in /var/log/syslog : "routing socket reports: No buffer space available" The next step, would be to increase the "net.core.rmem_max" and "net.core.wmem_max"values equally until the "routing socket reports: No buffer space available" message no longer showed up. [1] 1:4.2.6.p3+dfsg-1ubuntu3.4+20150820lp1481388~2 https://launchpad.net/~eric-desrochers-z/+archive/ubuntu/lp1481388 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs