From: Jon Hunter <jonathanh@nvidia.com>
To: Niklas Cassel <cassel@kernel.org>,
Hans Zhang <18255117159@163.com>,
manivannan.sadhasivam@linaro.org
Cc: kw@linux.com, kishon@kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rockswang7@gmail.com,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [v11 2/2] misc: pci_endpoint_test: Fix overflow of bar_size
Date: Wed, 22 Jan 2025 06:03:04 +0000 [thread overview]
Message-ID: <11b41380-9ab1-4628-8e1b-2a71a7b92a0c@nvidia.com> (raw)
In-Reply-To: <87FA054A-053E-4E73-94D7-CB9F4F655053@kernel.org>
On 21/01/2025 20:31, Niklas Cassel wrote:
>
>
> On 21 January 2025 18:46:43 CET, Jon Hunter <jonathanh@nvidia.com> wrote:
>> Hi Hans,
>>
>> On 09/01/2025 09:45, Hans Zhang wrote:
>>> With 8GB BAR2, running pcitest -b 2 fails with "TEST FAILED".
>>>
>>> The return value of the `pci_resource_len` interface is not an integer.
>>> Using `pcitest` with an 8GB BAR2, the bar_size of integer type will
>>> overflow.
>>>
>>> Change the data type of bar_size from integer to resource_size_t, to fix
>>> the above issue.
>>>
>>> Signed-off-by: Hans Zhang <18255117159@163.com>
>>> Suggested-by: Niklas Cassel <cassel@kernel.org>
>>> Reviewed-by: Niklas Cassel <cassel@kernel.org>
>>> ---
>>> Changes since v10:
>>> https://lore.kernel.org/linux-pci/20250108080951.1700230-3-18255117159@163.com/
>>>
>>> - Replace do_div with the div_u64 API.
>>>
>>> Changes since v8-v9:
>>> https://lore.kernel.org/linux-pci/20250104151652.1652181-1-18255117159@163.com/
>>>
>>> - Split the patch.
>>>
>>> Changes since v4-v7:
>>> https://lore.kernel.org/linux-pci/20250102120222.1403906-1-18255117159@163.com/
>>>
>>> - Fix 32-bit OS warnings and errors.
>>> - Fix undefined reference to `__udivmoddi4`
>>>
>>> Changes since v3:
>>> https://lore.kernel.org/linux-pci/20241221141009.27317-1-18255117159@163.com/
>>>
>>> - The patch subject were modified.
>>>
>>> Changes since v2:
>>> https://lore.kernel.org/linux-pci/20241220075253.16791-1-18255117159@163.com/
>>>
>>> - Fix "changes" part goes below the --- line
>>> - The patch commit message were modified.
>>>
>>> Changes since v1:
>>> https://lore.kernel.org/linux-pci/20241217121220.19676-1-18255117159@163.com/
>>>
>>> - The patch subject and commit message were modified.
>>> ---
>>> drivers/misc/pci_endpoint_test.c | 5 +++--
>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
>>> index f78c7540c52c..0f6291801078 100644
>>> --- a/drivers/misc/pci_endpoint_test.c
>>> +++ b/drivers/misc/pci_endpoint_test.c
>>> @@ -280,10 +280,11 @@ static int pci_endpoint_test_bar_memcmp(struct pci_endpoint_test *test,
>>> static bool pci_endpoint_test_bar(struct pci_endpoint_test *test,
>>> enum pci_barno barno)
>>> {
>>> - int j, bar_size, buf_size, iters;
>>> + int j, buf_size, iters;
>>> void *write_buf __free(kfree) = NULL;
>>> void *read_buf __free(kfree) = NULL;
>>> struct pci_dev *pdev = test->pdev;
>>> + resource_size_t bar_size;
>>> if (!test->bar[barno])
>>> return false;
>>> @@ -307,7 +308,7 @@ static bool pci_endpoint_test_bar(struct pci_endpoint_test *test,
>>> if (!read_buf)
>>> return false;
>>> - iters = bar_size / buf_size;
>>> + iters = div_u64(bar_size, buf_size);
>>> for (j = 0; j < iters; j++)
>>> if (pci_endpoint_test_bar_memcmp(test, barno, buf_size * j,
>>> write_buf, read_buf, buf_size))
>>
>>
>> This change breaks building the kernel with GCC v7 and I see ...
>>
>> ERROR: modpost: "__aeabi_uldivmod" [drivers/misc/pci_endpoint_test.ko] undefined!
>> ERROR: modpost: "__aeabi_ldivmod" [drivers/misc/pci_endpoint_test.ko] undefined!
>>
>> I know that this is an old GCC version, but this is a farm builder and the kernel still indicates that GCC v5.1 is still supported [0].
>>
>
> Hmm.. div_u64() should work on gcc 5.1.
>
> Out of curiosity, is there any difference if you add:
>
> #include <linux/math64.h>
> to
> drivers/misc/pci_endpoint_test.c ?
I tried the above, but I am still seeing the same problem. So
unfortunately, that did not fix it.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2025-01-22 6:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 9:45 [v11 0/2] misc: pci_endpoint_test: Fix overflow of bar_size Hans Zhang
2025-01-09 9:45 ` [v11 1/2] misc: pci_endpoint_test: Remove the "remainder" code Hans Zhang
2025-01-15 16:58 ` Manivannan Sadhasivam
2025-01-09 9:45 ` [v11 2/2] misc: pci_endpoint_test: Fix overflow of bar_size Hans Zhang
2025-01-15 16:58 ` Manivannan Sadhasivam
2025-01-15 17:05 ` Niklas Cassel
2025-01-16 2:03 ` Krzysztof Wilczyński
2025-01-16 9:36 ` Niklas Cassel
2025-01-16 9:38 ` Niklas Cassel
2025-01-17 8:49 ` Krzysztof Wilczyński
2025-01-21 17:46 ` Jon Hunter
2025-01-21 20:23 ` Bjorn Helgaas
2025-01-21 20:31 ` Niklas Cassel
2025-01-22 6:03 ` Jon Hunter [this message]
2025-01-22 10:07 ` Niklas Cassel
2025-01-22 10:26 ` Arnd Bergmann
2025-01-22 11:18 ` Jon Hunter
2025-01-23 8:10 ` Niklas Cassel
2025-01-15 14:02 ` [v11 0/2] " Krzysztof Wilczyński
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=11b41380-9ab1-4628-8e1b-2a71a7b92a0c@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=18255117159@163.com \
--cc=arnd@arndb.de \
--cc=cassel@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rockswang7@gmail.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