From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 CA0221CABB; Mon, 22 Apr 2024 20:57:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713819472; cv=none; b=TIwGLWzzm2uGPCRfCmWHBuAPrVZkjoVDlfOWUr0DikS7lZtl7cMlAF9j5Df5ZAAWUApaQOY9PNZTcZLNS/gF663TxFD344ZG1XRlmKO0ULPbNAiB3IbNdSjLCfotK+0flc7ASBypfrCtdZyBouWiKFd605XvPoa3qn4sZCj7k0A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713819472; c=relaxed/simple; bh=JZkkbWavLnoJRxVojqyfMx8Q4tIhl0ig8oK0YrTVm/s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=nPHRMjkBpuUZb1dDNbPktfQPBk+/4CESq+PDWP34Ffi9k1xc71dqrBzjvUPFRpcS4+6UACGNPcmLabSLFgnXcGilR5iYRTiGZQLI3pTWsUFoz5Kid1fVN2eGQJAV2U1GONbdJr+2nrS8X2iQhhFkQb04aX3SbVrIMHd0oSW2Duo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 Received: by smtp.kernel.org (Postfix) with ESMTPSA id A8CF4C113CC; Mon, 22 Apr 2024 20:57:50 +0000 (UTC) Message-ID: <9e76f971-b2d7-424a-bf21-c6cf5cd4a3f3@xs4all.nl> Date: Mon, 22 Apr 2024 22:57:48 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [Linux Kernel Bugs] KASAN: slab-use-after-free Read in cec_queue_msg_fh and 4 other crashes in the cec device (`cec_ioctl`) Content-Language: en-US, nl To: "Yang, Chenyuan" , "linux-media@vger.kernel.org" , "linux-kernel@vger.kernel.org" Cc: "jani.nikula@intel.com" , "syzkaller@googlegroups.com" , "mchehab@kernel.org" , "Zhao, Zijie" , "Zhang, Lingming" References: <526380BE-57AC-493D-A7B0-B8F0ECC0FE0A@illinois.edu> <2e5f1e92-7fad-4a74-b375-1e194ff08ce6@xs4all.nl> <49a68c10-9549-4fd8-b929-d4c7a9c8debf@xs4all.nl> <7E36CBBD-F2AD-4D98-8D4E-F52E62C3E812@illinois.edu> From: Hans Verkuil In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 22/04/2024 20:54, Yang, Chenyuan wrote: > Hi Hans, > > Such timeout logs happen all the time when I execute the C program attached. > > ``` > gcc -pthread repro.c -o exe > ./exe > ``` > > The logs are from QEMU: > > ``` > Debian GNU/Linux 11 syzkaller ttyS0 > > syzkaller login: [ 326.705401][ T51] Bluetooth: hci0: sending frame failed (-49) > [ 326.707063][ T4466] Bluetooth: hci0: Opcode 0x1003 failed: -49 > [ 335.945400][ T4466] Bluetooth: hci0: Opcode 0x1003 failed: -110 > [ 335.945417][ T51] Bluetooth: hci0: command 0x1003 tx timeout > [ 390.885042][ T2019] cec-vivid-000-vid-out0: transmit timed out > [ 390.894890][ T2050] cec-vivid-002-vid-cap0: transmit timed out > [ 390.895540][ T2034] cec-vivid-001-vid-cap0: transmit timed out > [ 390.905041][ T2067] cec-vivid-003-vid-out0: transmit timed out > [ 392.985033][ T2018] cec-vivid-000-vid-cap0: transmit timed out Hmm, I don't see this. With how many CPU cores is the qemu instance configured? And with what module options is the vivid module loaded? Regards, Hans > ... > ``` > > Best, > Chenyuan > > On 4/22/24, 10:04 AM, "Hans Verkuil" > wrote: > > > Hi Chenyuan, > > > My apologies for the delay, I missed your email. > > > On 26/02/2024 13:27, Yang, Chenyuan wrote: >> Hi Hans, >> >> Thank you for your continued efforts in investigating this bug and implementing the new patch! >> >> Regarding the two warnings, they have been addressed by this new patch and are no longer reproducible. Additionally, I conducted a 48-hour fuzzing test on the CEC driver, which has successfully eliminated the previous hanging issue. >> >> One thing to note that the system will now log timeout events: >> ``` >> [ 2281.265385][ T2034] cec-vivid-001-vid-out0: transmit timed out >> [ 2282.994510][ T2017] cec-vivid-000-vid-cap0: transmit timed out >> [ 2283.063484][ T2050] cec-vivid-002-vid-out0: transmit timed out >> [ 2283.073468][ T2065] cec-vivid-003-vid-cap0: transmit timed out >> [ 2283.373518][ T2033] cec-vivid-001-vid-cap0: transmit timed out >> [ 2285.113544][ T2018] cec-vivid-000-vid-out0: transmit timed out >> [ 2285.193502][ T2050] cec-vivid-002-vid-out0: transmit timed out >> [ 2285.193570][ T2065] cec-vivid-003-vid-cap0: transmit timed out >> [ 2285.513570][ T2033] cec-vivid-001-vid-cap0: transmit timed out >> ``` > > > Is this happening all the time, or just once in a (long?) while? > > > Regards, > > > Hans > > >> >> Best, >> Chenyuan >> >> From: Hans Verkuil > >> Date: Friday, February 23, 2024 at 8:44 AM >> To: Yang, Chenyuan >, linux-media@vger.kernel.org >, linux-kernel@vger.kernel.org > >> Cc: jani.nikula@intel.com >, syzkaller@googlegroups.com >, mchehab@kernel.org >, Zhao, Zijie >, Zhang, Lingming > >> Subject: Re: [Linux Kernel Bugs] KASAN: slab-use-after-free Read in cec_queue_msg_fh and 4 other crashes in the cec device (`cec_ioctl`) >> Hi Chenyuan, >> >> Here is another patch for you to try. I think it is good for blocking CEC_ADAP_S_LOG_ADDRS >> ioctl calls, but if the filehandle is in non-blocking mode, I'm still not certain it >> is correct. But one issue at a time :-) >> >> Regards, >> >> Hans >> >> diff --git a/drivers/media/cec/core/cec-adap.c b/drivers/media/cec/core/cec-adap.c >> index 559a172ebc6c..a493cbce2456 100644 >> --- a/drivers/media/cec/core/cec-adap.c >> +++ b/drivers/media/cec/core/cec-adap.c >> @@ -936,8 +936,7 @@ int cec_transmit_msg_fh(struct cec_adapter *adap, struct cec_msg *msg, >> */ >> mutex_unlock(&adap->lock); >> wait_for_completion_killable(&data->c); >> - if (!data->completed) >> - cancel_delayed_work_sync(&data->work); >> + cancel_delayed_work_sync(&data->work); >> mutex_lock(&adap->lock); >> >> /* Cancel the transmit if it was interrupted */ >> @@ -1575,9 +1574,12 @@ static int cec_config_thread_func(void *arg) >> */ >> static void cec_claim_log_addrs(struct cec_adapter *adap, bool block) >> { >> - if (WARN_ON(adap->is_configuring || adap->is_configured)) >> + if (WARN_ON(adap->is_claiming_log_addrs || >> + adap->is_configuring || adap->is_configured)) >> return; >> >> + adap->is_claiming_log_addrs = true; >> + >> init_completion(&adap->config_completion); >> >> /* Ready to kick off the thread */ >> @@ -1592,6 +1594,7 @@ static void cec_claim_log_addrs(struct cec_adapter *adap, bool block) >> wait_for_completion(&adap->config_completion); >> mutex_lock(&adap->lock); >> } >> + adap->is_claiming_log_addrs = false; >> } >> >> /* >> diff --git a/drivers/media/cec/core/cec-api.c b/drivers/media/cec/core/cec-api.c >> index 67dc79ef1705..3ef915344304 100644 >> --- a/drivers/media/cec/core/cec-api.c >> +++ b/drivers/media/cec/core/cec-api.c >> @@ -178,7 +178,7 @@ static long cec_adap_s_log_addrs(struct cec_adapter *adap, struct cec_fh *fh, >> CEC_LOG_ADDRS_FL_ALLOW_RC_PASSTHRU | >> CEC_LOG_ADDRS_FL_CDC_ONLY; >> mutex_lock(&adap->lock); >> - if (!adap->is_configuring && >> + if (!adap->is_claiming_log_addrs && !adap->is_configuring && >> (!log_addrs.num_log_addrs || !adap->is_configured) && >> !cec_is_busy(adap, fh)) { >> err = __cec_s_log_addrs(adap, &log_addrs, block); >> @@ -664,6 +664,8 @@ static int cec_release(struct inode *inode, struct file *filp) >> list_del_init(&data->xfer_list); >> } >> mutex_unlock(&adap->lock); >> + >> + mutex_lock(&fh->lock); >> while (!list_empty(&fh->msgs)) { >> struct cec_msg_entry *entry = >> list_first_entry(&fh->msgs, struct cec_msg_entry, list); >> @@ -681,6 +683,7 @@ static int cec_release(struct inode *inode, struct file *filp) >> kfree(entry); >> } >> } >> + mutex_unlock(&fh->lock); >> kfree(fh); >> >> cec_put_device(devnode); >> diff --git a/include/media/cec.h b/include/media/cec.h >> index 10c9cf6058b7..cc3fcd0496c3 100644 >> --- a/include/media/cec.h >> +++ b/include/media/cec.h >> @@ -258,6 +258,7 @@ struct cec_adapter { >> u16 phys_addr; >> bool needs_hpd; >> bool is_enabled; >> + bool is_claiming_log_addrs; >> bool is_configuring; >> bool must_reconfigure; >> bool is_configured; >> > > > > >