From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DB0AC10F06 for ; Sat, 6 Apr 2019 10:38:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CD49E21855 for ; Sat, 6 Apr 2019 10:38:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726387AbfDFKie (ORCPT ); Sat, 6 Apr 2019 06:38:34 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:53574 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726036AbfDFKie (ORCPT ); Sat, 6 Apr 2019 06:38:34 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 21BF580572; Sat, 6 Apr 2019 12:38:24 +0200 (CEST) Date: Sat, 6 Apr 2019 12:38:35 +0200 From: Pavel Machek To: Patryk Mungai Cc: stable@vger.kernel.org, davem@davemloft.net, cip-dev@lists.cip-project.org Subject: Re: [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Message-ID: <20190406103835.GA15362@amd> References: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 g= et > a dhcp address. >=20 > 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 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlyogasACgkQMOfwapXb+vIZSwCfWkg4sj1ytNA1gX2EkyBj0GMN odcAoIjlPX5j5tXOTHpgMoao5t7hGzBw =o7fl -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--