From: Greg KH <gregkh@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: stable@vger.kernel.org, david@unsolicited.net,
hans.verkuil@cisco.com, linux@roeck-us.net,
mchehab@osg.samsung.com, stable-commits@vger.kernel.org
Subject: Re: Patch "Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"" has been added to the 4.4-stable tree
Date: Wed, 15 Apr 2020 15:27:42 +0200 [thread overview]
Message-ID: <20200415132742.GA3461248@kroah.com> (raw)
In-Reply-To: <20200415131412.GD27762@paasikivi.fi.intel.com>
On Wed, Apr 15, 2020 at 04:14:12PM +0300, Sakari Ailus wrote:
> Hi Greg,
>
> On Wed, Apr 15, 2020 at 12:15:54PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > revert-videobuf2-v4l2-verify-planes-array-in-buffer-dequeueing.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From 93f0750dcdaed083d6209b01e952e98ca730db66 Mon Sep 17 00:00:00 2001
> > From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > Date: Wed, 11 May 2016 13:09:34 -0300
> > Subject: Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"
> >
> > From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> >
> > commit 93f0750dcdaed083d6209b01e952e98ca730db66 upstream.
>
> This patch has been already applied to the 4.4-stable tree --- and the
> original has been re-applied as well, just as in upstream.
>
> The original revert was done because another patch was missing the tree
> (commit 93f0750dcdaed083d6209b01e952e98ca730db66 upstream), not because
> there was a problem with the patch itself.
>
> In other words, this patch must be dropped.
Really?
This is a mess. I see the following commits in the stable 4.4 tree:
In the 4.4.9 release the following upstream commit was backported:
2c1f6951a8a8 ("[media] videobuf2-v4l2: Verify planes array in buffer dequeueing")
then in 4.4.11 it was reverted by backporting:
93f0750dcdae ("Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"")
Then finally, in 4.4.19 this commit gets added:
83934b75c368 ("[media] videobuf2-v4l2: Verify planes array in buffer dequeueing")
So, is 83934b75c368 ok to backport, but 2c1f6951a8a8 was not?
Because they look identical to me...
So, what am I missing here?
thanks,
greg k-h
next prev parent reply other threads:[~2020-04-15 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <158694575418840@kroah.com>
2020-04-15 13:14 ` Patch "Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"" has been added to the 4.4-stable tree Sakari Ailus
2020-04-15 13:27 ` Greg KH [this message]
2020-04-15 13:45 ` Sakari Ailus
2020-04-15 13:58 ` Greg KH
2020-04-15 14:45 ` Guenter Roeck
2016-05-14 23:59 gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200415132742.GA3461248@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david@unsolicited.net \
--cc=hans.verkuil@cisco.com \
--cc=linux@roeck-us.net \
--cc=mchehab@osg.samsung.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox