Fix a possible refcount leak in regen_tmpaddr().
ClosedPublic
Actions

Authored by markj on Apr 8 2015, 5:18 AM.

Tags

None

Referenced Files

	F168065682: D2253.id4736.diff
	Wed, Aug 26, 5:24 AM

	F168064560: D2253.diff
	Wed, Aug 26, 5:16 AM

	F168064542: D2253.diff
	Wed, Aug 26, 5:15 AM

	Unknown Object (File)
	Sat, Aug 15, 10:11 PM

	Unknown Object (File)
	Thu, Aug 13, 12:35 PM

	Unknown Object (File)
	Thu, Aug 13, 12:34 PM

	Unknown Object (File)
	May 5 2026, 9:01 AM

	Unknown Object (File)
	Apr 29 2026, 12:25 PM

View All Files

Subscribers

imp

Details

Reviewers

ae
hrs
bz

Commits

rS281483: Fix a possible refcount leak in regen_tmpaddr().

Summary

public_ifa6 may be set to NULL after taking a reference to a previous
element of the address list. Instead, only take the reference once we've
left the loop, but before releasing the address list lock.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

markj updated this revision to Diff 4736.Apr 8 2015, 5:18 AM

markj retitled this revision from to Fix a possible refcount leak in regen_tmpaddr()..

markj edited the test plan for this revision. (Show Details)

markj updated this object.

Herald added a subscriber: imp. · View Herald TranscriptApr 8 2015, 5:18 AM

markj added reviewers: ae, hrs, bz.Apr 8 2015, 7:52 PM

ae accepted this revision.Apr 9 2015, 8:52 AM

ae edited edge metadata.

This revision is now accepted and ready to land.Apr 9 2015, 8:52 AM

Closed by commit rS281483 (authored by @markj).

Revision Contents
Changeset List

Path

Size

head/

sys/

netinet6/

nd6.c

7 lines

Diff 4799

View Options

Fix a possible refcount leak in regen_tmpaddr().ClosedPublicActions