summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2021-07-07 11:08:41 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-07-08 14:58:28 +0100
commita16d7d2ec63f911657330dd1df9c8cb069bbd5ee (patch)
tree0837a328f487521c4abe218903ced20f7f58de5e /meta-yocto-bsp
parentbdc5f4e892f36d90737e87192ab3f2c30d8dbdd9 (diff)
downloadpoky-a16d7d2ec63f911657330dd1df9c8cb069bbd5ee.tar.gz
runqemu: Remove potential lock races around tap device handling
The qemu tap device handling is potentially race ridden. We pass the fd to the main qemu subprocess which is good as it means the lock is held as long as the qemu process exists. This means we shouldn't unlock it ourselves though, only close the file. We also can't delete the file as we have no idea if qemu is still using it. We could try and obtain an exclusive new lock, then the file would be safe to unlink but it doesn't seem worth it. Also fix the same issue in the port lock code. (From OE-Core rev: 2a87bddabf816d09ec801e33972879e6983627eb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp')
0 files changed, 0 insertions, 0 deletions