Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+ guint32 mtu = 0;
+ g_object_get (setting, "mtu", &mtu, NULL);
mtu should be guint.
rest lgtm
Comment 4Beniamino Galvani
2016-10-27 07:58:44 UTC
(In reply to Thomas Haller from comment #3)
> + guint32 mtu = 0;
> + g_object_get (setting, "mtu", &mtu, NULL);
>
> mtu should be guint.
Fixed, thanks.
Comment 5Beniamino Galvani
2016-11-08 12:27:23 UTC
Repushed with an additional commit (device: don't call apply_mtu_from_config() when ipv4.method=disabled)
lgtm
maybe: in a follow-up commit move apply_slave_mtu() inside where it's called.
maybe:
else
_LOGW (LOGD_IP4, "unhandled IPv4 config method '%s'; will fail", method);
should be just g_return_val_if_reached (ret); Seems we hit this line only in case of a bug, where we can just as well assert.
Comment 7Beniamino Galvani
2016-11-15 17:31:24 UTC
(In reply to Thomas Haller from comment #6)
> lgtm
>
> maybe: in a follow-up commit move apply_slave_mtu() inside where it's called.
I thinks it's nicer to have a separate function that does only one thing even if there is only one caller.
> maybe:
>
> else
> _LOGW (LOGD_IP4, "unhandled IPv4 config method '%s'; will fail",
> method);
>
>
> should be just g_return_val_if_reached (ret); Seems we hit this line only in
> case of a bug, where we can just as well assert.
Updated, thanks.
Comment 10Beniamino Galvani
2017-02-18 08:04:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2299