From: Milan Broz <gmazyland@gmail.com>
To: "Nuno Gonçalves" <nunog@fr24.com>
Cc: dm-devel@lists.linux.dev, mpatocka@redhat.com
Subject: Re: dm-verity issue on 6.19
Date: Mon, 22 Dec 2025 16:13:05 +0100 [thread overview]
Message-ID: <0cabd3cf-232a-46f4-9ca6-b1df7fe675d5@gmail.com> (raw)
In-Reply-To: <CA+mKM5kC_rPcfOnKrvdJoDPKW3j3ATdouwrJV+Jx8kXa5u-gxg@mail.gmail.com>
On 12/22/25 3:39 PM, Nuno Gonçalves wrote:
> I opened a issue with RAUC after your answer suggests there was no
> regression in user land API.
It was an addition to the status line, it should be "compatible".
That said, we were quite lucky in libcryptsetup to not fail on parse here
(I added support for this field for veritysetup recently) but I can imagine
it could break other code.
For more information, see this patch in 6.19
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ae97648e14f7907f4b0e0b295eb2fdcf43806f9d
Milan
prev parent reply other threads:[~2025-12-22 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 11:57 dm-verity issue on 6.19 Nuno Gonçalves
2025-12-22 14:30 ` Milan Broz
2025-12-22 14:39 ` Nuno Gonçalves
2025-12-22 15:13 ` Milan Broz [this message]
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=0cabd3cf-232a-46f4-9ca6-b1df7fe675d5@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=mpatocka@redhat.com \
--cc=nunog@fr24.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