public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Reiter <s.reiter@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH 0/7] fuse_loop cleanups and named mappings
Date: Wed,  7 Oct 2020 13:53:01 +0200	[thread overview]
Message-ID: <20201007115308.6275-1-s.reiter@proxmox.com> (raw)

First three patches are independent cleanups/documentation.

Patch 4 is the meat of the matter, switching over to using names generated from
the mapped image to identify mappings. This allows easier unmap by having a
specific tab-completion handler. Also allows listing all current mappings and
where they are mapped to with the 'unmap' command without parameters.

The last 3 patches are for better cleanup handling. With all three in place I
could not come up with a realistic situation in which a user would have to rely
on external tools to cancel a connection or clean up.


proxmox-backup: Stefan Reiter (7):
  format: fix typo in function name
  fuse_loop: add documentation
  loopdev: add module doc
  mount/map: use names for map/unmap for easier use
  fuse_loop: add automatic cleanup of run files and dangling instances
  fuse_loop: wait for instance to close after killing
  fuse_loop: handle unmap on crashed instance

 src/bin/proxmox-backup-client.rs       |   6 +-
 src/bin/proxmox_backup_client/mount.rs |  58 +++++-
 src/client/backup_writer.rs            |   2 +-
 src/tools/format.rs                    |   4 +-
 src/tools/fuse_loop.rs                 | 257 ++++++++++++++++++++-----
 src/tools/loopdev.rs                   |   2 +
 6 files changed, 268 insertions(+), 61 deletions(-)

-- 
2.20.1




             reply	other threads:[~2020-10-07 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 11:53 Stefan Reiter [this message]
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 1/7] format: fix typo in function name Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 2/7] fuse_loop: add documentation Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 3/7] loopdev: add module doc Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 4/7] mount/map: use names for map/unmap for easier use Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 5/7] fuse_loop: add automatic cleanup of run files and dangling instances Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 6/7] fuse_loop: wait for instance to close after killing Stefan Reiter
2020-10-07 11:53 ` [pbs-devel] [PATCH proxmox-backup 7/7] fuse_loop: handle unmap on crashed instance Stefan Reiter
2020-10-08  6:45 ` [pbs-devel] applied: [PATCH 0/7] fuse_loop cleanups and named mappings Dietmar Maurer

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=20201007115308.6275-1-s.reiter@proxmox.com \
    --to=s.reiter@proxmox.com \
    --cc=pbs-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal