All of lore.kernel.org
 help / color / mirror / Atom feed
From: "李佑鸿 " <dayou5941@163.com>
To: syzbot <syzbot+a53c2918175b36cfd601@syzkaller.appspotmail.com>
Cc: agk@redhat.com, bmarzins@redhat.com, dm-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	liyouhong@kylinos.cn, magiclinan@didiglobal.com,
	mpatocka@redhat.com, sashiko-bot@kernel.org, snitzer@kernel.org,
	song@kernel.org, stable@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, xiao@kernel.org, yukuai@fygo.io
Subject: Re:Re: [syzbot] [raid?] BUG: unable to handle kernel paging request in remove_spares
Date: Thu, 19 Nov 2026 14:07:27 +0800 (CST)	[thread overview]
Message-ID: <4ac2cebb.48be.1a1f26ac925.Coremail.dayou5941@163.com> (raw)
In-Reply-To: <6afdad2f.15a38f0c.5f8d.0009.GAE@google.com>


















At 2026-11-18 21:50:39, "syzbot" <syzbot+a53c2918175b36cfd601@syzkaller.appspotmail.com> wrote:
>syzbot has found a reproducer for the following issue on:
>
>HEAD commit:    20eef29b7c84 Merge tag 'arc-fixes-7.4' of git://git.kernel..
>git tree:       upstream
>console output: https://syzkaller.appspot.com/x/log.txt?x=1186ff3d580000
>kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
>dashboard link: https://syzkaller.appspot.com/bug?extid=a53c2918175b36cfd601
>compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
>syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17f8f94d580000
>C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=173f9411580000
>
>Downloadable assets:
>disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-20eef29b.raw.xz
>vmlinux: https://storage.googleapis.com/syzbot-assets/bb852a1ddb76/vmlinux-20eef29b.xz
>kernel image: https://storage.googleapis.com/syzbot-assets/4c636c3f4242/bzImage-20eef29b.xz
>
>AI-generated root cause summary:
>In the MD (Multiple Devices / RAID) subsystem, md_start_sync is scheduled as a
>work item on the md_misc workqueue to initiate resynchronization or manage spare
>devices. For read-only arrays (!md_is_rdwr(mddev)), md_start_sync executes
>remove_and_add_spares(), which invokes remove_spares(). However, md_start_sync
>fails to verify whether the array's personality (mddev->pers) is still valid
>before calling into personality operations, and array stop/detach sequences do
>not ensure that mddev->sync_work is completely halted or prevented from running
>after mddev->pers is cleared. When remove_spares() executes with mddev->pers ==
>NULL, it attempts to invoke mddev->pers->hot_remove_disk (located at offset
>0x50), triggering a NULL pointer dereference crash.
>
>full analysis:  https://syzkaller.appspot.com/x/ai_root_cause?x=a53c2918175b36cfd601
>
>IMPORTANT: if you fix the issue, please add the following tag to the commit:
>Reported-by: syzbot+a53c2918175b36cfd601@syzkaller.appspotmail.com
>
>Oops: general protection fault, probably for non-canonical address 0xdffffc000000000a: 0000 [#1] SMP KASAN NOPTI
>KASAN: null-ptr-deref in range [0x0000000000000050-0x0000000000000057]
>CPU: 2 UID: 0 PID: 66 Comm: kworker/2:2 Not tainted syzkaller #0 PREEMPT(full) 
>Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
>Workqueue: md_misc md_start_sync
>RIP: 0010:remove_spares+0x147/0x540 drivers/md/md.c:10182
>Code: 67 60 f9 45 84 ff 74 55 e8 e6 6c 60 f9 48 8b 44 24 10 80 38 00 0f 85 83 03 00 00 49 8b 45 08 48 8d 78 50 48 89 fa 48 c1 ea 03 <42> 80 3c 22 00 0f 85 78 03 00 00 48 89 de 4c 89 ef 48 8b 40 50 2e
>RSP: 0018:ffffc90000d47a10 EFLAGS: 00010206
>RAX: 0000000000000000 RBX: ffff888059649108 RCX: 0000000000000000
>RDX: 000000000000000a RSI: ffffffff88ae1bfa RDI: 0000000000000050
>RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
>R10: ffff8880596491cf R11: 0000000000000000 R12: dffffc0000000000
>R13: ffff888059648058 R14: ffff888059648070 R15: 0000000000000001
>FS:  0000000000000000(0000) GS:ffff8880d4669000(0000) knlGS:0000000000000000
>CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>CR2: 0000001b30924008 CR3: 0000000051ca3000 CR4: 0000000000352ef0
>Call Trace:
> <TASK>
> remove_and_add_spares+0x6c7/0x7f0 drivers/md/md.c:10207
> md_start_sync+0x736/0xea0 drivers/md/md.c:10323
> 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
> </TASK>
>Modules linked in:
>---[ end trace 0000000000000000 ]---
>RIP: 0010:remove_spares+0x147/0x540 drivers/md/md.c:10182
>Code: 67 60 f9 45 84 ff 74 55 e8 e6 6c 60 f9 48 8b 44 24 10 80 38 00 0f 85 83 03 00 00 49 8b 45 08 48 8d 78 50 48 89 fa 48 c1 ea 03 <42> 80 3c 22 00 0f 85 78 03 00 00 48 89 de 4c 89 ef 48 8b 40 50 2e
>RSP: 0018:ffffc90000d47a10 EFLAGS: 00010206
>RAX: 0000000000000000 RBX: ffff888059649108 RCX: 0000000000000000
>RDX: 000000000000000a RSI: ffffffff88ae1bfa RDI: 0000000000000050
>RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
>R10: ffff8880596491cf R11: 0000000000000000 R12: dffffc0000000000
>R13: ffff888059648058 R14: ffff888059648070 R15: 0000000000000001
>FS:  0000000000000000(0000) GS:ffff8880d4669000(0000) knlGS:0000000000000000
>CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>CR2: 0000001b30924008 CR3: 0000000051ca3000 CR4: 0000000000352ef0
>----------------
>Code disassembly (best guess):
>   0:	67 60                	addr32 (bad)
>   2:	f9                   	stc
>   3:	45 84 ff             	test   %r15b,%r15b
>   6:	74 55                	je     0x5d
>   8:	e8 e6 6c 60 f9       	call   0xf9606cf3
>   d:	48 8b 44 24 10       	mov    0x10(%rsp),%rax
>  12:	80 38 00             	cmpb   $0x0,(%rax)
>  15:	0f 85 83 03 00 00    	jne    0x39e
>  1b:	49 8b 45 08          	mov    0x8(%r13),%rax
>  1f:	48 8d 78 50          	lea    0x50(%rax),%rdi
>  23:	48 89 fa             	mov    %rdi,%rdx
>  26:	48 c1 ea 03          	shr    $0x3,%rdx
>* 2a:	42 80 3c 22 00       	cmpb   $0x0,(%rdx,%r12,1) <-- trapping instruction
>  2f:	0f 85 78 03 00 00    	jne    0x3ad
>  35:	48 89 de             	mov    %rbx,%rsi
>  38:	4c 89 ef             	mov    %r13,%rdi
>  3b:	48 8b 40 50          	mov    0x50(%rax),%rax

>  3f:	2e                   	cs


v5 fix is here:
https://lore.kernel.org/linux-raid/20261112013523.120428-1-dayou5941@163.com/

Thanks,
Li Youhong

      reply	other threads:[~2026-11-19  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 11:09 [syzbot] [raid?] BUG: unable to handle kernel paging request in remove_spares syzbot
2026-11-18 13:50 ` syzbot
2026-11-19  6:07   ` 李佑鸿  [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ac2cebb.48be.1a1f26ac925.Coremail.dayou5941@163.com \
    --to=dayou5941@163.com \
    --cc=agk@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=liyouhong@kylinos.cn \
    --cc=magiclinan@didiglobal.com \
    --cc=mpatocka@redhat.com \
    --cc=sashiko-bot@kernel.org \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+a53c2918175b36cfd601@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiao@kernel.org \
    --cc=yukuai@fygo.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.