Re: [RFC 16/16] lpfc: vmid: Introducing vmid in io path.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/6/2020 9:26 AM, Muneendra Kumar M wrote:
Hi Paolo,

3.As part of this interface user/deamon will provide the details of VM such
as UUID,PID on VM creation to the transport .
The VM process, or the container process, is likely to be unprivileged and
cannot obtain the permissions needed to do this; therefore, you need to
cope with the situation where there is no PID yet in the cgroup, because
the tool >that created the VM or container might be initializing the
cgroup, but it might not have started the VM yet.  In that case there would
be no PID.

Agreed.A
small doubt. If the VM is started (running)then we can have the PID and   we
can use the  PID?
Note: I'm not worried about this. The transport/lldd would be fine with the device being used for a while with no blkcg attribute set. When it finally does get set, it would initiate the creation of the corresponding fc wire app_id. This will be something normal.

-- james




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]

  Powered by Linux