https://bugs.kde.org/show_bug.cgi?id=317127
--- Comment #19 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Mark Wielaard from comment #18) > I must admit I don't fully understand what we are trying to do. As far as I > understand it, the idea is that we sanity check what the aspacemgr records > against what /proc/self/maps shows? But that includes some device specific > inode values which we don't have/know? Can't we just make cmp_devino = False > the default? aka never check those? Or are we loosing some valuable sanity > checks/info that way? I think the goal is to check as many things as possible. Is it valuable? Hard to imagine reading the wrong exe or library that is mmap'd but if ever that did happen it would be fairly catastrophic. The problem with btrfs is that /proc/self/maps uses the device id for the supernode whilst statx returns the device id for the btrfs subvolume. The two are different so the sanity check fails. This check is turned off for Darwin. I'm just testing turning it back on for FreeBSD - it seems to work with a couple of tweaks. -- You are receiving this mail because: You are watching all bug changes.
