diff options
| author | martin <martin@NetBSD.org> | 2020-04-23 13:31:43 +0000 |
|---|---|---|
| committer | martin <martin@NetBSD.org> | 2020-04-23 13:31:43 +0000 |
| commit | 7e07bcdb6bd4e9f5c0076d8c4139fa2967931305 (patch) | |
| tree | 5e34578b148c5b3b26d51d1a8683a89a26080a61 /sys/dev/microcode/run | |
| parent | 1332d5f25c9d624c0a81425fe83b6aac7a783c4d (diff) | |
Pull up following revision(s) (requested by roy in ticket #845):
sys/netinet6/nd6_nbr.c: revision 1.178
inet6: nd6_na_input() now considers ln_state <= ND6_LLINFO_INCOMPLETE
Otherwise if ln_state != ND6_LLINFO_INCOMPLETE and the is no lladdr
and this message was solicited then ln_state is set to ND6_LLINFO_REACHABLE
which could then cause a panic in nd6_resolve().
If ln_state > ND6_LLINFO_INCOMPLETE then it's assumed we have a lladdr.
Potentially this could have been triggered by the introduction of
ND6_LLINFO_PURGE in nd6.c r1.143 but also by the re-introduction of
ND6_LLINFO_INCOMPLETE in nd6.c r1.263.
Depending on the timing, it's technically possible to receive such
a message after the llentry is created with ND6_LLINFO_NOSTATE.
Diffstat (limited to 'sys/dev/microcode/run')
0 files changed, 0 insertions, 0 deletions
