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

mcast: fix leaked igmp packets on multicast cleanup #1391

Closed
wants to merge 2 commits into from

Conversation

fichtner
Copy link
Contributor

The commits cherry-picked here have not been added to stable/14.
They have been known to fix IGMP leave messages which are currently
broken on both 14.0 and 14.1. The necessary MFC has been absent from
them for unknown reasons.

Differential Revision: https://reviews.freebsd.org/D46190

This reverts commit fa03d37.

This commit caused us to not send IGMP leave messages if the inpcb went
away. In other words: we freed pending packets whenever the socket
closed rather than when the interface (or address) goes away.

Reviewed by:	glebius
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D43032

(cherry picked from commit c196e43)
When we release a multicast address (e.g. on interface shutdown) we may
still have packets queued in inm_scq. We have to free those, or we'll
leak memory.

Reviewed by:	glebius
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D43033

(cherry picked from commit c2e3404)
@bsdimp
Copy link
Member

bsdimp commented Aug 23, 2024

Normally we don't take MFC PRs. However, this one looks like it's easy enough to followup on so I'll allow it for now.

@bsdimp bsdimp self-assigned this Aug 23, 2024
@fichtner
Copy link
Contributor Author

Thanks. To avoid chasing up committers for MFC on operational issues would it make sense to make this semi-recurring? One change of note is ad874544d9f that would at least benefit 14.2 in the long run.

@bsdimp
Copy link
Member

bsdimp commented Aug 28, 2024

Yea, the original committer is responsible for MFC requests. So that's the first line of attack on that.
Now that we have git, we can likely shift how we do MFC requests, but are still operating under the old ways.

@fichtner
Copy link
Contributor Author

Fair enough, thanks for responding. I'll chase Vincenzo then.

@glebius
Copy link
Member

glebius commented Sep 13, 2024

These two commits had already been merged. I really don't understand why github doesn't reflect this.

@glebius glebius closed this Sep 13, 2024
@emaste
Copy link
Member

emaste commented Sep 13, 2024

I really don't understand why github doesn't reflect this.

The hashes in this pull request commits (d7d51e1, e2e0761) don't match the hashes in stable/14 (31ad232, 88e1bc0) so GitHub does not know that the changes were merged.

@bsdimp
Copy link
Member

bsdimp commented Sep 13, 2024

Even if they did match, it would only close it.
There is no good way to accept MFC pull requests.

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.

5 participants