From: Michael Chan <michael.c...@broadcom.com> Date: Wed, 25 Jan 2017 02:55:06 -0500
> There are 2 function calls from bnxt_sp_task() that have buggy RTNL > usage. These 2 functions take RTNL lock under some conditions, but > some callers (such as open, ethtool) have already taken RTNL. These > 3 patches fix the issue by making it clear that callers must take > RTNL. If the caller is bnxt_sp_task() which does not automatically > take RTNL, we add a common scheme for bnxt_sp_task() to call these > functions properly under RTNL. Series applied, thanks Michael. You can sprinkle some ASSERT_RTNL(); in the functions that require RTNL to be held if you like.