summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/tests/fetch.py
diff options
context:
space:
mode:
authorMuhammad Hamza <Muhammad_Hamza@mentor.com>2022-06-20 18:17:56 +0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-06-21 18:44:27 +0100
commit97a4c50fa3ed5ffbe212e7eed25b4427bebd546e (patch)
treee048376378aad8ba7acbf868074e18449940ac8a /bitbake/lib/bb/tests/fetch.py
parent27b5d5ad5be0a0d1a6c8aadc8af8228ccea322e0 (diff)
downloadpoky-97a4c50fa3ed5ffbe212e7eed25b4427bebd546e.tar.gz
udev-extraconf/mount.sh: only mount devices on hotplug
fdisk from util-linux (2.31.1) and above allows the user to manipulate an already mounted device. In order to achieve this functionality it issues a BLKRRPART (block device re-read part) ioctl and in response the kernel generates remove/change/add events if the device is not mounted (manually unmounted etc) which are caught and processed by udev. This causes our auto-mounter to remount everything because it does not keep track and things go out of control. Differentiating between types of remove events such as the one described above (generated by BLKRRPART) and one where the device is physically plugged out is only possible using the DEVPATH variable which is cleaned up only when the device is actually plugged-out. This fixes the above anomaly by only mounting a device in add event which is cleaned up properly (tmp cache deleted) in the remove event or is not present in the tmp cache while making use of the DEVPATH variable during the remove action. (From OE-Core rev: 11a5e6c17535438ea1e7a8403ed260c8b3a22bc8) Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/tests/fetch.py')
0 files changed, 0 insertions, 0 deletions