public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: kingdix10@qq.com
To: helgaas@kernel.org
Cc: bhelgaas@google.com, kingdix10@qq.com, kw@linux.com,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, lpieralisi@kernel.org,
	manivannan.sadhasivam@linaro.org, marek.vasut+renesas@gmail.com,
	prabhakar.csengg@gmail.com,
	prabhakar.mahadev-lad.rj@bp.renesas.com, robh@kernel.org,
	yoshihiro.shimoda.uh@renesas.com
Subject: Re: Re: [PATCH v4] PCI: rcar-ep: Fix the issue of the name parameter when calling devm_request_mem_region
Date: Wed,  8 Jan 2025 12:59:11 +0800	[thread overview]
Message-ID: <tencent_D3EAA236B531BDF17998832CC18EC36CBC07@qq.com> (raw)
In-Reply-To: <20250107225653.GA189000@bhelgaas>

On Tue, 2025-01-07 at 16:56 -0600, Bjorn Helgaas wrote:
> On Tue, Jan 07, 2025 at 09:51:23PM +0800, kingdix10@qq.com wrote:
> > From: King Dix <kingdix10@qq.com>
> > 
> > When using devm_request_mem_region to request a resource, if the
> > passed
> > variable is a stack string variable, it will lead to an oops issue
> > when
> > executing the command cat /proc/iomem.
> > 
> > Fix this by replacing outbound_name with the name of the previously
> > requested resource.
> 
> Thanks a lot for doing this work!
> 
> Add "()" after function names in subject and commit log.
> 

Thanks for your review. I will fix the issue right now.

> Please include a couple lines of the oops message to help people
> connect the problem with the fix.
> 

This is a potential issue that I found while analyzing the code. I don't
have the conditions to reproduce this issue, but I can write a driver to
reproduce this issue in QEMU and obtain logs for reference.

> I suppose you found this by tripping over it.  Can you look through
> the other callers of devm_request_mem_region() and similar
> interfaces,
> at least in drivers/pci, and make sure there are no other similar
> errors?
> 

I've already checked that there are only a few calls of 
devm_request_mem_region() under the drivers/pci directory, and they
are all correct. 

> > Fixes: 2a6d0d63d999 ("PCI: rcar: Add endpoint mode support")
> > 
> > Signed-off-by: King Dix <kingdix10@qq.com>
> > Reviewed-by: Lad Prabhakar
> > <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > Tested-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > ---
> > Changes in v4:
> >   - Add more information to the comment.
> > Changes in v3:
> >   - Fix the spelling issue in the comment.
> > Changes in v2:
> >   - Fix the code indentation issue.
> > ---
> >  drivers/pci/controller/pcie-rcar-ep.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/pci/controller/pcie-rcar-ep.c
> > b/drivers/pci/controller/pcie-rcar-ep.c
> > index 047e2cef5afc..c5e0d025bc43 100644
> > --- a/drivers/pci/controller/pcie-rcar-ep.c
> > +++ b/drivers/pci/controller/pcie-rcar-ep.c
> > @@ -107,7 +107,7 @@ static int
> > rcar_pcie_parse_outbound_ranges(struct rcar_pcie_endpoint *ep,
> >  		}
> >  		if (!devm_request_mem_region(&pdev->dev, res->start,
> >  					     resource_size(res),
> > -					     outbound_name)) {
> > +					     res->name)) {
> >  			dev_err(pcie->dev, "Cannot request memory region %s.\n",
> >  				outbound_name);
> >  			return -EIO;
> > -- 
> > 2.43.0
> > 


  reply	other threads:[~2025-01-08  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 13:51 [PATCH v4] PCI: rcar-ep: Fix the issue of the name parameter when calling devm_request_mem_region kingdix10
2025-01-07 22:56 ` Bjorn Helgaas
2025-01-08  4:59   ` kingdix10 [this message]
2025-01-08 10:45     ` Biju Das
2025-01-08 10:50       ` Lad, Prabhakar
2025-01-08 10:57         ` Biju Das
2025-01-08 11:09           ` Geert Uytterhoeven
2025-01-08 11:13             ` Biju Das
2025-01-09  0:45               ` kingdix10

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=tencent_D3EAA236B531BDF17998832CC18EC36CBC07@qq.com \
    --to=kingdix10@qq.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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