Demi Marie Obenour

This is a case where I wish D-Bus clients sent a `/proc/self` FD at connection. We already know the client’s PID, and can check that it has not been recycled...

> > This is a case where I wish D-Bus clients sent a `/proc/self` FD at connection. We already know the client’s PID, and can check that it has not...

> > Once we have a race-free way to get the client’s `/proc/$PID` FD, we can obtain their AppArmor context from `/proc`, without using `SO_PEERSEC`. For this to work, a...

> Have you taken a look at that? Does that not meet your requirements? I have not, but I believe it does not. I would like there to be a...

> > > Have you taken a look at that? Does that not meet your requirements? > > > > > > I have not, but I believe it does...

> > * XFS does not have good support for large amounts of growth. A filesystem that is created at 5GiB will not perform well if it is later extended...

> This seems like the most challenging part to address, and I don't think we could necessarily resolve it without XFS shrink support. I'll discuss this with the team! This...

> > Quotas allow creating the volume as highly sparse, with a filesystem size much greater than the volume size. > > I understand why someone would want this if...

> I want to make sure I'm understanding your concern appropriately. Are you saying in the no overprovisioning case, you would have to accurately guess your _eventual_ data usage (which...

> Does that sound like it could be helpful for you? Yes, it does. > Just please be aware that this will not help with out of space issues in...