summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Makefile: add more compiler flagsKinga Stefaniuk2024-07-301-1/+22
| | | | | | | | | | | It is essential to avoid vulnerabilities in code as much as possible using safe compilation flags. It is easier if they are added to the Makefile and applied during compilation. Add new gcc flags and make them configurable, because they may not be supported for some compilers. Set FORTIFY_SOURCE with the highest supported value for platform. Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* super0: use define for char array in examine_super0Kinga Stefaniuk2024-07-302-1/+4
| | | | | | | | | Using nb with 11 length may cause format-truncation errors, because it was possible to use snprintf with 12 length input and write it to 11 length output. Added new define and use it to avoid this error. Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* drive_encryption: Fix ata passthrough12 verifyBlazej Kucman2024-07-241-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | Based on documentation SCSI Primary Commands - 4 (SPC-4) only first 7 bits of first byte in sense data are used to store response code. The current verification uses all 8 bits for comparison of response code. Incorrect verification may make impossible to use SATA disks with IMSM, because IMSM requires verification of the encryption state before use. There was issue in kernel libata [1]. This issue hides bug in mdadm because last bit was not set. Example output with affected mdadm: Port3 : /dev/sde (BTPR212503EK120LGN) mdadm: Failed ata passthrough12 ioctl. Device: /dev/sde. mdadm: Failed to get drive encryption information The fix is use the first 7 bits of Byte 0, to compare with the expected values. [1] https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git/commit/?id=38dab832c3f4 Fixes: df38df3052c3 ("Add reading SATA encryption information") Signed-off-by: Blazej Kucman <blazej.kucman@intel.com>
* Detail: fix --detail --export for uuid_zeroKinga Stefaniuk2024-07-241-1/+1
| | | | | | | | | | | | | | Mentioned commit (see Fixes) causes that devices with UUID equal to uuid_zero was not recognized properly. For few devices the first one was taken always, and the same information was printed. It caused regression, when few containers were created, symlinks were generated only for the first one. Add checking if uuid is uuid_zero and, if yes, use devname to differentiate devices. Fixes: 60c19530dd7c ("Detail: remove duplicated code") Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* CI: fetch all of the changes in repositoryKinga Stefaniuk2024-07-241-3/+1
| | | | | | | | GH action is using checkout plugin, which takes fetch-depth as a parameter to specify number of commits to fetch. Setting it to 0 to fetch all of the history of all branches and tags. Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* mdadm: do not allow leading dot in MD device nameMariusz Tkaczyk2024-07-191-34/+41
| | | | | | | | | | Do not allow to use '.' on first place for named MD device. Having leading dot might be confusing, MD device cannot be hidden. It also removes possibility to create md device with name '.'. Additionally, code optimalizations are done. Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm: lib.c fix coverity issuesNigel Croxon2024-07-161-2/+2
| | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Event fixed_size_dest: You might overrun the 32-character fixed-size string "devnm" by copying "cp + 1" without checking the length. * Event fixed_size_dest: You might overrun the 32-character fixed-size string "devnm" by copying "cp" without checking the length. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* mdadm: Query.c fix coverity issuesNigel Croxon2024-07-161-1/+3
| | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Event leaked_storage: Variable "sra" going out of scope leaks the storage it points to. * Event uninit_use_in_call: Using uninitialized value "larray_size" when calling "human_size_brief". Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* mdadm: Monitor.c fix coverity issuesNigel Croxon2024-07-161-4/+8
| | | | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Event check_return: Calling "fcntl(fd, 2, 1)" without checking return value. This library function may fail and return an error code. * Dereferencing "sl", which is known to be "NULL". * Event fixed_size_dest: You might overrun the 32-character fixed-size string "devnm" by copying "tmp" without checking the length. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* imsm: add indent for encryption detailsMariusz Tkaczyk2024-07-161-1/+1
| | | | | | Improve readability of the output. Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* Manage: fix is_remove_safe()Mariusz Tkaczyk2024-07-161-1/+1
| | | | | | | Fix for to make --set-faulty working. Fixes: 1b4b73fd535a ("mdadm: Manage.c fix coverity issues") Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm: Manage.c fix coverity issuesNigel Croxon2024-07-101-78/+71
| | | | | | | | | | | | | | | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Event parameter_hidden: declaration hides parameter "dv". * Event leaked_storage: Variable "mdi" going out of scope leaks the storage it points to. * Event overwrite_var: Overwriting "mdi" in "mdi = mdi->devs" leaks the storage that "mdi" points to. * Event leaked_handle: Handle variable "lfd" going out of scope leaks the handle. * Event leaked_handle: Returning without closing handle "fd" leaks it. * Event fixed_size_dest: You might overrun the 32-character fixed-sizei string "devnm" by copying the return value of "fd2devnm" without checking the length. * Event fixed_size_dest: You might overrun the 32-character fixed-size string "nm" by copying "nmp" without checking the length. * Event fixed_size_dest: You might overrun the 32-character fixed-size string "devnm" by copying the return value of "fd2devnm" without checking the length. * Event assigned_value: Assigning value "-1" to "tfd" here, but that stored value is overwritten before it can be used. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* mapfile.c: Fix STRING_OVERFLOW issueAnna Sztukowska2024-07-101-3/+3
| | | | | | | Fix STRING_OVERFLOW issue found by SAST analysis in map_add() and map_update() in mapfile.c. Signed-off-by: Anna Sztukowska <anna.sztukowska@intel.com>
* mdadm/clustermd_tests: adjust test cases to support md module changesHeming Zhao2024-07-104-5/+7
| | | | | | | | | | Since kernel commit db5e653d7c9f ("md: delay choosing sync action to md_start_sync()") delays the start of the sync action, clustermd array sync/resync jobs can happen on any leg of the array. This commit adjusts the test cases to follow the new kernel layer behavior. Signed-off-by: Heming Zhao <heming.zhao@suse.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/clustermd_tests: add some APIs in func.sh to support running the tests ↵Heming Zhao2024-07-101-0/+60
| | | | | | | | | | without errors clustermd_tests/func.sh lacks some APIs to run, this patch makes clustermd_tests runnable from the test suite. Signed-off-by: Heming Zhao <heming.zhao@suse.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm: super-ddf.c fix coverity issuesNigel Croxon2024-07-091-57/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Calling "lseek64" without checking return value. This library function may fail and return an error code. * Overrunning array "anchor->pad2" of 3 bytes by passing it to a function which accesses it at byte offset 398 using argument "399UL". * Event leaked_storage: Variable "sra" going out of scope leaks the storage it points to. * Event leaked_storage: Variable "super" going out of scope leaks the storage it points to. * Event leaked_handle: Handle variable "dfd" going out of scope leaks the handle. * Event leaked_storage: Variable "dl1" going out of scope leaks the storage it points to * Event leaked_handle: Handle variable "cfd" going out of scope leaks the handle. * Variable "avail" going out of scope leaks the storage it points to. * Passing unterminated string "super->anchor.revision" to "fprintf", which expects a null-terminated string. * You might overrun the 32-character fixed-size string "st->container_devnm" by copying the return value of "fd2devnm" without checking the length. * Event fixed_size_dest: You might overrun the 33-character fixed-size string "dev->name" by copying "(*d).devname" without checking the length. * Event uninit_use_in_call: Using uninitialized value "info.array.raid_disks" when calling "getinfo_super_ddf" V2: clean up validate_geometry_ddf() routine with Mariusz Tkaczyk recommendations. V3: clean up spaces with Blazej Kucman recommendations. V4: clean up recommended by Mariusz Tkaczyk. V5: clean up recommended by Mariusz Tkaczyk. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* mdadm: Create.c fix coverity issuesNigel Croxon2024-07-051-3/+3
| | | | | | | | | | | | * Event negative_returns: "fd" is passed to a parameter that cannot be negative. Which is set to -1 to start. * Event open_fn: Returning handle opened by "open_dev_excl". * Event var_assign: Assigning: "container_fd" = handle returned from "open_dev_excl(st->container_devnm)" * Event leaked_handle: Handle variable "container_fd" going out of scope leaks the handle Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* mdadm: Build.c fix coverity issuesNigel Croxon2024-07-031-6/+6
| | | | | | | Event leaked_handle: Handle variable "bitmap_fd" going out of scope leaks the handle. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* config.c: Fix memory leak in load_containers()Anna Sztukowska2024-07-031-0/+1
| | | | | | | Fix memory leak in load_containers() in config.c reported by SAST analysis. Signed-off-by: Anna Sztukowska <anna.sztukowska@intel.com>
* CI: use prepared checkpatch.conf file only for GH actionsKinga Stefaniuk2024-07-022-0/+2
| | | | | | | | | | Configuration file .checkpatch.conf is working properly only with GH actions, because flags from GH plugin are used there. This file shall not be placed in main repo directory, because it causes errors while using checkpatch from Linux. Add step to review.yml to copy this file before checkpatch action is started. Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* mdadm: Fix socket connection failure when mdmon runs in foreground mode.Shminderjit Singh2024-07-023-2/+50
| | | | | | | | | | | | | | | | | | | | While creating an IMSM RAID, mdadm will wait for the mdmon main process to finish if mdmon runs in forking mode. This is because with "Type=forking" in the mdmon service unit file, "systemctl start service" will block until the main process of mdmon exits. At that moment, mdmon has already created the socket, so the subsequent socket connect from mdadm will succeed. However, when mdmon runs in foreground mode (without "Type=forking" in the service unit file), "systemctl start service" will return once the mdmon process starts. This causes mdadm and mdmon to run in parallel, which may lead to a socket connection failure since mdmon has not yet initialized the socket when mdadm tries to connect. If the next instruction/command is to access this device and try to write to it, a permission error will occur since mdmon has not yet set the array to RW mode. Signed-off-by: Shminderjit Singh <shminderjit.singh@oracle.com>
* CI: fix excluded files in checkpatch.confKinga Stefaniuk2024-06-251-6/+0
| | | | | | | | --exclude flag in checkpatch.conf is configured to work on directories only. When checkpatch.conf contains files, checkpatch scan is not started. Remove file names and keep only directories which should be excluded. Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* mdadm: Assemble.c fix coverity issuesNigel Croxon2024-06-251-6/+24
| | | | | | | | | | | | | Fixing the following coding errors the coverity tools found: * Event dereference: Dereferencing "pre_exist", which is known to be "NULL". * Event parameter_hidden: Declaration hides parameter "c". * Event leaked_storage: Variable "pre_exist" going out of scope leaks the storage it points to. * Event leaked_storage: Variable "avail" going out of scope leaks the storage it points to. Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
* Revert "mdadm: Fix socket connection failure when mdmon runs in foreground ↵Mariusz Tkaczyk2024-06-211-19/+1
| | | | | | | | | | | | mode." This reverts commit 66a54b266f6c579e5f37b6253820903a55c3346c. connect_monitor() is called from ping_monitor() but this function is often used as advice, without verification that mdmon is really working. This produces hangs in many scenarios. Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: judge foreign array in test casesXiao Ni2024-06-205-4/+14
| | | | | | | | | It needs to use array name when judging if one array is foreign or not. So calling is_raid_foreign in test cases which need it. Fixes: 41706a915684 ('mdadm/tests: names_template enhance') Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* Makefile: Do not call gcc directlyGwendal Grignou2024-06-181-3/+3
| | | | | | | | | | | | When mdadm is compiled with clang, direct gcc will fail. Make sure to use $(CC) variable instead. Note that Clang does not support --help=warnings, --print-diagnostic-options should be used instead. So with Clang, the compilation will go through, but the extra warning flags will never be added. Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
* mdadm: Fix socket connection failure when mdmon runs in foreground mode.Shminderjit Singh2024-06-181-1/+19
| | | | | | | | | | | | | | | | | | | | While creating an IMSM RAID, mdadm will wait for the mdmon main process to finish if mdmon runs in forking mode. This is because with "Type=forking" in the mdmon service unit file, "systemctl start service" will block until the main process of mdmon exits. At that moment, mdmon has already created the socket, so the subsequent socket connect from mdadm will succeed. However, when mdmon runs in foreground mode (without "Type=forking" in the service unit file), "systemctl start service" will return once the mdmon process starts. This causes mdadm and mdmon to run in parallel, which may lead to a socket connection failure since mdmon has not yet initialized the socket when mdadm tries to connect. If the next instruction/command is to access this device and try to write to it, a permission error will occur since mdmon has not yet set the array to RW mode. Signed-off-by: Shminderjit Singh <shminderjit.singh@oracle.com>
* test: pass flags to servicesMateusz Kusiak2024-06-182-6/+48
| | | | | | | | | | | | | | | | | | Commit 4c12714d1ca0 ("test: run tests on system level mdadm") removed MDADM_NO_SYSTEMCTL flag from test suite. This causes imsm tests to fail as mdadm no longer triggers mdmon and flags exists only within session. Use systemd set/unset-environment to pass necessary flags. Introduce colors to grab users attention to warnings and key messages. Make test suite setup systemd environment. Add setup/clean_systemd_env() functions. Warn user about altering systemd environment. Add colors to success/fail messages and warnings. Signed-off-by: Mateusz Kusiak <mateusz.kusiak@intel.com>
* mdadm: Block SIGCHLD processes before starting childrenLogan Gunthorpe2024-06-131-0/+1
| | | | | | | | | | | | | | | There is a small race condition noticed during code review, but never actully hit in practice, with the write_zero feature. If a write zeros fork finishes quickly before wait_for_zero_forks() gets called, then the SIGCHLD will be delivered before the signalfd is setup. While this is only theoretical, fix this by blocking the SIGCHLD signal before forking any children. Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm: Fix hang race condition in wait_for_zero_forks()Logan Gunthorpe2024-06-131-13/+15
| | | | | | | | | | | | | | | | | | Running a create operation with --write-zeros can randomly hang forever waiting for child processes. This happens roughly on in ten runs with when running with small (20MB) loop devices. The bug is caused by the fact that signals can be coallesced into one if they are not read by signalfd quick enough. So if two children finish at exactly the same time, only one SIGCHLD will be received by the parent. To fix this, wait on all processes with WNOHANG every time a SIGCHLD is received and exit when all processes have been waited on. Reported-by: Xiao Ni <xni@redhat.com> Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* imsm: make freesize required to volume autolayoutKinga Stefaniuk2024-06-111-4/+6
| | | | | | | | | | | | | Autolayout_imsm() shall be executed when IMSM_NO_PLATFORM=1 is set. It was fixed by listed commit, checking super->orom was removed, but also checking freesize. Freesize is not set for operations on RAID volume with no size update, that's why it is not required to have this value and always run autolayout_imsm(). Fix it by making autolayout_imsm() dependent on freesize. Fixes: 46f192 ("imsm: fix first volume autolayout with IMSM_NO_PLATFORM") Signed-off-by: Kinga Stefaniuk <kinga.stefaniuk@intel.com>
* imsm: fix first volume autolayout with IMSM_NO_PLATFORMMariusz Tkaczyk2024-05-281-9/+9
| | | | | | | | | | | | | Autolayout_imsm() is not executed if IMSM_NO_PLATFORM=1 is set. This causes that first volume cannot be created. Disk for new volume are never configured. Fix it by making autolayout_imsm() independent from super->orom because NULL there means that IMSM_NO_PLATFORM=1 is set. There are not platform restrictions to create volume, we just analyze drives. It is safe. Fixes: 6d4d9ab295de ("imsm: use same slot across container") Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm.h: provide basename if GLIBC is not avialableMariusz Tkaczyk2024-05-281-0/+8
| | | | | | | | | If GNU basename is not avilable, define it. It is safer to use that rather than include libgen.h with XPG basename() definition. Fixes:#12 Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: remove strace testXiao Ni2024-05-282-2/+2
| | | | | | | | Some tests will fail if the test env doesn't have strace commands. So remove the dependency. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 05r1-re-add-nosuperXiao Ni2024-05-281-1/+1
| | | | | | | | Patch 50b100768a11('mdadm: deprecate bitmap custom file') needs to confirm when creating raid device with bitmap file. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 04update-uuidXiao Ni2024-05-281-2/+2
| | | | | | | | Patch 50b100768a11('mdadm: deprecate bitmap custom file') needs to confirm when creating raid device with bitmap file. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: bitmap cases enhanceXiao Ni2024-05-286-64/+48
| | | | | | | | | It fails because bitmap dirty number is smaller than 400 sometimes. It's not good to compare bitmap dirty bits with a number. It depends on the test machine, it can flush soon before checking the number. So remove related codes. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/platform-intel: buffer overflow detectedXiao Ni2024-05-281-2/+2
| | | | | | | | | | | | | | mdadm -CR /dev/md0 -l1 -n2 /dev/nvme0n1 /dev/nvme2n1 *** buffer overflow detected ***: terminated Aborted (core dumped) It doesn't happen 100% and it depends on the building environment. It can be fixed by replacing sprintf with snprintf. Fixes: d835518b6b53 ('imsm: nvme multipath support') Reported-by: Guang Wu <guazhang@redhat.com> Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: disable selinuxXiao Ni2024-05-242-0/+13
| | | | | | | | | Sometimes systemd service fails because selinux. Disable selinux during testing now. We can enable it in future when having a better method. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 07changelevelintrXiao Ni2024-05-242-13/+5
| | | | | | | | | | | | It needs to specify a 2 powered array size when updating array size. If not, it can't change chunksize. And sometimes it reports error reshape doesn't happen. In fact the reshape has finished. It doesn't need to wait before checking reshape action. Because check function waits itself. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 07autodetect.broken can be removedXiao Ni2024-05-241-5/+0
| | | | | | | 07autodetect can run successfully without error in kernel 6.9.0-rc5. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 07autoassembleXiao Ni2024-05-243-10/+37
| | | | | | | | | | | | | | | | This test is used to test stacked array auto assemble. There are two different cases depends on if array is foreign or not. If the array is foreign, the stacked array (md0 is on md1 and md2) can't be assembled with name md0. Because udev rule will run when md1 and md2 are assembled and mdadm -I doesn't specify homehost. So it will treat stacked array (md0) as foreign array and choose md127 as the device node name (/dev/md127) Add the case that stacked array is local. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 06name enhanceXiao Ni2024-05-241-2/+8
| | | | | | | | It needs to check hostname in metadata name if one array is local. Add the check in this case. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 05r5-internalbitmapXiao Ni2024-05-241-12/+9
| | | | | | | | | It's not right to compare bitmap bits with a number after io comes. Because maybe those bits are already flused. Remove the related tests. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* tests/04update-metadata skip linearXiao Ni2024-05-243-15/+25
| | | | | | | | Add one check that if kernel doesn't support linear/multipath, it can skip linear/multipath testing. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: remove 04r5swap.brokenXiao Ni2024-05-241-7/+0
| | | | | | | 04r5swap can run successfully with kernel 6.9.0-rc4 Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 03r5assemV1Xiao Ni2024-05-241-17/+0
| | | | | | | | dcc22ae74a864 ('super1: remove support for name= in config') already removes name= support. So remove related test codes in 03r5assemV1. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: remove 03r5assem-failedXiao Ni2024-05-241-12/+0
| | | | | | | 03r5assem can run successfully with kernel 6.9.0-rc4 Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests 03r0assem enhanceXiao Ni2024-05-241-10/+0
| | | | | | | | dcc22ae74a864 ('super1: remove support for name= in config') already removes name= support. So remove related test codes in 03r0assem. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
* mdadm/tests: 03assem-incr enhanceXiao Ni2024-05-242-7/+16
| | | | | | | | | | It fails when hostname lenght > 32. Because the super1 metadata name doesn't include hostname when hostname length > 32. Then mdadm thinks the array is a foreign array if no device link is specified when assembling the array. It chooses a minor number from 127. Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 06:03:43 +0100