Bug 200991
| Summary: | [patch] do not assert that the new rtentry mutex is not initialized | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | luke.tw | ||||
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | cem, ngie, op | ||||
| Priority: | --- | Keywords: | patch | ||||
| Version: | CURRENT | Flags: | cem:
mfc-stable10-
|
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
A commit references this bug: Author: cem Date: Mon Aug 1 23:07:32 UTC 2016 New revision: 303651 URL: https://svnweb.freebsd.org/changeset/base/303651 Log: rtentry: Initialize rt_mtx with MTX_NEW The "rtentry" zone does not use UMA_ZONE_ZINIT, so it is invalid to assume the mutex's memory will be zero. Without MTX_NEW, garbage backing memory may trigger the "re-initializing a mutex" assertion. PR: 200991 Submitted by: Chang-Hsien Tsai <luke.tw AT gmail.com> Changes: head/sys/net/route.h Thanks! |
Created attachment 157895 [details] rtentry lock patch Similar to r277489, do not assert that the new rtentry mutex is not initialized. The backing memory contains garbage and might trigger the assertion.