Linux RAID subsystem development
 help / color / mirror / Atom feed
From: EOS - Manlio Morini <morini@eosdev.it>
To: stable@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: [5.15.y] Request to backport c567c86b90d4 (md/raid10 fstrim kernel crash)
Date: Mon, 26 Oct 2026 17:51:16 +0100	[thread overview]
Message-ID: <50c31a4e-9a41-46bf-9c70-ccbc1ed07b2e@eosdev.it> (raw)

Hello,

I'd like to request the backport of the following upstream commit to the 
Linux 5.15.y stable series:

---

c567c86b90d4715081adfe5eb812141a5b6b4883
md: move initialization and destruction of 'io_acct_set' to md.c

---

The regression was introduced in 5.15.181 by commit 4a05f7ae3371 
("md/raid10: fix missing discard IO accounting"), which depends on the 
above commit.

Without this prerequisite, running fstrim on an MD RAID10 array can 
cause a NULL pointer dereference and crash the kernel.

I have reproduced this crash on my Slackware workstation running Linux 
5.15.223.

The issue was independently investigated and fixed by Canonical in 
Ubuntu's 5.15 kernel:

* https://bugs.launchpad.net/bugs/2117395

*https://lists.ubuntu.com/archives/kernel-team/2025-July/161560.html

The prerequisite was also backported to the Linux 6.1.y stable series:

* https://lists.openwall.net/linux-kernel/2025/05/06/1629

My original report:

* 
https://blog.eosdev.it/2025/07/attenzione-fstrim-su-raid-10-crash-del.html

Since this is a reproducible kernel crash caused by a missing dependency 
of an already backported commit, could the necessary fix also be 
considered for the 5.15.y stable series?

Thank you for your work on maintaining the stable kernels.

Best regards,
Manlio Morini


             reply	other threads:[~2026-10-26 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 16:51 EOS - Manlio Morini [this message]
2026-10-26 22:55 ` [5.15.y] Request to backport c567c86b90d4 (md/raid10 fstrim kernel crash) Sasha Levin

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=50c31a4e-9a41-46bf-9c70-ccbc1ed07b2e@eosdev.it \
    --to=morini@eosdev.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=stable@vger.kernel.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