public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies
Date: Sat, 6 Apr 2019 12:38:35 +0200	[thread overview]
Message-ID: <20190406103835.GA15362@amd> (raw)
In-Reply-To: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com>

Hi!

> 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?

Ok, so first patch adds support for using "delayed" DHCP replies, then
there are three more patches to fix up issues it creates.

Which tells me that maybe this is not quite suitable for -stable.

How long do your dhcp servers take to reply? Can you solve the problem
some other way, like for example increasing timeouts?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190406/635ad643/attachment.sig>

  parent reply	other threads:[~2019-04-06 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 ` [cip-dev] [PATCH 4.4 1/5] net: ipconfig: Support using "delayed" DHCP replies Patryk Mungai
2019-04-05 10:47 ` [cip-dev] [PATCH 4.4 2/5] net: ipconfig: drop inter-device timeout Patryk Mungai
2019-04-05 10:47 ` [cip-dev] [PATCH 4.4 3/5] net: ipconfig: fix use after free Patryk Mungai
2019-04-05 10:47 ` [cip-dev] [PATCH 4.4 4/5] net: ipconfig: Fix more " Patryk Mungai
2019-04-05 10:47 ` [cip-dev] [PATCH 4.4 5/5] net: ipconfig: Fix NULL pointer dereference on RARP/BOOTP/DHCP timeout Patryk Mungai
2019-04-06 10:38 ` Pavel Machek [this message]
2019-04-09  9:10   ` [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Patryk Mungai Ndungu
2019-04-06 13:53 ` Sasha Levin
2019-04-24 16:44   ` 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=20190406103835.GA15362@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox