Linux EDAC development
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: bp@alien8.de, tony.luck@intel.com
Cc: dinguyen@kernel.org, rounakdas2025@gmail.com,
	niravkumar.l.rabara@altera.com, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 00/10] EDAC/altera: Address sashiko reviews part 1
Date: Mon, 27 Jul 2026 08:24:06 -0500	[thread overview]
Message-ID: <20260727132416.807230-1-dinguyen@kernel.org> (raw)

This is the first set of patches addressing sashiko reviews. I've tried
to the best of my ability to decipher hallucinations and actually bugs
found. There are a few more and I anticipate another series, but I wanted
to keep the series small and handle the most critical bugs found first.

The most important patch is in this series is "EDAC/altera: Add
suppress_bind_attrs so driver cannot get unbound". Because this driver
never tested against bind/unbind, this bug was not observed. Without
this patch, an unbind/bind would cause the system to crash.

Thanks,
Dinh

Dinh Nguyen (10):
  EDAC/altera: Fix NULL of_node dereference altr_edac_device_probe()
  EDAC/altera: Fix use-after-free in error paths
  EDAC/altera: Guard against NULL match data in altr_sdram_probe()
  EDAC/altera: Fix IRQ domain leak on platform_get_irq() failure
  EDAC/altera: Fix code leak on dci allocation failure
  EDAC/altera: Add suppress_bind_attrs so driver cannot get unbound
  EDAC/altera: Drop __init from ECC setup paths for re-probe safety
  EDAC/altera: Skip ECC memory init if already initialized
  EDAC/altera: Detach sb_irq handler when db_irq setup fails
  EDAC/altera: Fix error cleanup path in altr_edac_device_probe()

 drivers/edac/altera_edac.c | 118 ++++++++++++++++++++++++-------------
 1 file changed, 77 insertions(+), 41 deletions(-)

-- 
2.42.0.411.g813d9a9188


             reply	other threads:[~2026-07-27 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 13:24 Dinh Nguyen [this message]
2026-07-27 13:24 ` [PATCH 01/10] EDAC/altera: Fix NULL of_node dereference altr_edac_device_probe() Dinh Nguyen
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=20260727132416.807230-1-dinguyen@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=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