Linux EDAC development
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: tony.luck@intel.com, rounakdas2025@gmail.com,
	niravkumar.l.rabara@altera.com, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 01/10] EDAC/altera: Fix NULL of_node dereference altr_edac_device_probe()
Date: Fri, 31 Jul 2026 08:49:35 -0500	[thread overview]
Message-ID: <79e35eae-5977-4da4-a0d8-4491b823a49f@kernel.org> (raw)
In-Reply-To: <20260728185638.GAamj7ZjiuriHIBjTw@fat_crate.local>



On 7/28/26 13:56, Borislav Petkov wrote:
> On Mon, Jul 27, 2026 at 08:24:07AM -0500, Dinh Nguyen wrote:
>> In altr_edac_device_probe() dereferenced pdev->dev.of_node and
>> of_match_node() before validating it,
> 
> How did that AI let you fumble that sentence? :-P

sorry about that...

> 
>> which could cause a NULL pointer
>> dereference when the device tree node is missing. Check the result for
>> a NULL and bail out with -ENODEV before using it.
>>
>> Assisted-by: Cursor:claude-4.8-opus
>> Fixes: c3eea1942a16 ("EDAC, altera: Add Altera L2 cache and OCRAM support")
>> Closes: https://sashiko.dev/#/patchset/20260719211238.589402-1-rosenp%40gmail.com
> 
> So the AI review for this one here is this one, I think:
> 
> "This isn't a bug introduced by this patch, but can np be NULL here if the
> driver is bound via sysfs?
> If a privileged user unbinds and rebinds the driver via sysfs to a platform
> device that lacks an of_node, pdev->dev.of_node will be NULL, which would
> cause an unconditional dereference when accessing np->name."
> 
> Can that happen?

I don't think this can ever happen. The SoCFPGA platform is strictly OF 
enabled, so not having an of_node would be impossible.

Let me rework this down some more. Sorry for the noise!

Dinh

  reply	other threads:[~2026-07-31 13:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 13:24 [PATCH 00/10] EDAC/altera: Address sashiko reviews part 1 Dinh Nguyen
2026-07-27 13:24 ` [PATCH 01/10] EDAC/altera: Fix NULL of_node dereference altr_edac_device_probe() Dinh Nguyen
2026-07-28 18:56   ` Borislav Petkov
2026-07-31 13:49     ` Dinh Nguyen [this message]
2026-07-27 13:24 ` [PATCH 02/10] EDAC/altera: Fix use-after-free in error paths Dinh Nguyen
2026-07-27 13:24 ` [PATCH 03/10] EDAC/altera: Guard against NULL match data in altr_sdram_probe() Dinh Nguyen
2026-07-27 13:24 ` [PATCH 04/10] EDAC/altera: Fix IRQ domain leak on platform_get_irq() failure Dinh Nguyen
2026-07-27 13:24 ` [PATCH 05/10] EDAC/altera: Fix code leak on dci allocation failure Dinh Nguyen
2026-07-27 13:24 ` [PATCH 06/10] EDAC/altera: Add suppress_bind_attrs so driver cannot get unbound Dinh Nguyen
2026-07-27 13:24 ` [PATCH 07/10] EDAC/altera: Drop __init from ECC setup paths for re-probe safety Dinh Nguyen
2026-07-27 13:24 ` [PATCH 08/10] EDAC/altera: Skip ECC memory init if already initialized Dinh Nguyen
2026-07-27 13:24 ` [PATCH 09/10] EDAC/altera: Detach sb_irq handler when db_irq setup fails Dinh Nguyen
2026-07-27 13:24 ` [PATCH 10/10] EDAC/altera: Fix error cleanup path in altr_edac_device_probe() Dinh Nguyen

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=79e35eae-5977-4da4-a0d8-4491b823a49f@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niravkumar.l.rabara@altera.com \
    --cc=rounakdas2025@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@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