Linux Device Mapper development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: dm-devel@lists.linux.dev, Mikulas Patocka <mpatocka@redhat.com>,
	Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 6.18 0/4] dm-verity fixes
Date: Tue, 28 Jul 2026 22:19:05 -0700	[thread overview]
Message-ID: <20260729051909.62106-1-ebiggers@kernel.org> (raw)

This series backports some dm-verity fixes to 6.18 that failed to apply
earlier.

The lines added/removed are the same as the upstream commits.  The
conflicts were just in the context.

Eric Biggers (3):
  dm-verity-fec: fix the size of dm_verity_fec_io::erasures
  dm-verity-fec: fix reading parity bytes split across blocks (take 3)
  dm-verity-fec: replace {MAX,MIN}_RSN with {MIN,MAX}_ROOTS

Mikulas Patocka (1):
  dm-verity: fix buffer overflow in FEC calculation

 drivers/md/dm-verity-fec.c | 110 +++++++++++++++++--------------------
 drivers/md/dm-verity-fec.h |   6 +-
 2 files changed, 52 insertions(+), 64 deletions(-)


base-commit: 221fc2f4d0eda59d02af2e751a9282fa013a8e97
-- 
2.55.0


             reply	other threads:[~2026-07-29  5:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  5:19 Eric Biggers [this message]
2026-07-29  5:19 ` [PATCH 6.18 1/4] dm-verity-fec: fix the size of dm_verity_fec_io::erasures Eric Biggers
2026-07-29  5:19 ` [PATCH 6.18 2/4] dm-verity-fec: fix reading parity bytes split across blocks (take 3) Eric Biggers
2026-07-29  5:19 ` [PATCH 6.18 3/4] dm-verity-fec: replace {MAX,MIN}_RSN with {MIN,MAX}_ROOTS Eric Biggers
2026-07-29  5:19 ` [PATCH 6.18 4/4] dm-verity: fix buffer overflow in FEC calculation Eric Biggers
2026-07-30  2:40 ` [PATCH 6.18 0/4] dm-verity fixes 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=20260729051909.62106-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=mpatocka@redhat.com \
    --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