From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail114-240.sinamail.sina.com.cn (mail114-240.sinamail.sina.com.cn [218.30.114.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E8F9215E1FF for ; Tue, 7 May 2024 12:35:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=218.30.114.240 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715085336; cv=none; b=hsW7eU7b7K2gPTbwxtSfNsjcXp1n+nb0IJd3O5zJeka20ncZ0Gf0niwNMKA3dpLf40gaOlFMaJ0U7STFOAUOhWuDudf1Wu63UmFSmoDjjBm2BIUL1LFyxzuBNRXBZ45s6607GBiFMVO0jlKNdo+/lnhEE0LbUNsF5zBhg9wpWno= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715085336; c=relaxed/simple; bh=BOeaLKmGCdfjfOTRkm62sxCYIza5IMMDDnYsPVUQFiQ=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=ft5tIlIhVVXgh082HFU8pdpeDfVN6aVWXmk/pW/wCxZF6xAP4E9AjKmFq7rIxxJ7s7j0ovmMtLaYhQs/ghvE1FgRDCERhCXGPREcq48GHM4Ymwjf+h8TxY5y5aPvur0J2HFgbdOQLJccQdd8FrrYkim9vKj35vQyyw+1K0Tsctg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sina.com; spf=pass smtp.mailfrom=sina.com; arc=none smtp.client-ip=218.30.114.240 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sina.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sina.com X-SMAIL-HELO: localhost.localdomain Received: from unknown (HELO localhost.localdomain)([113.118.71.2]) by sina.com (172.16.235.24) with ESMTP id 663A1FFB0000689F; Tue, 7 May 2024 20:35:09 +0800 (CST) X-Sender: hdanton@sina.com X-Auth-ID: hdanton@sina.com Authentication-Results: sina.com; spf=none smtp.mailfrom=hdanton@sina.com; dkim=none header.i=none; dmarc=none action=none header.from=hdanton@sina.com X-SMAIL-MID: 22048545089433 X-SMAIL-UIID: DE8FC96376674BA5A6F6EF6B0A1AD192-20240507-203509-1 From: Hillf Danton To: syzbot Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] [net?] INFO: rcu detected stall in sock_write_iter (3) Date: Tue, 7 May 2024 20:34:56 +0800 Message-Id: <20240507123456.2204-1-hdanton@sina.com> In-Reply-To: <0000000000000612fa0617dc20f6@google.com> References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On Tue, 07 May 2024 05:14:17 -0700 > syzbot found the following issue on: > > HEAD commit: 7367539ad4b0 Merge tag 'cxl-fixes-6.9-rc7' of git://git.ke.. > git tree: upstream > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1379d9df180000 #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 7367539ad4b0 --- x/net/sched/sch_taprio.c +++ y/net/sched/sch_taprio.c @@ -980,7 +980,9 @@ first_run: rcu_assign_pointer(q->current_entry, next); spin_unlock(&q->current_entry_lock); - hrtimer_set_expires(&q->advance_timer, end_time); + hrtimer_set_expires(&q->advance_timer, + ktime_add(timer->base->get_time(), + ns_to_ktime(NSEC_PER_USEC *200))); rcu_read_lock(); __netif_schedule(sch); --