linux-kernel - Re: [PATCH] xen-netfront: enable device after manual module load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180108.141722.1413694733176935221.davem@davemloft.net>
Date:   Mon, 08 Jan 2018 14:17:22 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     otubo@...hat.com
Cc:     linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        xen-devel@...ts.xenproject.org, jgross@...e.com,
        boris.ostrovsky@...cle.com, vkuznets@...hat.com, mgamal@...hat.com,
        cavery@...hat.com
Subject: Re: [PATCH] xen-netfront: enable device after manual module load

From: Eduardo Otubo <otubo@...hat.com>
Date: Fri,  5 Jan 2018 09:42:16 +0100

> When loading the module after unloading it, the network interface would
> not be enabled and thus wouldn't have a backend counterpart and unable
> to be used by the guest.
> 
> The guest would face errors like:
> 
>   [root@...st ~]# ethtool -i eth0
>   Cannot get driver information: No such device
> 
>   [root@...st ~]# ifconfig eth0
>   eth0: error fetching interface information: Device not found
> 
> This patch initializes the state of the netfront device whenever it is
> loaded manually, this state would communicate the netback to create its
> device and establish the connection between them.
> 
> Signed-off-by: Eduardo Otubo <otubo@...hat.com>

Applied, thank you.