From: Kyungwook Boo <bookyungwook@gmail.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH] i40e: fix MMIO write access to an invalid page in i40e_clear_hw
Date: Thu, 6 Mar 2025 18:44:11 +0900 [thread overview]
Message-ID: <76a11baf-e3c1-4b83-bc53-73b74fe1b8e9@gmail.com> (raw)
In-Reply-To: <5cfd4c17-71a8-4bd8-972b-31fc0634f518@intel.com>
On 25. 3. 6. 16:59, Przemek Kitszel wrote:
> On 3/6/25 06:25, Kyungwook Boo wrote:
>> In i40e_clear_hw(), when the device sends a specific input(e.g., 0),
>> an integer underflow in the num_{pf,vf}_int variables can occur,
>> leading to MMIO write access to an invalid page.
>>
>> To fix this, we change the type of the unsigned integer variables
>> num_{pf,vf}_int to signed integers. Additionally, in the for-loop where the
>> integer underflow occurs, we also change the type of the loop variable i to
>> a signed integer.
>>
>> Signed-off-by: Kyungwook Boo <bookyungwook@gmail.com>
>> Signed-off-by: Loktionov, Aleksandr <aleksandr.loktionov@intel.com>
>
> when Alex said "make sure I signed too" he meant:
> "make sure the variable @i is signed too", not the Sign-off ;)
>
> (please wait 24h for the next submission, and also put "iwl-next" after
> the "PATCH" word)
>
>> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
>
> I didn't signed that either
Oh.. I totally misunderstood the comment.
I apologize for mistakenly adding the sign.
>> Link: https://lore.kernel.org/lkml/ffc91764-1142-4ba2-91b6-8c773f6f7095@gmail.com/T/
>> ---
>> drivers/net/ethernet/intel/i40e/i40e_common.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/i40e/i40e_common.c b/drivers/net/ethernet/intel/i40e/i40e_common.c
>> index 370b4bddee44..9a73cb94dc5e 100644
>> --- a/drivers/net/ethernet/intel/i40e/i40e_common.c
>> +++ b/drivers/net/ethernet/intel/i40e/i40e_common.c
>> @@ -817,8 +817,8 @@ int i40e_pf_reset(struct i40e_hw *hw)
>> void i40e_clear_hw(struct i40e_hw *hw)
>> {
>> u32 num_queues, base_queue;
>> - u32 num_pf_int;
>> - u32 num_vf_int;
>> + s32 num_pf_int;
>> + s32 num_vf_int;
>> u32 num_vfs;
>> u32 i, j;
>
> It's fine to move the declaration of @i into the for loop, but
> you have to remove it here, otherwise it's shadowing, which we
> avoid.
>
>> u32 val;
>> @@ -848,18 +848,18 @@ void i40e_clear_hw(struct i40e_hw *hw)
>> /* stop all the interrupts */
>> wr32(hw, I40E_PFINT_ICR0_ENA, 0);
>> val = 0x3 << I40E_PFINT_DYN_CTLN_ITR_INDX_SHIFT;
>> - for (i = 0; i < num_pf_int - 2; i++)
>> + for (s32 i = 0; i < num_pf_int - 2; i++)
>> wr32(hw, I40E_PFINT_DYN_CTLN(i), val);
>> /* Set the FIRSTQ_INDX field to 0x7FF in PFINT_LNKLSTx */
>> val = eol << I40E_PFINT_LNKLST0_FIRSTQ_INDX_SHIFT;
>> wr32(hw, I40E_PFINT_LNKLST0, val);
>> - for (i = 0; i < num_pf_int - 2; i++)
>> + for (s32 i = 0; i < num_pf_int - 2; i++)
>> wr32(hw, I40E_PFINT_LNKLSTN(i), val);
>> val = eol << I40E_VPINT_LNKLST0_FIRSTQ_INDX_SHIFT;
>> for (i = 0; i < num_vfs; i++)
>> wr32(hw, I40E_VPINT_LNKLST0(i), val);
>> - for (i = 0; i < num_vf_int - 2; i++)
>> + for (s32 i = 0; i < num_vf_int - 2; i++)
>> wr32(hw, I40E_VPINT_LNKLSTN(i), val);
>> /* warn the HW of the coming Tx disables */
>
Thank you for reviewing the patch.
I will correct the patch and resubmit it.
Best,
Kyungwook Boo
next prev parent reply other threads:[~2025-03-06 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 5:25 [Intel-wired-lan] [PATCH] i40e: fix MMIO write access to an invalid page in i40e_clear_hw Kyungwook Boo
2025-03-06 7:59 ` Przemek Kitszel
2025-03-06 9:44 ` Kyungwook Boo [this message]
2025-03-06 11:13 ` Loktionov, Aleksandr
2025-03-07 4:10 ` Kyungwook Boo
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=76a11baf-e3c1-4b83-bc53-73b74fe1b8e9@gmail.com \
--to=bookyungwook@gmail.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
/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