summaryrefslogtreecommitdiffstats
path: root/meta/classes/mirrors.bbclass
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2022-04-03 11:12:04 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-04-03 17:51:26 +0100
commitdfc910bdc24633897c17caf2293409b5cd4a849b (patch)
tree16c93be00e74beadfc729e6429dbe43f8fa6281a /meta/classes/mirrors.bbclass
parentd0082265d5358f672ff00ff2d5c6a4d38564576e (diff)
downloadpoky-dfc910bdc24633897c17caf2293409b5cd4a849b.tar.gz
bitbake: pyinotify: Handle potential latent bug
The kernel inotify code can set more than one of the bits in the mask, fsnotify_change() in linux/fsnotify.h is quite clear that IN_ATTRIB, IN_MODIFY and IN_ACCESS can arrive together. We don't care about two of these from a bitbake perspective but it probably explains why in real world builds, we've seen: pyinotify.ProcessEventError: Unknown mask 0x00000006 This module code assumes only one mask bit can be present. Since we don't care about two of these events, just mask them out for now. The "upstream" code is unmainained since 2015. (Bitbake rev: 7fb93c2ce6dacd9b53fc3a227133a3493e6a6a1d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/mirrors.bbclass')
0 files changed, 0 insertions, 0 deletions