Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct panic when IPv4 lacks IFA_ADDRESS address #665

Merged
merged 1 commit into from
Jul 3, 2021

Conversation

jswantek
Copy link
Contributor

IFA_ADDRESS is to be used as the peer address if it differs from IFA_LOCAL.
Therefore, include the check for "no IFA_ADDRESS" in the difference check.

Example: ppp interfaces can contain IFA_LOCAL and no IFA_ADDRESS attribute

Signed-off-by: Joe Swantek [email protected]

IFA_ADDRESS is to be used as the peer address if it differs from IFA_LOCAL.
Therefore, include the check for "no IFA_ADDRESS" in the difference check.

Example: ppp interfaces can contain IFA_LOCAL and no IFA_ADDRESS attribute
@jswantek
Copy link
Contributor Author

Addresses issue: #664

@jswantek
Copy link
Contributor Author

jswantek commented Jul 2, 2021

It was discovered that this does resolve a potential panic but there is other elements in the code-base that assume IFA_ADDRESS will be present. Maybe a larger fix to remove that assumption is necessary?

@aboch
Copy link
Collaborator

aboch commented Jul 3, 2021

LGTM

@aboch aboch merged commit 5345539 into vishvananda:master Jul 3, 2021
EdTheBearded added a commit to EdTheBearded/meta-common-torizon that referenced this pull request Aug 29, 2024
Sometimes, especially on devices relying on modems, docker would fail to
initialize and create 'docker0' interface. This is a known issue [1],
that was solved upstream [2].

Since we're using an older version of docker, I've backported this fix
to our layer.

[1] moby/moby#43034
[2] vishvananda/netlink#665

Signed-off-by: Eduardo Ferreira <[email protected]>
EdTheBearded added a commit to EdTheBearded/meta-common-torizon that referenced this pull request Aug 29, 2024
Sometimes, especially on devices relying on modems, docker would fail to
initialize and create 'docker0' interface. This is a known issue [1],
that was solved upstream [2].

Since we're using an older version of docker, I've backported this fix
to our layer.

[1] moby/moby#43034
[2] vishvananda/netlink#665

Related-to: TOR-3551

Signed-off-by: Eduardo Ferreira <[email protected]>
EdTheBearded added a commit to EdTheBearded/meta-toradex-torizon that referenced this pull request Aug 29, 2024
Sometimes, especially on devices relying on modems, docker would fail to
initialize and create 'docker0' interface. This is a known issue [1],
that was solved upstream [2].

Since we're using an older version of docker, I've backported this fix
to our layer.

[1] moby/moby#43034
[2] vishvananda/netlink#665

Related-to: TOR-3551

Signed-off-by: Eduardo Ferreira <[email protected]>
EdTheBearded added a commit to EdTheBearded/meta-toradex-torizon that referenced this pull request Aug 29, 2024
Sometimes, especially on devices relying on modems, docker would fail to
initialize and create 'docker0' interface. This is a known issue [1],
that was solved upstream [2].

Since we're using an older version of docker, I've backported this fix
to our layer.

[1] moby/moby#43034
[2] vishvananda/netlink#665

Related-to: TOR-3551

Signed-off-by: Eduardo Ferreira <[email protected]>
microhobby pushed a commit to commontorizon/meta-common-torizon that referenced this pull request Sep 19, 2024
Sometimes, especially on devices relying on modems, docker would fail to
initialize and create 'docker0' interface. This is a known issue [1],
that was solved upstream [2].

Since we're using an older version of docker, I've backported this fix
to our layer.

[1] moby/moby#43034
[2] vishvananda/netlink#665

Related-to: TOR-3551

Signed-off-by: Eduardo Ferreira <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants