mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: chalianis1@gmail.com, barebox@lists.infradead.org
Subject: Re: [PATCH] pci: pci-tegra: fix null pointer assignation.
Date: Thu, 27 Nov 2025 12:53:51 +0100	[thread overview]
Message-ID: <aSg7z0GGSgtsQzPV@pengutronix.de> (raw)
In-Reply-To: <7391cf043e0c56d2b52fe7fdd278349229516f45.camel@pengutronix.de>

On Thu, Nov 27, 2025 at 10:19:34AM +0100, Lucas Stach wrote:
> Hi,
> 
> Am Mittwoch, dem 26.11.2025 um 22:40 -0500 schrieb
> chalianis1@gmail.com:
> > From: Chali Anis <chalianis1@gmail.com>
> > 
> > the dev might be null, to be sure we move the dev assignation before
> > the pci parent assignation.
> 
> This isn't worded strongly enough. pcie->dev will absolutely be NULL at
> the point where it is assigned to pci.parent, which seem like a blatant
> bug and I don't know how this did ever work or if we just ignored the
> broken parent device connection.

This was broken by:

commit fd3be9d95f342a3d056a08a8e69fe81fd2a35948
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Tue Mar 26 11:07:37 2024 +0100

    pci: add pci_controller_init()

    Upcoming patches will add a list to struct pci_controller. To make
    sure we have a single point to initialize the list introduce a
    pci_controller_init() and call it from all drivers which use
    register_pci_controller(). Make sure host->parent is set correctly
    before calling register_pci_controller() as that will be needed for
    device tree parsing later.

    Link: https://lore.barebox.org/20240326100746.471532-8-s.hauer@pengutronix.de
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-11-27 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27  3:40 chalianis1
2025-11-27  9:19 ` Lucas Stach
2025-11-27 11:53   ` Sascha Hauer [this message]
2025-11-27 11:54   ` Sascha Hauer
2025-11-27 11:53 ` Sascha Hauer

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=aSg7z0GGSgtsQzPV@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=chalianis1@gmail.com \
    --cc=l.stach@pengutronix.de \
    /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