public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Filip Schauer <f.schauer@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container/manager 0/2] add deny read/write options for device passthrough
Date: Wed, 24 Jul 2024 19:18:53 +0200	[thread overview]
Message-ID: <cf58ddf4-fc28-42ee-9db6-b0e948aef5ee@proxmox.com> (raw)
In-Reply-To: <130170ce-e0d5-4979-a5e8-752f26d9fe7b@proxmox.com>

On 24/07/2024 12:20, Fiona Ebner wrote:
> In the UI, it think it's enough to expose a checkbox for read-only. Use
> cases that deny reads seem a bit esoteric, so I'm not even sure we
> should add deny_read in the back-end before somebody complains. But no
> strong opinion there.


I removed the deny_read checkbox from the UI but there is no harm in
keeping the option in the backend, in case someone ends up needing it.

Superseded by:
https://lists.proxmox.com/pipermail/pve-devel/2024-July/064896.html



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2024-07-24 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 13:15 Filip Schauer
2024-04-29 13:15 ` [pve-devel] [PATCH container 1/2] " Filip Schauer
2024-07-24 10:20   ` Fiona Ebner
2024-04-29 13:15 ` [pve-devel] [PATCH manager 2/2] ui: lxc: " Filip Schauer
2024-07-24 10:20 ` [pve-devel] [PATCH container/manager 0/2] " Fiona Ebner
2024-07-24 17:18   ` Filip Schauer [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=cf58ddf4-fc28-42ee-9db6-b0e948aef5ee@proxmox.com \
    --to=f.schauer@proxmox.com \
    --cc=f.ebner@proxmox.com \
    --cc=pve-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