netdev - Re: [PATCH v3] net: Cavium: Fix MAC address setting in shutdown state

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 24 Jun 2015 01:03:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	p.fedin@...sung.com
Cc:	netdev@...r.kernel.org, Aleksey.Makarov@...iumnetworks.com,
	sgoutham@...ium.com, thlab.kim@...sung.com, s.dyasly@...sung.com,
	robert.richter@...iumnetworks.com
Subject: Re: [PATCH v3] net: Cavium: Fix MAC address setting in shutdown
 state

From: Pavel Fedin <p.fedin@...sung.com>
Date: Tue, 23 Jun 2015 17:51:06 +0300

> This bug pops up with NetworkManager on Fedora 21. NetworkManager tends to
> stop the interface (nicvf_stop() is called) before changing settings. In
> stopped state MAC cannot be sent to a PF. However, when the interface is
> restarted (nicvf_open() is called), we ping the PF using NIC_MBOX_MSG_READY
> message, and the PF replies back with old MAC address, overriding what we
> had after MAC setting from userspace. As a result, we cannot set MAC
> address using NetworkManager.
> 
> This patch introduces special tracking of MAC change in stopped state so
> that the correct new MAC address is sent to a PF when interface is reopen.
> 
> Signed-off-by: Pavel Fedin <p.fedin@...sung.com>

Applied, thanks.

> - Fixed (actually hand-edited) file permissions to be 644. I occasionally pushed them as 755 to my
> local repo.

You should be sending patches against my repo, or something derived from it,
which therefore has the correct file permissions for these files.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html