From mboxrd@z Thu Jan 1 00:00:00 1970 From: sashal@kernel.org (Sasha Levin) Date: Sat, 6 Apr 2019 09:53:50 -0400 Subject: [cip-dev] [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies In-Reply-To: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> References: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> Message-ID: <20190406135350.GA2935@sasha-vm> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org On Fri, Apr 05, 2019 at 11:47:31AM +0100, Patryk Mungai wrote: >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? This is something that seems more suited for the CIP kernel as it adds new functionality. -- Thanks, Sasha 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.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,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 EE29EC10F06 for ; Sat, 6 Apr 2019 13:53:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B62EE20870 for ; Sat, 6 Apr 2019 13:53:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554558832; bh=8gkQDapKE1jZmYBtsSmMOQYsvQWgEAgxBQmTLse83mE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=OC1vSDrQs1fOddutYMYly/Wt9/z3q3rDv4X8Qx76NZw85o0wvgdmTvz/h5u/3RsvO kGDRAgcGml6q1Xs1jbmNYBft4//ub6I4j8HjO+Xvqw7VqW+NFym7alSIP1cOnDw0p5 kXLqVUFssJlI8YmEMudyGzfy5hOBEigX0aRsxvMo= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726499AbfDFNxw (ORCPT ); Sat, 6 Apr 2019 09:53:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:44712 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726493AbfDFNxw (ORCPT ); Sat, 6 Apr 2019 09:53:52 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 395B9206BA; Sat, 6 Apr 2019 13:53:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554558831; bh=8gkQDapKE1jZmYBtsSmMOQYsvQWgEAgxBQmTLse83mE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Lj+S01tQyvk0M5VRXz+3zXMJCKaF2pfUtJyLt7jFdnhlzfB27i5aDln9hIVrdPu9G qpfhKMTctfEVrly1PQ1nZVZVXZysLZphyYFRRCV1dgr63WMw2pkO/Tkxhq/OkOf6+P W161Pdn6PEw4TFhERiKFzagc0Pj5ZFKI57vZmn+w= Date: Sat, 6 Apr 2019 09:53:50 -0400 From: Sasha Levin To: Patryk Mungai Cc: stable@vger.kernel.org, davem@davemloft.net, cip-dev@lists.cip-project.org Subject: Re: [PATCH 4.4 0/5] DHCP client support when receiving "delayed" replies Message-ID: <20190406135350.GA2935@sasha-vm> References: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Apr 05, 2019 at 11:47:31AM +0100, Patryk Mungai wrote: >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? This is something that seems more suited for the CIP kernel as it adds new functionality. -- Thanks, Sasha