linux-kernel - Re: [PATCH v2] media: ov5640: fix get_light

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2024121425-ended-coastal-0c46@gregkh>
Date: Sat, 14 Dec 2024 19:41:10 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: Michal Simek <michal.simek@....com>, linux-kernel@...r.kernel.org,
	monstr@...str.eu, michal.simek@...inx.com, git@...inx.com,
	stable@...nel.org, Sam Bobrowicz <sam@...te-embedded.com>,
	Hans Verkuil <hans.verkuil@...co.com>,
	Mauro Carvalho Chehab <mchehab@...nel.org>,
	Steve Longerbeam <slongerbeam@...il.com>,
	"open list:V4L2 CAMERA SENSOR DRIVERS" <linux-media@...r.kernel.org>
Subject: Re: [PATCH v2] media: ov5640: fix get_light_freq on auto

On Sat, Dec 14, 2024 at 06:24:39PM +0000, Sakari Ailus wrote:
> Hi Greg,
> 
> On Fri, Dec 13, 2024 at 12:12:18PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 13, 2024 at 11:30:38AM +0100, Michal Simek wrote:
> > > Hi Ailus, +Greg
> > > 
> > > On 12/13/24 09:54, Sakari Ailus wrote:
> > > > Hi Michal,
> > > > 
> > > > Thanks for the patch.
> > > > 
> > > > On Fri, Nov 22, 2024 at 09:28:01AM +0100, Michal Simek wrote:
> > > > > From: Sam Bobrowicz <sam@...te-embedded.com>
> > > > > 
> > > > > Light frequency was not properly returned when in auto
> > > > > mode and the detected frequency was 60Hz.
> > > > > 
> > > > > Fixes: 19a81c1426c1 ("[media] add Omnivision OV5640 sensor driver")
> > > > > Signed-off-by: Sam Bobrowicz <sam@...te-embedded.com>
> > > > > Signed-off-by: Michal Simek <michal.simek@....com>
> > > > > Cc: <stable@...nel.org>
> > 
> > That address is totally acceptable.
> 
> The documentation (Documentation/process/stable-kernel-rules.rst) tells to
> use stable@...r.kernel.org nevertheless (we're not discussing the latter
> option here):
> 
> To have a patch you submit for mainline inclusion later automatically picked up
> for stable trees, add this tag in the sign-off area::
> 
>   Cc: stable@...r.kernel.org
> 
> Use ``Cc: stable@...nel.org`` instead when fixing unpublished vulnerabilities:
> it reduces the chance of accidentally exposing the fix to the public by way of
> 'git send-email', as mails sent to that address are not delivered anywhere.

Yes, either works.  But to keep the "signal" of "hey, look, a security
bug!" down, feel free to use stable@...nel.oorg also everywhere just to
make the bad guys have to do more work :)

thanks,

greg k-h