All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+293a57918b36cfae3d48@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (3)
Date: Fri, 17 Jul 2026 07:48:01 -0700	[thread overview]
Message-ID: <6a5a40a1.42649fcc.6186.0029.GAE@google.com> (raw)
In-Reply-To: <20260717134133.38390-1-kartikey406@gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: task hung in ext4_page_mkwrite

I
INFO: task syz.0.1038:10254 blocked in I/O wait for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.1038      state:D stack:0     pid:10254 tgid:10250 ppid:8212   task_flags:0x400140 flags:0x00000001
Call trace:
 __switch_to+0x2b0/0x6e0 arch/arm64/kernel/process.c:775 (T)
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x1370/0x2d80 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0x13c/0x20c kernel/sched/core.c:7326
 io_schedule+0x1c/0xe0 kernel/sched/core.c:8154
 folio_wait_bit_common+0x6b8/0xa30 mm/filemap.c:1323
 __folio_lock+0x2c/0x3c mm/filemap.c:1704
 folio_lock include/linux/pagemap.h:1157 [inline]
 ext4_page_mkwrite+0x864/0xd1c fs/ext4/inode.c:6833
 do_page_mkwrite+0x138/0x2b8 mm/memory.c:3684
 wp_page_shared mm/memory.c:4085 [inline]
 do_wp_page+0x1270/0x4074 mm/memory.c:4304
 handle_pte_fault mm/memory.c:6395 [inline]
 __handle_mm_fault mm/memory.c:6517 [inline]
 handle_mm_fault+0x123c/0x253c mm/memory.c:6686
 do_page_fault+0x4b0/0xb88 arch/arm64/mm/fault.c:751
 do_mem_abort+0x70/0x194 arch/arm64/mm/fault.c:984
 el1_abort+0x50/0x74 arch/arm64/kernel/entry-common.c:322
 el1h_64_sync_handler+0xdc/0x130 arch/arm64/kernel/entry-common.c:449
 el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:589
 __arch_copy_to_user+0xf0/0x240 arch/arm64/lib/copy_template.S:129 (P)
 processcompl_compat+0x160/0x8dc drivers/usb/core/devio.c:2222
 proc_reapurb_compat drivers/usb/core/devio.c:2256 [inline]
 usbdev_do_ioctl drivers/usb/core/devio.c:2627 [inline]
 usbdev_ioctl+0x324/0x1990 drivers/usb/core/devio.c:2826
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __arm64_sys_ioctl+0x14c/0x1c4 fs/ioctl.c:583
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736
 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594

Showing all locks held in the system:
1 lock held by ksoftirqd/0/14:
1 lock held by khungtaskd/31:
 #0: ffff800088cb6f20 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffff800088cb6f20 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffff800088cb6f20 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x4c/0x188 kernel/locking/lockdep.c:6775
3 locks held by kworker/u8:3/40:
 #0: ffff0000ccf96140 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff0000ccf96140 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x734/0x10b8 kernel/workqueue.c:3405
 #1: ffff80008eff7c40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffff80008eff7c40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x73c/0x10b8 kernel/workqueue.c:3405
 #2: ffff800089d93380 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
3 locks held by kworker/u8:7/3673:
3 locks held by kworker/1:3/4460:
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x734/0x10b8 kernel/workqueue.c:3405
 #1: ffff800096067c40 (deferred_process_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffff800096067c40 (deferred_process_work){+.+.}-{0:0}, at: process_scheduled_works+0x73c/0x10b8 kernel/workqueue.c:3405
 #2: ffff800089d93380 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
2 locks held by getty/4493:
 #0: ffff0000cf2630a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff80009248b2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x348/0xf78 drivers/tty/n_tty.c:2211
3 locks held by kworker/0:3/4757:
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x734/0x10b8 kernel/workqueue.c:3405
 #1: ffff800094407c40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffff800094407c40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0x73c/0x10b8 kernel/workqueue.c:3405
 #2: ffff0000c8e4a250 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x198/0x320 drivers/net/netdevsim/fib.c:1490
4 locks held by kworker/1:5/4810:
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff0000c002b540 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x734/0x10b8 kernel/workqueue.c:3405
 #1: ffff800097867c40 ((work_completion)(&helper->damage_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffff800097867c40 ((work_completion)(&helper->damage_work)){+.+.}-{0:0}, at: process_scheduled_works+0x73c/0x10b8 kernel/workqueue.c:3405
 #2: ffff0000c4db6a70 (&helper->lock){+.+.}-{4:4}, at: drm_fb_helper_fb_dirty drivers/gpu/drm/drm_fb_helper.c:324 [inline]
 #2: ffff0000c4db6a70 (&helper->lock){+.+.}-{4:4}, at: drm_fb_helper_damage_work+0x120/0xbc0 drivers/gpu/drm/drm_fb_helper.c:365
 #3: ffff0000c6e2c128 (&dev->master_mutex){+.+.}-{4:4}, at: drm_master_internal_acquire+0x24/0x78 drivers/gpu/drm/drm_auth.c:435
4 locks held by syz.0.1038/10254:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_do_ioctl drivers/usb/core/devio.c:2610 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_ioctl+0x120/0x1990 drivers/usb/core/devio.c:2826
 #1: ffff0000d2f8d078 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_trylock include/linux/mmap_lock.h:611 [inline]
 #1: ffff0000d2f8d078 (&mm->mmap_lock){++++}-{4:4}, at: get_mmap_lock_carefully mm/mmap_lock.c:441 [inline]
 #1: ffff0000d2f8d078 (&mm->mmap_lock){++++}-{4:4}, at: lock_mm_and_find_vma+0x38/0x2c0 mm/mmap_lock.c:501
 #2: ffff0000d5dd6548 (sb_pagefaults){.+.+}-{0:0}, at: percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 #2: ffff0000d5dd6548 (sb_pagefaults){.+.+}-{0:0}, at: __sb_start_write include/linux/fs/super.h:19 [inline]
 #2: ffff0000d5dd6548 (sb_pagefaults){.+.+}-{0:0}, at: sb_start_pagefault include/linux/fs/super.h:159 [inline]
 #2: ffff0000d5dd6548 (sb_pagefaults){.+.+}-{0:0}, at: ext4_page_mkwrite+0x1a4/0xd1c fs/ext4/inode.c:6804
 #3: ffff0000daa87598 (mapping.invalidate_lock#2){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
 #3: ffff0000daa87598 (mapping.invalidate_lock#2){++++}-{4:4}, at: ext4_page_mkwrite+0x1c8/0xd1c fs/ext4/inode.c:6807
1 lock held by syz.1.1039/10291:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.2.1040/10332:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.3.1041/10378:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.4.1042/10425:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.5.1043/10473:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.6.1044/10520:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.7.1045/10574:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.8.1046/10621:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz.9.1047/10670:
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #0: ffff0000ca8ea1d8 (&dev->mutex){....}-{4:4}, at: usbdev_open+0x138/0x674 drivers/usb/core/devio.c:1054
1 lock held by syz-executor/10677:
 #0: ffff800089d93380 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80

=============================================



Tested on:

commit:         a13c140c Linux 7.2-rc3
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=17924cb9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ecdef466b08b9772
dashboard link: https://syzkaller.appspot.com/bug?extid=293a57918b36cfae3d48
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11666cb9580000


       reply	other threads:[~2026-07-17 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260717134133.38390-1-kartikey406@gmail.com>
2026-07-17 14:48 ` syzbot [this message]
     [not found] <20260718020535.46460-1-kartikey406@gmail.com>
2026-07-18  4:44 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (3) syzbot
     [not found] <20260717105327.37079-1-kartikey406@gmail.com>
2026-07-17 11:57 ` syzbot
     [not found] <20260717091456.36085-1-kartikey406@gmail.com>
2026-07-17 10:36 ` syzbot
     [not found] <20260717000803.14708-1-kartikey406@gmail.com>
2026-07-17  4:39 ` syzbot
2026-07-16  7:50 syzbot

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=6a5a40a1.42649fcc.6186.0029.GAE@google.com \
    --to=syzbot+293a57918b36cfae3d48@syzkaller.appspotmail.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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.