All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Hans Zhang <18255117159@163.com>
Cc: manivannan.sadhasivam@linaro.org, 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
Subject: Re: [v8] misc: pci_endpoint_test: Fix overflow of bar_size
Date: Tue, 7 Jan 2025 12:47:40 +0100	[thread overview]
Message-ID: <Z30UXDVZi3Re_J9p@ryzen> (raw)
In-Reply-To: <270783b7-70c6-49d5-8464-fb542396e2dd@163.com>

On Tue, Jan 07, 2025 at 07:43:26PM +0800, Hans Zhang wrote:
> 
> 
> On 2025/1/7 19:33, Niklas Cassel wrote:
> > > Hi Niklas,
> > > 
> > > resource_size_t bar_size;
> > > remain = do_div((u64)bar_size, buf_size);
> > > 
> > > It works for the arm platform.
> > > 
> > > arch/arm/include/asm/div64.h
> > > static inline uint32_t __div64_32(uint64_t *n, uint32_t base)
> > > {
> > > 	register unsigned int __base      asm("r4") = base;
> > > 	register unsigned long long __n   asm("r0") = *n;
> > > 	register unsigned long long __res asm("r2");
> > > 	unsigned int __rem;
> > > 	asm(	__asmeq("%0", "r0")
> > > 		__asmeq("%1", "r2")
> > > 		__asmeq("%2", "r4")
> > > 		"bl	__do_div64"
> > > 		: "+r" (__n), "=r" (__res)
> > > 		: "r" (__base)
> > > 		: "ip", "lr", "cc");
> > > 	__rem = __n >> 32;
> > > 	*n = __res;
> > > 	return __rem;
> > > }
> > > #define __div64_32 __div64_32
> > > 
> > > #define do_div(n, base) __div64_32(&(n), base)
> > > 
> > > 
> > > For X86 platforms, do_div is a macro definition, and the first parameter
> > > does not define its type. If the macro definition is replaced directly, an
> > > error will be reported in the ubuntu20.04 release.
> > 
> > What is the error?
> > 
> > We don't need to use do_div().
> > The current code that does normal / and % works fine on both
> > 32-bit and 64-bit if you just do:
> > 
> >   static bool pci_endpoint_test_bar(struct pci_endpoint_test *test,
> >                                    enum pci_barno barno)
> >   {
> > -       int j, bar_size, buf_size, iters, remain;
> > +       int j, buf_size, iters, remain;
> >          void *write_buf __free(kfree) = NULL;
> >          void *read_buf __free(kfree) = NULL;
> >          struct pci_dev *pdev = test->pdev;
> > +       u64 bar_size;
> > 
> > No?
> 
> 
> Hi Niklas,
> 
> Please look at the robot compilation error.
> 
> https://patchwork.kernel.org/project/linux-pci/patch/20241231065500.168799-1-18255117159@163.com/
> 
> drivers/misc/pci_endpoint_test.c:315: undefined reference to `__udivmoddi4'

That error was for your patch that changed bar_size to resource_size_t,
which is typedefed to phys_addr_t, which can be either 32-bits or 64-bits
on 32-bit systems (depending on CONFIG_X86_PAE).

I was suggesting to just change it to u64, so it will unconditionally be
64-bits.


Kind regards,
Niklas

  reply	other threads:[~2025-01-07 11:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04 15:16 [v8] misc: pci_endpoint_test: Fix overflow of bar_size Hans Zhang
2025-01-06 11:49 ` Niklas Cassel
2025-01-06 13:56   ` Hans Zhang
2025-01-06 15:32   ` Hans Zhang
2025-01-07 10:32     ` Niklas Cassel
2025-01-07 11:27       ` Hans Zhang
2025-01-07 11:33         ` Niklas Cassel
2025-01-07 11:43           ` Hans Zhang
2025-01-07 11:47             ` Niklas Cassel [this message]
2025-01-07 12:09               ` Hans Zhang
2025-01-07 13:36                 ` Niklas Cassel
2025-01-07 15:44               ` Hans Zhang
2025-01-07 15:57                 ` Niklas Cassel
2025-01-07 16:12                   ` Hans Zhang
2025-01-08 14:10                   ` Arnd Bergmann
2025-01-08 14:13                     ` Niklas Cassel
2025-01-09  2:59                       ` Hans Zhang
2025-01-09  6:29                         ` Arnd Bergmann
2025-01-09  9:19                           ` Hans Zhang

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=Z30UXDVZi3Re_J9p@ryzen \
    --to=cassel@kernel.org \
    --cc=18255117159@163.com \
    --cc=arnd@arndb.de \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.