From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg()
Date: Fri, 15 Apr 2022 13:55:06 -0700 [thread overview]
Message-ID: <248da3d7-cb00-14b6-12f0-6bb9fda6d532@intel.com> (raw)
In-Reply-To: <YlldsfrRJURXpp5d@boxer>
On 4/15/2022 4:57 AM, Maciej Fijalkowski wrote:
<snip>
>>> diff --git a/drivers/net/ethernet/intel/ice/ice_virtchnl.c b/drivers/net/ethernet/intel/ice/ice_virtchnl.c
>>> index 5612c032f15a..553287a75b50 100644
>>> --- a/drivers/net/ethernet/intel/ice/ice_virtchnl.c
>>> +++ b/drivers/net/ethernet/intel/ice/ice_virtchnl.c
>>> @@ -3625,44 +3625,39 @@ void ice_vc_process_vf_msg(struct ice_pf *pf, struct ice_rq_event_info *event)
>>> return;
>>> }
>>>
>>> + mutex_lock(&vf->cfg_lock);
>>> +
>>> /* Check if VF is disabled. */
>>> if (test_bit(ICE_VF_STATE_DIS, vf->vf_states)) {
>>> err = -EPERM;
>>> - goto error_handler;
>>> - }
>>> -
>>> - ops = vf->virtchnl_ops;
>>> -
>>> - /* Perform basic checks on the msg */
>>> - err = virtchnl_vc_validate_vf_msg(&vf->vf_ver, v_opcode, msg, msglen);
>>> - if (err) {
>>> - if (err == VIRTCHNL_STATUS_ERR_PARAM)
>>> - err = -EPERM;
>>> - else
>>> - err = -EINVAL;
>>> + } else {
>>> + /* Perform basic checks on the msg */
>>> + err = virtchnl_vc_validate_vf_msg(&vf->vf_ver, v_opcode, msg,
>>> + msglen);
>>> + if (err) {
>>> + if (err == VIRTCHNL_STATUS_ERR_PARAM)
>>> + err = -EPERM;
>>> + else
>>> + err = -EINVAL;
>>> + }
>> The chunk above feels a bit like unnecessary churn, no?
>> Couldn't this patch be simply focused only on extending critical section?
Agree, this doesn't seem related to the fix.
Thanks,
Tony
>>> }
>>> -
>>> -error_handler:
>>> if (err) {
>>> ice_vc_send_msg_to_vf(vf, v_opcode, VIRTCHNL_STATUS_ERR_PARAM,
>>> NULL, 0);
>>> dev_err(dev, "Invalid message from VF %d, opcode %d, len %d, error %d\n",
>>> vf_id, v_opcode, msglen, err);
>>> - ice_put_vf(vf);
>>> - return;
>>> + goto finish;
>>> }
>>>
>>> - mutex_lock(&vf->cfg_lock);
>>> -
>>> if (!ice_vc_is_opcode_allowed(vf, v_opcode)) {
>>> ice_vc_send_msg_to_vf(vf, v_opcode,
>>> VIRTCHNL_STATUS_ERR_NOT_SUPPORTED, NULL,
>>> 0);
>>> - mutex_unlock(&vf->cfg_lock);
>>> - ice_put_vf(vf);
>>> - return;
>>> + goto finish;
>>> }
>>>
>>> + ops = vf->virtchnl_ops;
>>> +
>>> switch (v_opcode) {
>>> case VIRTCHNL_OP_VERSION:
>>> err = ops->get_ver_msg(vf, msg);
>>> @@ -3773,6 +3768,7 @@ void ice_vc_process_vf_msg(struct ice_pf *pf, struct ice_rq_event_info *event)
>>> vf_id, v_opcode, err);
>>> }
>>>
>>> +finish:
>>> mutex_unlock(&vf->cfg_lock);
>>> ice_put_vf(vf);
>>> }
>>> --
>>> 2.35.1
>>>
>>> _______________________________________________
>>> Intel-wired-lan mailing list
>>> Intel-wired-lan at osuosl.org
>>> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-04-15 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:22 [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg() Ivan Vecera
2022-04-15 11:55 ` Maciej Fijalkowski
2022-04-15 11:57 ` Maciej Fijalkowski
2022-04-15 13:53 ` Alexander Lobakin
2022-04-15 20:55 ` Tony Nguyen [this message]
2022-04-16 11:30 ` Ivan Vecera
2022-04-18 18:10 ` Tony Nguyen
2022-04-19 14:23 ` Ivan Vecera
2022-04-15 16:38 ` Ivan Vecera
2022-04-15 18:31 ` Keller, Jacob E
2022-04-15 20:53 ` Tony Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=248da3d7-cb00-14b6-12f0-6bb9fda6d532@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox