Otherwise this request will create a useless prkeys file.
Signed-off-by: Benjamin Marzinski
Reviewed-by: Martin Wilck
---
libmpathpersist/mpath_persist_int.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libmpathpersist/mpath_persist_int.c
b/libmpathpersist/mpath_persis
On 09.09.2025 13:47, Milan Broz wrote:
> On 9/9/25 1:18 PM, Ingo Franzki wrote:
>>> Please, revert my patches and run the same test on a clean 6.17.0-rc5 just
>>> to verify that the patches do not introduce the bug.
>>
>> With your patches reverted the combined mode fails the same way as with your
On 2025-09-12 10:08, Ingo Franzki wrote:
On 11.09.2025 17:58, Mikulas Patocka wrote:
On Thu, 11 Sep 2025, Ingo Franzki wrote:
So, it looks like a dm-crypt bug.
Please, revert my patches and run the same test on a clean
6.17.0-rc5 just
to verify that the patches do not introduce the bug.
On 9/9/25 2:23 PM, Ingo Franzki wrote:
On 09.09.2025 14:15, Milan Broz wrote:
On 9/9/25 1:50 PM, Ingo Franzki wrote:
On 09.09.2025 13:47, Milan Broz wrote:
On 9/9/25 1:18 PM, Ingo Franzki wrote:
Please, revert my patches and run the same test on a clean 6.17.0-rc5 just
to verify that the patc
The mpathpersist code has many areas where it does a poor job of
mimicking the behavior of setting up persistent reservations on an
individual device, especially if paths to the multipath device are
missing or unusable. This patchset is aimed at fixing a number of
them. It is a combination of my tw
When you change the reservation key of a registered multipath device,
some of paths might be down or even deleted since you originally
registered the key. libmpathpersist won't be able to change these
registrations. This can be a problem if the path that is down is holding
the reservation. Other no
This commit enables the asynchronous hash interface in dm-integrity.
Signed-off-by: Mikulas Patocka
---
drivers/md/dm-integrity.c | 243 +-
1 file changed, 199 insertions(+), 44 deletions(-)
Index: linux-2.6/drivers/md/dm-integrity.c
On Sat, Sep 20, 2025 at 09:11:02AM -0300, Augusto wrote:
> Hello.
> Thanks for reading that message.
> Please excuse if here not was the correct area to contact you.
> I use Linux with dm-cache writeback. You are the dm cache developer ? If yes
> thanks very much for making it.
> I want report an i
