summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/glibc
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-07 11:39:56 +0100
commit2a87bddabf816d09ec801e33972879e6983627eb (patch)
treea0a7e6daa9c0c48b246d8b3c0e071bf3a704aa65 /meta/recipes-core/glibc
parent2abb5fd026bb6f1df504a025702c32eefb13b8bb (diff)
downloadopenembedded-core-contrib-2a87bddabf816d09ec801e33972879e6983627eb.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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/glibc')
0 files changed, 0 insertions, 0 deletions