From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bali.collaboradmins.com (bali.collaboradmins.com [148.251.105.195]) (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 6240E2868A9 for ; Fri, 23 Jan 2026 23:18:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=148.251.105.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769210292; cv=none; b=B+4T+HGcZwgcwXQqlhCd6kBlu0barBKl9qbSHWkLrI28R62ZasqFb8E89VjlknRzIX/x4PapYj+HuCSBcSsXzDT4oNyvyCAhc4/roj7UobgO02e0tGzvrXJgpzS7VMinc9Z1Cq54iK/FvG+AvHAnMr8JwulkU23Cf6sknaVZXvE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769210292; c=relaxed/simple; bh=wHgjORyqTwml6ZZCoMQV+QxMxcgExVvZFnvtJJH7wWc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=XOVoKyKXhWoNT0wMOtsrvqS+CdNrhW6ryf6+Ihb/Faxbg75dp0dd18nYzN3mGow0/A0/u279xgAVG3oh0WcNVKSWzKN+DuSaAiNDRtyKPDVImL8UhrpUd2LIADRXgf8FERsMlNoBCSBwu+0Jeer94PdFP8CZCi9y0L/lZ5BQVtg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=UzRCEGFd; arc=none smtp.client-ip=148.251.105.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="UzRCEGFd" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1769210289; bh=wHgjORyqTwml6ZZCoMQV+QxMxcgExVvZFnvtJJH7wWc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=UzRCEGFd6JoUn5SpkXKpCxLisafY/Uw8B8paZfqPRJZNOc3txMUBidOy37fDYzp77 DYV7jyQVhxIFrVCtepVpkmX4csqklhga2049ZH41mnV5UHfMyZvVuKsmo8JrkuG35N 0s/fdtaeQln5qR8BC4dn2ojvuGgWlKLyWxGJeZ4PGk2huhk0sJtsQieSooG7HdEG/a DubYoCu/IQQ8mlM/gzmHkIoagF7Xpf2lgIbk2R2bdluIGkQ6hiEDcuZ+3Zz4W1/0Yh nDwl0YXVHx92LrJIhhRaYTPhTH2cNJvpB/d8OCJWPhfYsgbxsXDNg+sydUpqdS/4Uz 8PbZ9aUE4E1ow== Received: from [192.168.1.90] (unknown [82.79.138.145]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: cristicc) by bali.collaboradmins.com (Postfix) with ESMTPSA id C79E617E0181; Sat, 24 Jan 2026 00:18:08 +0100 (CET) Message-ID: <8bdb6ea8-9434-4fa6-87ad-4c2f2697a3e5@collabora.com> Date: Sat, 24 Jan 2026 01:18:08 +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: [PATCH 0/6] Rockchip DRM use-after-free & null-ptr-deref fixes To: Chaoyi Chen Cc: Sandy Huang , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Andy Yan , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Dmitry Baryshkov , Dmitry Baryshkov , kernel@collabora.com, dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org References: <20260122-drm-rk-fixes-v1-0-3942f185750e@collabora.com> <8e770288-f29b-4e72-b5a6-e3cfd77b87fb@rock-chips.com> Content-Language: en-US From: Cristian Ciocaltea In-Reply-To: <8e770288-f29b-4e72-b5a6-e3cfd77b87fb@rock-chips.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Chaoyi, On 1/22/26 4:27 AM, Chaoyi Chen wrote: > Hi Cristian, > > On 1/22/2026 7:17 AM, Cristian Ciocaltea wrote: >> The first three patches in the series are fixes for use-after-free & >> null-ptr-deref related issues found in dw_dp and inno-hdmi Rockchip DRM >> drivers. >> > > Have you tried calling unbind() and bind() multiple times? > In this case, can DRM still work properly? Do you have any specific usecase in mind? The tests performed so far were mostly focused on reloading the rockchipdrm module, which is how I actually noticed those issues. Regards, Cristian