See also commit 71a1539e3783.
Reported by: syzbot+9b461b6a07a83cc10daa@syzkaller.appspotmail.com
Reported by: syzbot+b6ce0aec16f5fdab3282@syzkaller.appspotmail.com
Differential D35472
rip6: Fix a lock order reversal in rip6_bind() markj on Jun 13 2022, 3:56 PM. Authored by Tags None Referenced Files
Details
See also commit 71a1539e3783. Reported by: syzbot+9b461b6a07a83cc10daa@syzkaller.appspotmail.com
Diff Detail
Event TimelineComment Actions The patch of course brings locking into correct order. However, at a glance I don't see any good reason to lock INP_INFO_WLOCK() for this assignment on a single inp->inp6p_laddr. Maybe this is some feature of IPv6, that I don't know, though. Comment Actions I wondered the same thing. rip6_connect() has the same "feature." I am inclined to leave it alone for now. |