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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,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 C8FCBC282CE for ; Wed, 24 Apr 2019 16:44:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 99C80206A3 for ; Wed, 24 Apr 2019 16:44:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556124285; bh=9wAKuPO4KdMijb6jZweXa8M6Msx4hN5/8fMMkLSCnYg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=RcITbqkOaDpnKB0jmOVzcHdH4VzvEydB5O2Qsn6IcIEBxfs5Fu+0C8MPKJHuPVZo5 0YGYO6h1LYnaH1eXGqf/lpevVO5fqWHa/k5BD4yixFEH45I5OMnnBolFBPLn4j+IIU CeLlUEnHNC9wkHrBvXfgXbhHUcmFAYQQ5TFkfudo= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732693AbfDXQoo (ORCPT ); Wed, 24 Apr 2019 12:44:44 -0400 Received: from mail.kernel.org ([198.145.29.99]:51468 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726935AbfDXQom (ORCPT ); Wed, 24 Apr 2019 12:44:42 -0400 Received: from localhost (62-193-50-229.as16211.net [62.193.50.229]) (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 54512206A3; Wed, 24 Apr 2019 16:44:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556124281; bh=9wAKuPO4KdMijb6jZweXa8M6Msx4hN5/8fMMkLSCnYg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pzrXqx37ZbF2Poa4sREiJCTt765AcJTujB/Eck9T4hHTiIy/SdXWjIuNyBUf5YzeL BQcnQCSAxD3gsQa/G0/a8/u4TLKykKFGA2V22xLGjUVeEU6rvD5CFEXuaIcrnu7jPe iKpiqK8BoFZiV2QfDM3an7l5MMRBstBAqiRiOPpY= Date: Wed, 24 Apr 2019 18:44:39 +0200 From: Greg KH To: Sasha Levin Cc: Patryk Mungai , 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: <20190424164439.GB21916@kroah.com> References: <1554461256-12966-1-git-send-email-patryk.mungai-ndungu.kx@renesas.com> <20190406135350.GA2935@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190406135350.GA2935@sasha-vm> User-Agent: Mutt/1.11.4 (2019-03-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Sat, Apr 06, 2019 at 09:53:50AM -0400, Sasha Levin wrote: > 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. I agree, this is a new feature. If someone wants this, they should use a newer kernel please. Like 4.19.y :) thanks, greg k-h