mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] EDAC urgent for v7.3-rc6
Date: Sat, 3 Oct 2026 20:59:29 -0700	[thread overview]
Message-ID: <20261004035929.GAasHPIYlVqxw08xmc@fat_crate.local> (raw)

Hi Linus,

please pull the EDAC fixes lineup for v7.3-rc6.

This is more of the new normal of LLM-induced fixes of error paths. Oh well,
they should be done eventually and hopefully we'll be back to normal
soon-ish... one would hope... :-P

Thx.

---

The following changes since commit 93f51579e7df248780214094418f205253383cc5:

  Linux 7.3-rc4 (2026-09-20 13:48:15 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/edac_urgent_for_v7.3_rc6

for you to fetch changes up to 5f43a2d35d5e748c09a50a98fc766dc95bb3a6bd:

  EDAC/versalnet: Drop remote processor handle refcount on driver removal (2026-09-27 14:05:10 -0700)

----------------------------------------------------------------
- In versalnet_edac, properly release a remote processor reference which was
  acquired at probe time, on memory controller instance remove

- A handful of Altera EDAC driver fixes:

  - Fix device node reference leaks covering both the success path and the
    various error paths, and route the single-bit setup function through the
    common exit label

  - Fix a use-after-free by releasing the devres group before freeing the
    control info structure in the error paths, since managed IRQ handlers
    could reference the freed dci struct if they fire at just the right time

  - Fix a memory leak by freeing the allocated control info structure when the
    devres group open fails in the Altera SDMMC setup path

  - Remove the __init marking from the Altera Arria10 setup paths and their
    helpers so they remain safely callable at runtime, including after
    deferred or re-triggered probing

  - Prevent the Altera driver from being unbound by removing their ->remove
    callbacks and marking them to suppress bind/unbind sysfs attributes, since
    unbinding could erase active system memory

----------------------------------------------------------------
Dinh Nguyen (4):
      EDAC/altera: Do not allow driver unbinding
      EDAC/altera: Drop __init from ECC setup paths for re-probe safety
      EDAC/altera: Fix memory leak on dci allocation failure
      EDAC/altera: Fix use-after-free in error paths

Guangshuo Li (1):
      EDAC/versalnet: Drop remote processor handle refcount on driver removal

Rounak Das (1):
      EDAC/altera: Fix device node reference leaks in the SDMMC ECC setup

 drivers/edac/altera_edac.c    | 67 ++++++++++++++++++++++---------------------
 drivers/edac/versalnet_edac.c |  1 +
 2 files changed, 36 insertions(+), 32 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2026-10-04  3:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04  3:59 Borislav Petkov [this message]
2026-10-04  4:20 ` pr-tracker-bot

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=20261004035929.GAasHPIYlVqxw08xmc@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®