Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp747578ybz; Wed, 15 Apr 2020 18:05:20 -0700 (PDT) X-Google-Smtp-Source: APiQypKh0n/tXeqS9AtpzGPduTT/9VLTeg4pOXBwcw4TzFwtvCRSIfF59GlmnR3Kl5A2GSW2r+C4 X-Received: by 2002:a17:906:390a:: with SMTP id f10mr7335901eje.74.1586999120320; Wed, 15 Apr 2020 18:05:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586999120; cv=none; d=google.com; s=arc-20160816; b=LEzUOLXvqdXfAI66UD+JVLu5o+ukxLkeyOf0Sm0UHM6MiFWvKqNxYNC9oDR92N/SHB kE01eg+Y15a03nweDPiKhRMn/KQ8Bh+pnKKw4URRWmHr+BTkxNvQ11dhXSx+pozGkXqd XUZ8JuJ9HLzeCQelu/6EIBMJk99vIakRvBOfw6rUgr0UGpc+4R87qWFkqT21J6cRgPzk yjNmVRiExhsSUapMUjDQG1/JOozDCjjlCU+FNff9rp6nHQ3X/MBNb6UPs9RAAU0ntc5i rCLa27N+14tM2Ik3/IJju2VT+nepN+/S03YpoFzAFyDNGDHbKNrVFWaC+4uWHTQEZHSK qeQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=YmoGzPhSYhYGSWM5wgpNyYVYjJV4XWVyBHmrFTZns4A=; b=Dj+MabY9tH65S5K1qh+Y0R2HO21fYpL7ViDD3kn7fnpCYHBao41e6MdLIML0by7EMB U/4qv8z4skMpRFx0qQvWm2r+X3HHNsWLkHThhIq0Dpx0nI2Iv9IaHQVNbLybxbBufbOw T5x1tuOsDfvLgysHzhDK1LYfkn+DFq7FAr5VeIsV9n+nFFYWkYXFDOKplOmhyerVTWQ1 MY3ROb2PZ1BYK48aag2Hq0nMfRuCVCGQb+Fe5vH0rrA99FhY2cm81rubzgoTf/KKhrx3 lNejMhluyPqXwcEZPzgZBeuyGIZnWjq+Tdwn//hzX0I5PU9ffgfv224cLHAtAH/FCJmi diow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=EPWOSpRu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x25si6421158ejs.434.2020.04.15.18.04.56; Wed, 15 Apr 2020 18:05:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=EPWOSpRu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2441878AbgDOTwA (ORCPT + 99 others); Wed, 15 Apr 2020 15:52:00 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:10177 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2406367AbgDOTvk (ORCPT ); Wed, 15 Apr 2020 15:51:40 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Wed, 15 Apr 2020 12:49:47 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Wed, 15 Apr 2020 12:51:37 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Wed, 15 Apr 2020 12:51:37 -0700 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 15 Apr 2020 19:51:36 +0000 Received: from [10.2.171.241] (10.124.1.5) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 15 Apr 2020 19:51:35 +0000 Subject: Re: [RFC PATCH v7 6/9] media: tegra: Add Tegra210 Video input driver To: Dmitry Osipenko CC: , , , , , , , , , , , References: <1586919463-30542-1-git-send-email-skomatineni@nvidia.com> <1586919463-30542-7-git-send-email-skomatineni@nvidia.com> <4118112f-f865-5460-6319-d71271fd78d1@gmail.com> <6afa951e-d904-f3c0-053f-82a02fb18979@nvidia.com> <5954a7e1-910e-7f48-56d3-e671b56ead74@nvidia.com> <786949a9-8507-7723-f29b-b91a216bfd28@nvidia.com> From: Sowjanya Komatineni Message-ID: <2ad9352f-cb65-1643-e540-a21f9c570266@nvidia.com> Date: Wed, 15 Apr 2020 12:51:34 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To DRHQMAIL107.nvidia.com (10.27.9.16) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1586980187; bh=YmoGzPhSYhYGSWM5wgpNyYVYjJV4XWVyBHmrFTZns4A=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Transfer-Encoding: Content-Language; b=EPWOSpRu7TsrjEd/ScsdhZxozGsUk37bS5oPWzI1MM/YA6irJ9u7NeG9BF7JQTPBx ZCpQXx/Fu/DvwCEu68r8L6meReI4ZmKxao2VBmu2ndU2q+oCbvg43Tl6WLq0bmTN9n WeG6Q3BVdAf/nkpqrKpW/ltQG2XMnpeUDkkn9c0tHPKFeFXXnFogTElu4eaD42zMKH zC8gaARqM7sEu5ojCgV49LZ/TntagOM6QBJwnCWTUMxzyEXc8Ngku8EfnvkVV8bMLF evNNeubKyN+hTRC6RQAAGihjeYch5ara8kXQbMVxqhtFAvmlT/WTvYiZE4lkhzRCVd f+K6faAr3Ca0w== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/15/20 12:21 PM, Dmitry Osipenko wrote: > External email: Use caution opening links or attachments > > > 15.04.2020 21:53, Sowjanya Komatineni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > ... >>>>>>>> Have you tried to test this driver under KASAN? I suspect that >>>>>>>> you just >>>>>>>> masked the problem, instead of fixing it. >> Tested with kmemleak scan and did not see any memory leaks > You should get use-after-free and not memleak. I don't see use-after-free bugs during the testing. But as mentioned when direct vi/csi client driver unbind happens while=20 video device node is kept opened, vi driver remove will free vi=20 structure memory but actual video device memory which is part of=20 channels remains but list head gets lost when vi structure is freed. So, when device node is released and executes release callback as list=20 head is lost it can't free allocated channels which is not good. This happens only with direct host1x client vi/csi driver unbind. Need to find better place to free host1x client driver data structure to=20 allow direct client driver unbind->bind.