diff options
author | 2023-06-13 10:13:37 +0200 | |
---|---|---|
committer | 2023-06-19 14:02:00 +0300 | |
commit | f723edb8a532cd26e1ff0a2b271d73762d48f762 (patch) | |
tree | 5811c7a694a1a528abf025ba41d290e575d2e3a7 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | ovl: implement lazy lookup of lowerdata in data-only layers (diff) | |
download | wireguard-linux-f723edb8a532cd26e1ff0a2b271d73762d48f762.tar.xz wireguard-linux-f723edb8a532cd26e1ff0a2b271d73762d48f762.zip |
ovl: check type and offset of struct vfsmount in ovl_entry
Porting overlayfs to the new amount api I started experiencing random
crashes that couldn't be explained easily. So after much debugging and
reasoning it became clear that struct ovl_entry requires the point to
struct vfsmount to be the first member and of type struct vfsmount.
During the port I added a new member at the beginning of struct
ovl_entry which broke all over the place in the form of random crashes
and cache corruptions. While there's a comment in ovl_free_fs() to the
effect of "Hack! Reuse ofs->layers as a vfsmount array before freeing
it" there's no such comment on struct ovl_entry which makes this easy to
trip over.
Add a comment and two static asserts for both the offset and the type of
pointer in struct ovl_entry.
Signed-off-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions