From: Patryk Mungai <patryk.mungai-ndungu.kx@renesas.com> To: stable@vger.kernel.org Cc: davem@davemloft.net, cip-dev@lists.cip-project.org, Patryk Mungai <patryk.mungai-ndungu.kx@renesas.com> Subject: [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Date: Fri, 5 Apr 2019 11:47:31 +0100 [thread overview] Message-ID: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> (raw) Dear All, When running dhcp tests using the 4.4.y (and 4.4.y-cip kernel as well), I encountered an issue where the dhcp client in the kernel could not get an IP address when multiple network devices were enabled. It seems that the current implementation of the dhcp client in the 4.4 kernel is send dhcp request via device 1 -> wait <1s for response from server on device 1 -> if no response, switch to device 2 -> repeat process on device 2 ...etc. When the dhcp server is slow to respond, this means it is impossible to get a dhcp address. This series backported from upstream fixes the issue, is it possible to apply this to 4.4.y and/or 4.4.y-cip? Thanks, Patryk Geert Uytterhoeven (1): net: ipconfig: Fix NULL pointer dereference on RARP/BOOTP/DHCP timeout Thierry Reding (1): net: ipconfig: Fix more use after free Uwe Kleine-König (3): net: ipconfig: Support using "delayed" DHCP replies net: ipconfig: drop inter-device timeout net: ipconfig: fix use after free net/ipv4/ipconfig.c | 61 ++++++++++++++++++++++++----------------------------- 1 file changed, 28 insertions(+), 33 deletions(-) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: patryk.mungai-ndungu.kx@renesas.com (Patryk Mungai) To: cip-dev@lists.cip-project.org Subject: [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Date: Fri, 5 Apr 2019 11:47:31 +0100 [thread overview] Message-ID: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> (raw) Dear All, When running dhcp tests using the 4.4.y (and 4.4.y-cip kernel as well), I encountered an issue where the dhcp client in the kernel could not get an IP address when multiple network devices were enabled. It seems that the current implementation of the dhcp client in the 4.4 kernel is send dhcp request via device 1 -> wait <1s for response from server on device 1 -> if no response, switch to device 2 -> repeat process on device 2 ...etc. When the dhcp server is slow to respond, this means it is impossible to get a dhcp address. This series backported from upstream fixes the issue, is it possible to apply this to 4.4.y and/or 4.4.y-cip? Thanks, Patryk Geert Uytterhoeven (1): net: ipconfig: Fix NULL pointer dereference on RARP/BOOTP/DHCP timeout Thierry Reding (1): net: ipconfig: Fix more use after free Uwe Kleine-K?nig (3): net: ipconfig: Support using "delayed" DHCP replies net: ipconfig: drop inter-device timeout net: ipconfig: fix use after free net/ipv4/ipconfig.c | 61 ++++++++++++++++++++++++----------------------------- 1 file changed, 28 insertions(+), 33 deletions(-) -- 2.7.4
next reply other threads:[~2019-04-05 10:48 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-05 10:47 Patryk Mungai [this message] 2019-04-05 10:47 ` [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Patryk Mungai 2019-04-05 10:47 ` [PATCH 4.4 1/5] net: ipconfig: Support using "delayed" DHCP replies Patryk Mungai 2019-04-05 10:47 ` [cip-dev] " Patryk Mungai 2019-04-05 10:47 ` [PATCH 4.4 2/5] net: ipconfig: drop inter-device timeout Patryk Mungai 2019-04-05 10:47 ` [cip-dev] " Patryk Mungai 2019-04-05 10:47 ` [PATCH 4.4 3/5] net: ipconfig: fix use after free Patryk Mungai 2019-04-05 10:47 ` [cip-dev] " Patryk Mungai 2019-04-05 10:47 ` [PATCH 4.4 4/5] net: ipconfig: Fix more " Patryk Mungai 2019-04-05 10:47 ` [cip-dev] " Patryk Mungai 2019-04-05 10:47 ` [PATCH 4.4 5/5] net: ipconfig: Fix NULL pointer dereference on RARP/BOOTP/DHCP timeout Patryk Mungai 2019-04-05 10:47 ` [cip-dev] " Patryk Mungai 2019-04-06 10:38 ` [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Pavel Machek 2019-04-06 10:38 ` Pavel Machek 2019-04-09 9:10 ` Patryk Mungai Ndungu 2019-04-09 9:10 ` Patryk Mungai Ndungu 2019-04-06 13:53 ` Sasha Levin 2019-04-06 13:53 ` [cip-dev] " Sasha Levin 2019-04-24 16:44 ` Greg KH 2019-04-24 16:44 ` [cip-dev] " Greg KH
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com \ --to=patryk.mungai-ndungu.kx@renesas.com \ --cc=cip-dev@lists.cip-project.org \ --cc=davem@davemloft.net \ --cc=stable@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.