On 06.07.23 14:48, Ziyang Xuan (William) wrote:
(..)
}
out:
release_sock(sk);
+ rtnl_unlock();
Would it also fix the issue when just adding the rtnl_locks to raw_bind() and raw_release() as suggested by you?
This patch just add rtnl_lock in raw_bind() and raw_release(). raw_setsockopt() has rtnl_lock before this. raw_notify()
is under rtnl_lock. My patch has been tested and solved the issue before send. I don't know if it answered your doubts.
My question was whether adding rtnl_locks to raw_bind() and
raw_release() would be enough to fix the issue.
Without introducing the additional ro->dev element!?
Best regards,
Oliver
