From: Stef Walter <stefw@redhat.com>
To: dm-devel@redhat.com
Cc: Stef Walter <stefw@redhat.com>
Subject: [PATCH 0/1] Fix kpart -d regression where matching devices not found
Date: Sat, 6 Oct 2018 09:38:55 +0200 [thread overview]
Message-ID: <20181006073856.15246-1-stefw@redhat.com> (raw)
The Lorax project found a regression in kpartx -d behavior introduced
by the following commit: 9bdfa3eb8e24b668e6c2bb882cddb0ccfe23ed5b
This patch should fix the problem. It's easy to reproduce this problem
(I did it on Fedora 28) with the following commands:
# kpartx -av disk.img
...
# kpartx -dv disk.img
Notice that the loop devices and partition mappings created by the first
command are not cleaned up by the second command.
Stef Walter (1):
kpartx: Use absolute paths to create mappings
kpartx/kpartx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2018-10-06 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 7:38 Stef Walter [this message]
2018-10-06 7:38 ` [PATCH 1/1] kpartx: Use absolute paths to create mappings Stef Walter
2018-10-09 23:21 ` Benjamin Marzinski
-- strict thread matches above, loose matches on Subject: below --
2018-10-09 12:38 [PATCH 0/1] Fix kpart -d regression where matching devices not found Xose Vazquez Perez
2018-10-09 13:35 ` Christophe Varoqui
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=20181006073856.15246-1-stefw@redhat.com \
--to=stefw@redhat.com \
--cc=dm-devel@redhat.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