From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f69.google.com (mail-oo1-f69.google.com [209.85.161.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2BB773DB635 for ; Wed, 18 Mar 2026 15:43:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773848587; cv=none; b=BHzNeNlK5Zcw1J8/8XilNDvnGzNpkpIh6vope0JgI4xFyEWY4A+1ye9l1C6el8jllB93JuDyPpPov6xtmrPzWHf476G3SigONU++8N9pTGZNOopB3yXdfTlMOzMgOZotAmQpLkJaEZQ+ffnRJvx1+dwyLkfEqlFkMFBUA4udvl0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773848587; c=relaxed/simple; bh=sW1NLiw3kynL84SVBgOKehN1hgb0cs9xhJyKycc+qpU=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=Mm2z8YiDitSsug7u+q+uPuJ7JDN4jUGSAPN08TIhx2/u+vXrhu+g5vIbhoDqN6LuoOzSwT3EEkPZdXXub+/MzALuDcpk91GOcOFy/ECRi0M0RFm5q95qq5jF/DB0ObDgqrE1AJ6NF21FnVazMDrzSIkfnSlZOOmcOYZfcduT2zU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.69 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f69.google.com with SMTP id 006d021491bc7-67c0da9bd62so620200eaf.1 for ; Wed, 18 Mar 2026 08:43:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1773848582; x=1774453382; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NuBoJn7c+NFFczu+JB4JDDLX/3oIvju9emG/o2QYmdA=; b=ItgV3r/ePRn7Zo3YQuFbv6/qhDax6aayztX9yb2BjhBW+7ezDroFMPORXpI8MmHGLn QCdzmV7Z6ajNg+PjxbDDfDgfW6gm3nF9Z+8jNLSpUzTQYwmMLW+kRwP5NGZecvfZWr4W EZ38DoyxDvdxgcIRzwckgKeGWat28ZeLC1Y9H549NiOhsIhwt0aGDr98uNdas/87bGs0 F32VnRApKATeY7gz/p7IXMEI2fk/Oh3D8HUU3IFl4C/KjWi1mWyVCZB4baKUMgnGKAGI Z9K/UjChmfogDLDwpL8/SMfteFKGcMXPPMfiVUB8V1uaB1hnNAheg5WR0QGClSHllBmi g0GA== X-Forwarded-Encrypted: i=1; AJvYcCUbrjjFn+8607tuhdIzx5xPVQKXIcThpmKp1/SQLxJ58a46vGLyDpiYks8+lRzu1Vc4Qs5qF+DkRc0e3Zw=@vger.kernel.org X-Gm-Message-State: AOJu0YymoTF97APPP7N7BKEPs6z0h2f8ltMhd668ZgFU4TPYDIPcQlUN EXWKXUVDWbvzOQ7h7R6QYYinWhuDNYZeLamELrxylvVg3IC+P6DqtKWMON3uhh2clI+t67RAUrK Z04Gsj2/mtWznj0HvlkEtKuL/W6fVbj5uurkGgxKH28Gq5Zomu7Sf/tBcvAs= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:4911:b0:67a:467:b2b9 with SMTP id 006d021491bc7-67c0da9f0eemr2019400eaf.21.1773848581984; Wed, 18 Mar 2026 08:43:01 -0700 (PDT) Date: Wed, 18 Mar 2026 08:43:01 -0700 In-Reply-To: <20260318145708.895955-1-kartikey406@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69bac805.050a0220.3a088d.0006.GAE@google.com> Subject: Re: [syzbot] [kernel?] INFO: task hung in ret_from_fork (4) From: syzbot To: kartikey406@gmail.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO: task hung in synchronize_rcu INFO: task kworker/u8:5:131 blocked for more than 161 seconds. Not tainted syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u8:5 state:D stack:19936 pid:131 tgid:131 ppid:2 task_flags:0x4208060 flags:0x00080000 Workqueue: events_unbound fsnotify_connector_destroy_workfn Call Trace: context_switch kernel/sched/core.c:5298 [inline] __schedule+0x15dd/0x52d0 kernel/sched/core.c:6911 __schedule_loop kernel/sched/core.c:6993 [inline] schedule+0x164/0x360 kernel/sched/core.c:7008 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75 do_wait_for_common kernel/sched/completion.c:100 [inline] __wait_for_common kernel/sched/completion.c:121 [inline] wait_for_common kernel/sched/completion.c:132 [inline] wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153 __synchronize_srcu+0x329/0x3e0 kernel/rcu/srcutree.c:1520 Tested on: commit: a989fde7 Merge tag 'libnvdimm-fixes-7.0-rc5' of git://.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1724a06a580000 kernel config: https://syzkaller.appspot.com/x/.config?x=b643133b3e44c9fd dashboard link: https://syzkaller.appspot.com/bug?extid=7c11975a7e4a2735d529 compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8 patch: https://syzkaller.appspot.com/x/patch.diff?x=1140cf4a580000