* [syzbot] [raid?] KASAN: slab-out-of-bounds Read in super_90_validate
@ 2026-11-15 22:06 syzbot
2026-11-16 8:32 ` [PATCH] md: reject out-of-bounds desc_nr in super_90_validate() Shuai Liu
0 siblings, 1 reply; 4+ messages in thread
From: syzbot @ 2026-11-15 22:06 UTC (permalink / raw)
To: linux-kernel, linux-raid, song, syzkaller-bugs, yukuai
Hello,
syzbot found the following issue on:
HEAD commit: 2800868f6322 Merge tag 'sound-7.4-rc3' of git://git.kernel..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17a6353d580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
dashboard link: https://syzkaller.appspot.com/bug?extid=c5969d7e0a934b384fd6
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159fc9ad580000
AI-generated root cause summary:
When creating a non-persistent RAID array (`not_persistent = 1`) via
`SET_ARRAY_INFO` (`md_set_array_info()`), `mddev->max_disks` is left
uninitialized as 0. When a new disk is added via `md_add_new_disk()`
(`ADD_NEW_DISK`), `mddev->persistent == 0` causes `md_import_device()` to
allocate an uninitialized `rdev->sb_page` without loading superblock data, and
`bind_rdev_to_array()` assigns `rdev->desc_nr` from `mddev->raid_disks` without
enforcing `MD_SB_DISKS` (since `max_disks == 0`). For array personalities
lacking `hot_remove_disk` (such as `md-linear`) or when journal devices are
added, `add_bound_rdev()` unconditionally calls
`super_types[mddev->major_version].validate_super()`, executing
`super_90_validate()` without checking `mddev->persistent`. In
`super_90_validate()`, `desc = sb->disks + rdev->desc_nr` is accessed without
checking that `rdev->desc_nr < MD_SB_DISKS` (27), leading to an out-of-bounds
read beyond the 4KB superblock page into adjacent kernel memory.
full analysis: https://syzkaller.appspot.com/x/ai_root_cause?x=c5969d7e0a934b384fd6
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5969d7e0a934b384fd6@syzkaller.appspotmail.com
md: md0 stopped.
md/raid1:md0: active with 1 out of 35 mirrors
md0: detected capacity change from 0 to 4096
=========================
==================================================================
BUG: KASAN: use-after-free in super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592
Read of size 4 at addr ffff888073d36390 by task syz-executor291/6009
CPU: 1 UID: 0 PID: 6009 Comm: syz-executor291 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0x13d/0x4b0 mm/kasan/report.c:482
kasan_report+0xdf/0x1c0 mm/kasan/report.c:595
super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592
add_bound_rdev+0x274/0x390 drivers/md/md.c:3012
md_add_new_disk+0xca1/0x1820 drivers/md/md.c:7666
md_ioctl+0x2c1d/0x3700 drivers/md/md.c:8525
blkdev_ioctl+0x5ad/0x6f0 block/ioctl.c:798
vfs_ioctl fs/ioctl.c:52 [inline]
__do_sys_ioctl fs/ioctl.c:598 [inline]
__se_sys_ioctl fs/ioctl.c:584 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:584
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f27a95100ab
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
RSP: 002b:00007ffd4383a800 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f27a95100ab
RDX: 00007ffd4383a890 RSI: 0000000040140921 RDI: 0000000000000003
RBP: 00007ffd4383a890 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f27a956cfc7
R13: 0000000000000002 R14: 00007f27a9594cc0 R15: 0000000000000002
</TASK>
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x73d36
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: f0(buddy)
raw: 00fff00000000000 ffffea0000d5ae88 ffffea0000d5af88 0000000000000000
raw: 0000000000000000 0000000000000000 00000000f0000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Unmovable, gfp_mask 0xcc0(GFP_KERNEL), pid 5639, tgid 5639 (syz-executor), ts 63888746915
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0xfd/0x120 mm/page_alloc.c:1860
prep_new_page mm/page_alloc.c:1868 [inline]
get_page_from_freelist+0xdae/0x2c80 mm/page_alloc.c:3950
__alloc_frozen_pages_noprof+0x2ad/0x31e0 mm/page_alloc.c:5492
__alloc_pages_noprof mm/page_alloc.c:5532 [inline]
alloc_pages_bulk_noprof+0x77e/0x1420 mm/page_alloc.c:5349
___alloc_pages_bulk mm/kasan/shadow.c:345 [inline]
__kasan_populate_vmalloc_do mm/kasan/shadow.c:370 [inline]
__kasan_populate_vmalloc+0xf0/0x210 mm/kasan/shadow.c:424
kasan_populate_vmalloc include/linux/kasan.h:580 [inline]
alloc_vmap_area+0x963/0x2bc0 mm/vmalloc.c:2151
__get_vm_area_node+0x1ed/0x350 mm/vmalloc.c:3281
__vmalloc_node_range_noprof+0x2ad/0x1440 mm/vmalloc.c:4112
vmalloc_user_noprof+0x9e/0xe0 mm/vmalloc.c:4307
kcov_ioctl+0x4d/0x750 kernel/kcov.c:756
vfs_ioctl fs/ioctl.c:52 [inline]
__do_sys_ioctl fs/ioctl.c:598 [inline]
__se_sys_ioctl fs/ioctl.c:584 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:584
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 5356 tgid 5356 ts 65501624162 stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
__free_pages_prepare mm/page_alloc.c:1402 [inline]
__free_frozen_pages+0x7b1/0x10f0 mm/page_alloc.c:2958
kasan_depopulate_vmalloc_pte+0x5d/0x80 mm/kasan/shadow.c:484
apply_to_pte_range mm/memory.c:3536 [inline]
apply_to_pmd_range mm/memory.c:3580 [inline]
apply_to_pud_range mm/memory.c:3616 [inline]
apply_to_p4d_range mm/memory.c:3652 [inline]
__apply_to_page_range+0xb1d/0x1520 mm/memory.c:3688
__kasan_release_vmalloc+0xd7/0xe0 mm/kasan/shadow.c:602
kasan_release_vmalloc include/linux/kasan.h:593 [inline]
kasan_release_vmalloc_node mm/vmalloc.c:2312 [inline]
purge_vmap_node+0x210/0xb40 mm/vmalloc.c:2334
__purge_vmap_area_lazy+0x90a/0xc00 mm/vmalloc.c:2424
drain_vmap_area_work+0x27/0x40 mm/vmalloc.c:2458
process_one_work+0xac7/0x1b10 kernel/workqueue.c:3495
process_scheduled_works kernel/workqueue.c:3578 [inline]
worker_thread+0x5ef/0xe50 kernel/workqueue.c:3659
kthread+0x373/0x450 kernel/kthread.c:436
ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Memory state around the buggy address:
ffff888073d36280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888073d36300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888073d36380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888073d36400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888073d36480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 4+ messages in thread* [PATCH] md: reject out-of-bounds desc_nr in super_90_validate() 2026-11-15 22:06 [syzbot] [raid?] KASAN: slab-out-of-bounds Read in super_90_validate syzbot @ 2026-11-16 8:32 ` Shuai Liu 2026-11-16 8:54 ` sashiko-bot 0 siblings, 1 reply; 4+ messages in thread From: Shuai Liu @ 2026-11-16 8:32 UTC (permalink / raw) To: linux-raid Cc: song, yukuai, magiclinan, xiao, linux-kernel, syzbot+c5969d7e0a934b384fd6, 847807867 super_90_validate() indexes the on-disk disk descriptor array with rdev->desc_nr without any bounds check: desc = sb->disks + rdev->desc_nr; if (desc->state & (1<<MD_DISK_FAULTY)) ... mdp_super_t carries only MD_SB_DISKS (27) descriptors of 128 bytes each starting at offset 512, so any desc_nr outside [0, MD_SB_DISKS) reads past the end of the 4KB superblock page. Such an out-of-range desc_nr is reachable in several ways: 1. On a running non-persistent array, ADD_NEW_DISK with the MD_DISK_JOURNAL flag reaches add_bound_rdev(), which calls validate_super() unconditionally for journal disks. bind_rdev_to_array() auto-assigns desc_nr = mddev->raid_disks to a new rdev, and its max_disks check is skipped both for journal disks and when mddev->max_disks == 0 (the case for non-persistent arrays, which never set it). With raid_disks > MD_SB_DISKS the assigned desc_nr points past the descriptor array. 2. During assembly, rdev->desc_nr comes straight from the on-disk sb->this_disk.number, which is fully attacker-controlled fuzz input. syzbot hit path 1: a RAID1 array with raid_disks=35 and not_persistent=1 plus a hot-added journal disk made super_90_validate() read sb->disks[35].state at byte offset 512 + 35 * 128 + 16 = 5008, i.e. 912 bytes into the page following the 4096-byte superblock page: BUG: KASAN: use-after-free in super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592 Read of size 4 at addr ffff888073d36390 by task syz-executor291/6009 ... super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592 add_bound_rdev+0x274/0x390 drivers/md/md.c:3012 md_add_new_disk+0xca1/0x1820 drivers/md/md.c:7666 md_ioctl+0x2c1d/0x3700 drivers/md/md.c:8525 blkdev_ioctl+0x5ad/0x6f0 block/ioctl.c:798 (The KASAN report shows use-after-free or slab-out-of-bounds depending on what occupies the neighbouring memory.) super_1_validate() already bounds desc_nr against sb->max_dev; the 0.90 metadata path has no equivalent check. Reject desc_nr outside [0, MD_SB_DISKS) with -EINVAL, which covers both the desc->state reads in super_90_validate() itself and keeps fuzzed on-disk sb->this_disk.number values from being used as an array index. Note that super_90_sync() also writes sb->disks[] indexed by desc_nr; on a persistent array a journal disk can still bypass the bind_rdev_to_array() max_disks check and reach that write. Reaching it additionally requires a crafted on-disk superblock, so it is left for follow-up discussion. Verified with the syzbot reproducer under QEMU with KASAN (7.4-rc3 based config): baseline reproduces the use-after-free on every run, with this patch the reproducer completes with zero KASAN reports across repeated runs. Reported-by: syzbot+c5969d7e0a934b384fd6@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=c5969d7e0a934b384fd6 Signed-off-by: Shuai Liu <847807867@qq.com> --- drivers/md/md.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/md/md.c b/drivers/md/md.c index 03e35386a8028..83009b0d84092 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -1495,6 +1495,9 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru mdp_super_t *sb = page_address(rdev->sb_page); __u64 ev1 = md_event(sb); + if (rdev->desc_nr < 0 || rdev->desc_nr >= MD_SB_DISKS) + return -EINVAL; + rdev->raid_disk = -1; clear_bit(Faulty, &rdev->flags); clear_bit(In_sync, &rdev->flags); -- 2.43.0 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] md: reject out-of-bounds desc_nr in super_90_validate() 2026-11-16 8:32 ` [PATCH] md: reject out-of-bounds desc_nr in super_90_validate() Shuai Liu @ 2026-11-16 8:54 ` sashiko-bot 2026-11-16 8:59 ` [PATCH v2] " Shuai Liu 0 siblings, 1 reply; 4+ messages in thread From: sashiko-bot @ 2026-11-16 8:54 UTC (permalink / raw) To: Shuai Liu, linux-raid; +Cc: yukuai Thank you for your contribution! Sashiko AI review found 1 potential issue to consider: - [Medium] md: ignored super_90_validate() error in md_add_new_disk() and add_bound_rdev() It also noticed 1 related pre-existing issue this patch does not introduce: - [Medium] md: missing raid_disk and delta_disks validation in super_90_validate() [1] -- commit 8c2da3468482d3b2e5d7496a1240f196823bd4e4 Author: Shuai Liu <847807867@qq.com> md: reject out-of-bounds desc_nr in super_90_validate() This commit adds a bounds check on rdev->desc_nr in super_90_validate() to reject values outside [0, MD_SB_DISKS) with -EINVAL before indexing sb->disks[]. > diff --git a/drivers/md/md.c b/drivers/md/md.c > index 03e35386a8028..83009b0d84092 100644 > --- a/drivers/md/md.c > +++ b/drivers/md/md.c > @@ -1495,6 +1495,9 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru > mdp_super_t *sb = page_address(rdev->sb_page); > __u64 ev1 = md_event(sb); > > + if (rdev->desc_nr < 0 || rdev->desc_nr >= MD_SB_DISKS) > + return -EINVAL; > + > rdev->raid_disk = -1; > clear_bit(Faulty, &rdev->flags); > clear_bit(In_sync, &rdev->flags); [Severity: Medium] Can a hot-added disk with an out-of-bounds sb->this_disk.number still be accepted onto a running persistent v0.90 array? Both md_add_new_disk() and add_bound_rdev() ignore the return value of validate_super(), and unlike super_1_validate(), super_90_validate() does not reset rdev->desc_nr = -1 on failure. When sb->this_disk.number >= MD_SB_DISKS and MD_DISK_JOURNAL is set, bind_rdev_to_array() skips its max_disks check and add_bound_rdev() proceeds to hot_add_disk() with the out-of-bounds rdev->desc_nr intact. When sb->this_disk.number < 0, bind_rdev_to_array() reassigns rdev->desc_nr to an in-range slot and the second validate_super() call in add_bound_rdev() reads a different descriptor slot than sb->this_disk.number. [Severity: Medium] This problem wasn't introduced by this patch, but can unvalidated sb->delta_disks and desc->raid_disk values in super_90_validate() cause out-of-bounds indexing into personality disk arrays [1]? super_90_validate() copies sb->delta_disks into mddev->delta_disks and desc->raid_disk into rdev->raid_disk without bounds checks: drivers/md/md.c:super_90_validate() { ... if (mddev->minor_version >= 91) { mddev->reshape_position = sb->reshape_position; mddev->delta_disks = sb->delta_disks; ... } else if (desc->state & (1<<MD_DISK_SYNC)) { set_bit(In_sync, &rdev->flags); rdev->raid_disk = desc->raid_disk; rdev->saved_raid_disk = desc->raid_disk; ... } When hot-adding via add_bound_rdev(), mddev->pers->hot_add_disk() is called directly after super_90_validate() without analyze_sbs(). Even during assembly, a desc->raid_disk >= 0x80000000 becomes a negative rdev->raid_disk (< -1) with In_sync set, or a negative sb->delta_disks inflates the upper bound in analyze_sbs() past mddev->raid_disks. Personality handlers such as raid1_add_disk() then index conf->mirrors[rdev->raid_disk] out of bounds. [1] https://sashiko.dev/#/bug/linux-9ad89505-1b9e-435b-941d-6a126f8f4adb -- Sashiko AI review · https://sashiko.dev/#/patchset/tencent_3583131EEE6BD2102C15F21A4DEEB86A6208@qq.com?part=1 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH v2] md: reject out-of-bounds desc_nr in super_90_validate() 2026-11-16 8:54 ` sashiko-bot @ 2026-11-16 8:59 ` Shuai Liu 0 siblings, 0 replies; 4+ messages in thread From: Shuai Liu @ 2026-11-16 8:59 UTC (permalink / raw) To: linux-raid Cc: song, yukuai, magiclinan, xiao, linux-kernel, syzbot+c5969d7e0a934b384fd6, sashiko-bot, 847807867 super_90_validate() indexes the on-disk disk descriptor array with rdev->desc_nr without any bounds check: desc = sb->disks + rdev->desc_nr; if (desc->state & (1<<MD_DISK_FAULTY)) ... mdp_super_t carries only MD_SB_DISKS (27) descriptors of 128 bytes each starting at offset 512, so any desc_nr outside [0, MD_SB_DISKS) reads past the end of the 4KB superblock page. Such an out-of-range desc_nr is reachable in several ways: 1. On a running non-persistent array, ADD_NEW_DISK with the MD_DISK_JOURNAL flag reaches add_bound_rdev(), which calls validate_super() unconditionally for journal disks. bind_rdev_to_array() auto-assigns desc_nr = mddev->raid_disks to a new rdev, and its max_disks check is skipped both for journal disks and when mddev->max_disks == 0 (the case for non-persistent arrays, which never set it). With raid_disks > MD_SB_DISKS the assigned desc_nr points past the descriptor array. 2. During assembly, rdev->desc_nr comes straight from the on-disk sb->this_disk.number, which is fully attacker-controlled fuzz input. syzbot hit path 1: a RAID1 array with raid_disks=35 and not_persistent=1 plus a hot-added journal disk made super_90_validate() read sb->disks[35].state at byte offset 512 + 35 * 128 + 16 = 5008, i.e. 912 bytes into the page following the 4096-byte superblock page: BUG: KASAN: use-after-free in super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592 Read of size 4 at addr ffff888073d36390 by task syz-executor291/6009 ... super_90_validate+0x178b/0x18c0 drivers/md/md.c:1592 add_bound_rdev+0x274/0x390 drivers/md/md.c:3012 md_add_new_disk+0xca1/0x1820 drivers/md/md.c:7666 md_ioctl+0x2c1d/0x3700 drivers/md/md.c:8525 blkdev_ioctl+0x5ad/0x6f0 block/ioctl.c:798 (The KASAN report shows use-after-free or slab-out-of-bounds depending on what occupies the neighbouring memory.) super_1_validate() already bounds desc_nr against sb->max_dev; the 0.90 metadata path has no equivalent check. Reject desc_nr outside [0, MD_SB_DISKS) with -EINVAL, which covers both the desc->state reads in super_90_validate() itself and keeps fuzzed on-disk sb->this_disk.number values from being used as an array index. Both callers of validate_super() in the hot-add path previously ignored its return value, so a disk with an out-of-bounds desc_nr would still be accepted onto the array with the invalid state intact, and a later md_update_sb() would then write sb->disks[rdev->desc_nr] out of bounds in super_90_sync() as well. Make add_bound_rdev() and md_add_new_disk() honor the -EINVAL and reject the disk instead, which closes that write path too. Verified with the syzbot reproducer under QEMU with KASAN (7.4-rc3 based config): baseline reproduces the use-after-free on every run, with this patch the reproducer completes with zero KASAN reports across repeated runs. Reported-by: syzbot+c5969d7e0a934b384fd6@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=c5969d7e0a934b384fd6 Signed-off-by: Shuai Liu <847807867@qq.com> --- Changes in v2: - make add_bound_rdev() and md_add_new_disk() honor the validate_super() return value so a disk with an out-of-bounds desc_nr is rejected instead of being hot-added with the invalid state intact; this also closes the super_90_sync() OOB write path mentioned in v1 (Sashiko) - raid1_add_disk() lacking an upper bound on rdev->raid_disk is a related pre-existing issue (Sashiko); it is outside the scope of this patch and flagged for separate discussion drivers/md/md.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/drivers/md/md.c b/drivers/md/md.c index 03e35386a8028..78ee8d932e71a 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -1495,6 +1495,9 @@ static int super_90_validate(struct mddev *mddev, struct md_rdev *freshest, stru mdp_super_t *sb = page_address(rdev->sb_page); __u64 ev1 = md_event(sb); + if (rdev->desc_nr < 0 || rdev->desc_nr >= MD_SB_DISKS) + return -EINVAL; + rdev->raid_disk = -1; clear_bit(Faulty, &rdev->flags); clear_bit(In_sync, &rdev->flags); @@ -3009,9 +3012,10 @@ static int add_bound_rdev(struct md_rdev *rdev) * then added disks for geometry changes, * and should be added immediately. */ - super_types[mddev->major_version]. + err = super_types[mddev->major_version]. validate_super(mddev, NULL/*freshest*/, rdev); - err = mddev->pers->hot_add_disk(mddev, rdev); + if (!err) + err = mddev->pers->hot_add_disk(mddev, rdev); if (err) { md_kick_rdev_from_array(rdev); return err; @@ -7590,9 +7594,11 @@ int md_add_new_disk(struct mddev *mddev, struct mdu_disk_info_s *info) } else rdev->raid_disk = -1; rdev->saved_raid_disk = rdev->raid_disk; - } else - super_types[mddev->major_version]. - validate_super(mddev, NULL/*freshest*/, rdev); + } else if (super_types[mddev->major_version]. + validate_super(mddev, NULL/*freshest*/, rdev)) { + export_rdev(rdev); + return -EINVAL; + } if ((info->state & (1<<MD_DISK_SYNC)) && rdev->raid_disk != info->raid_disk) { /* This was a hot-add request, but events doesn't -- 2.43.0 ^ permalink raw reply related [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-11-16 8:59 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2026-11-15 22:06 [syzbot] [raid?] KASAN: slab-out-of-bounds Read in super_90_validate syzbot 2026-11-16 8:32 ` [PATCH] md: reject out-of-bounds desc_nr in super_90_validate() Shuai Liu 2026-11-16 8:54 ` sashiko-bot 2026-11-16 8:59 ` [PATCH v2] " Shuai Liu
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox