From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) (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 22DD1186E40 for ; Fri, 1 Nov 2024 10:55:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730458523; cv=none; b=uzqCEjqZO3UxMjfYqrNFDXR/zeO4XU+DhIPWiviNJodNVshYyHeTePuY8tpBISPEGDOu66M3P4VKBlmwww0shzzi+8t7yd5qdbkPw+OR/FI1PRMdjVNFE3DQwVkbpkX+sTYK+WDNMSCjO40arD/SlwhRN/+TNhPJQw+1oXe0uck= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730458523; c=relaxed/simple; bh=QsUe6fSQf6mGTRUNT4acXIgf2YQM285WnECE08WtvIo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qRdr2jXFVqzCjFOv00uCbl6Z0QvfPHLoh2S7sauFGk4ebaQ+zMdfCkGaBCVSRwJqS10+FcjI/u6OBxc0AlljK2J0NO2T3CZX9NL5ur8een6UkmiJAPmm53YvOJxBNq2ECBpmwJ35Yws1J/GGaWV8yaXOw4+FU/SSmRhq6z7e1aY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=kernel.org; spf=fail smtp.mailfrom=kernel.org; arc=none smtp.client-ip=192.198.163.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=kernel.org Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=kernel.org X-CSE-ConnectionGUID: KvOs8hJSSDKmeMuxQ4m78g== X-CSE-MsgGUID: RcDaj6QMTEOjiK33Bbuqew== X-IronPort-AV: E=McAfee;i="6700,10204,11242"; a="30334170" X-IronPort-AV: E=Sophos;i="6.11,249,1725346800"; d="scan'208";a="30334170" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Nov 2024 03:55:21 -0700 X-CSE-ConnectionGUID: yM9fdRu8T92QKPFQQiyPqg== X-CSE-MsgGUID: vDnbDOEnRfilStIda7gUPQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.11,249,1725346800"; d="scan'208";a="113716536" Received: from smile.fi.intel.com ([10.237.72.154]) by orviesa002.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Nov 2024 03:55:19 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.98) (envelope-from ) id 1t6pJD-0000000A0Cr-2X1U; Fri, 01 Nov 2024 12:55:15 +0200 Date: Fri, 1 Nov 2024 12:55:15 +0200 From: Andy Shevchenko To: Li Huafei Cc: mchehab@kernel.org, hdegoede@redhat.com, sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org, linux-media@vger.kernel.org, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH] media: atomisp: Add check for rgby_data memory allocation failure Message-ID: References: <20241101154823.3067891-1-lihuafei1@huawei.com> Precedence: bulk X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Fri, Nov 01, 2024 at 12:16:03PM +0200, Andy Shevchenko wrote: > On Fri, Nov 01, 2024 at 05:57:36PM +0800, Li Huafei wrote: > > On 2024/11/1 16:30, Andy Shevchenko wrote: > > > On Fri, Nov 01, 2024 at 11:48:23PM +0800, Li Huafei wrote: > > >> In ia_css_3a_statistics_allocate(), there is no check on the allocation > > >> result of the rgby_data memory. If rgby_data is not successfully > > >> allocated, it may trigger the assert(host_stats->rgby_data) assertion in > > >> ia_css_s3a_hmem_decode(). Adding a check to fix this potential issue. > > > > > > Not sure if this code even run on currently supported hardware / firmware, > > > but fix looks okay. > > > > > >> Fixes: ad85094b293e ("Revert "media: staging: atomisp: Remove driver"") > > > > > > No, this is an intermediate commit, you should find the original, which is > > > earlier in the history. > > > > Apologies, the correct fix tag should be: > > > > Fixes: a49d25364dfb ("staging/atomisp: Add support for the Intel IPU v2") > > > > If this fix can be applied, do I need to send a v2, or can you help add the Fix tag? > > Up to Hans, but there is another question left unanswered about SoB chain. > Can you clarify that? Ah, sorry, I misread the From and answered to the wrong thread. Fixes tag seems better now. -- With Best Regards, Andy Shevchenko