From: Juergen Gross <jgross@suse.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>, netdev@vger.kernel.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
Liam Shepherd <liam@dancer.es>
Subject: Re: [PATCH 2/2] xen-netfront: Update features after registering netdev
Date: Thu, 21 Jun 2018 15:12:33 +0200 [thread overview]
Message-ID: <754ddc45-215a-458c-2b58-e9d979471f4d@suse.com> (raw)
In-Reply-To: <20180621130021.27029-3-ross.lagerwall@citrix.com>
On 21/06/18 15:00, Ross Lagerwall wrote:
> Update the features after calling register_netdev() otherwise the
> device features are not set up correctly and it not possible to change
> the MTU of the device. After this change, the features reported by
> ethtool match the device's features before the commit which introduced
> the issue and it is possible to change the device's MTU.
>
> Fixes: f599c64fdf7d ("xen-netfront: Fix race between device setup and open")
> Reported-by: Liam Shepherd <liam@dancer.es>
> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2018-06-21 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 13:00 [PATCH 0/2] xen-netfront: Fix issues with commit f599c64fdf7d Ross Lagerwall
2018-06-21 13:00 ` [PATCH 1/2] xen-netfront: Fix mismatched rtnl_unlock Ross Lagerwall
2018-06-21 13:05 ` Juergen Gross
2018-06-21 13:00 ` [PATCH 2/2] xen-netfront: Update features after registering netdev Ross Lagerwall
2018-06-21 13:12 ` Juergen Gross [this message]
2018-06-21 22:56 ` [PATCH 0/2] xen-netfront: Fix issues with commit f599c64fdf7d David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=754ddc45-215a-458c-2b58-e9d979471f4d@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=liam@dancer.es \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox