summaryrefslogtreecommitdiffstats
path: root/ReadMe.c
diff options
context:
space:
mode:
authorBlazej Kucman <blazej.kucman@intel.com>2024-11-22 11:01:04 +0100
committerMariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>2024-11-25 08:56:55 +0100
commit7f960c3bd050e76f8bf0a8a0c8fbdcbaa565fc78 (patch)
tree94ba6b68c97b8f64667a5f349aea2813ac02581b /ReadMe.c
parentCI: run mdadm tests on test scripts change (diff)
downloadmdadm-7f960c3bd050e76f8bf0a8a0c8fbdcbaa565fc78.tar.xz
mdadm-7f960c3bd050e76f8bf0a8a0c8fbdcbaa565fc78.zip
platform-intel: fix buffer overflow
mdadm -C /dev/md/imsm0 -e imsm -n 2 /dev/nvme5n1 /dev/nvme4n1 -R mdadm -C /dev/md/r0d2 -l 0 -n 2 /dev/nvme5n1 /dev/nvme4n1 -R *** buffer overflow detected ***: terminated Aborted (core dumped) Issue is related to D_FORTIFY_SOURCE=3 flag and depends on environment, especially compiler version. In function active_arrays_by_format length of path buffer is calculated dynamically based on parameters, while PATH_MAX is used in snprintf, this is my lead to buffer overflow. It is fixed by change dynamic length calculation, to use define PATH_MAX for path length. Signed-off-by: Blazej Kucman <blazej.kucman@intel.com>
Diffstat (limited to 'ReadMe.c')
0 files changed, 0 insertions, 0 deletions