On Thu, Feb 02, 2023 at 02:56:34PM -0500, Mike Snitzer wrote:
> On Thu, Feb 02 2023 at 1:41P -0500,
> Demi Marie Obenour wrote:
>
> > On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> > > On Wed, Jan 25 2023 at 10:33P -0500,
> > > Demi Marie Obenour wrote:
> > >
> > > > This
On Thu, Feb 02 2023 at 1:41P -0500,
Demi Marie Obenour wrote:
> On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> > On Wed, Jan 25 2023 at 10:33P -0500,
> > Demi Marie Obenour wrote:
> >
> > > This work aims to allow userspace to create and destroy block devices
> > > in a
On Thu, Feb 02, 2023 at 11:50:37AM -0500, Mike Snitzer wrote:
> On Wed, Jan 25 2023 at 10:33P -0500,
> Demi Marie Obenour wrote:
>
> > This work aims to allow userspace to create and destroy block devices
> > in a race-free and leak-free way,
>
> "race-free and leak-free way" implies there both
On Wed, Jan 25 2023 at 10:33P -0500,
Demi Marie Obenour wrote:
> This work aims to allow userspace to create and destroy block devices
> in a race-free and leak-free way,
"race-free and leak-free way" implies there both races and leaks in
existing code. You're making claims that are likely very
This work aims to allow userspace to create and destroy block devices
in a race-free and leak-free way, and to allow them to be exposed to
other Xen VMs via blkback without leaks or races. It’s marked as RFC
for a few reasons:
- The code has been only lightly tested. It might be unstable or
