diff options
| author | Blazej Kucman <blazej.kucman@intel.com> | 2021-12-03 15:31:15 +0100 |
|---|---|---|
| committer | Jes Sorensen <jsorensen@fb.com> | 2021-12-08 15:39:50 +0100 |
| commit | ced5fa8b170ad448f4076e24a10c731b5cfb36ce (patch) | |
| tree | 3d9bb069b988bb06da8445291076efcf31aebde6 /mdadm.8.in | |
| parent | Correct checking if file descriptors are valid (diff) | |
| download | mdadm-ced5fa8b170ad448f4076e24a10c731b5cfb36ce.tar.xz mdadm-ced5fa8b170ad448f4076e24a10c731b5cfb36ce.zip | |
mdadm: block creation with long names
This fixes buffer overflows in create_mddev(). It prohibits
creation with not supported names for DDF and native. For IMSM,
mdadm will do silent cut to 16 later.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Signed-off-by: Blazej Kucman <blazej.kucman@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Diffstat (limited to 'mdadm.8.in')
| -rw-r--r-- | mdadm.8.in | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -2186,6 +2186,11 @@ is run, but will be created by .I udev once the array becomes active. +The max length md-device name is limited to 32 characters. +Different metadata types have more strict limitation +(like IMSM where only 16 characters are allowed). +For that reason, long name could be truncated or rejected, it depends on metadata policy. + As devices are added, they are checked to see if they contain RAID superblocks or filesystems. They are also checked to see if the variance in device size exceeds 1%. |