From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH for v3.17] v4l2-ioctl: don't set PRIV_MAGIC unconditionally in g_fmt()
Date: Mon, 21 Jul 2014 11:11:07 +0200 [thread overview]
Message-ID: <18748136.AVYGmbiGvH@avalon> (raw)
In-Reply-To: <53CBBFAB.6030907@xs4all.nl>
Hi Hans,
Thank you for the patch.
On Sunday 20 July 2014 15:10:03 Hans Verkuil wrote:
> Regression fix:
>
> V4L2_PIX_FMT_PRIV_MAGIC should only be set for the VIDEO_CAPTURE and
> VIDEO_OUTPUT buffer types, and not for any others. In the case of
> the win format this overwrites a pointer value that is passed in from
> userspace.
>
> Since it is already set for the VIDEO_CAPTURE and VIDEO_OUTPUT cases
> anyway this line can just be dropped.
It's set after calling the vidioc_g_fmt_vid_cap or vidioc_g_fmt_vid_out
operation, which means that driver will not see the flag being set. Couldn't
that be an issue ?
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
> drivers/media/v4l2-core/v4l2-ioctl.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
> b/drivers/media/v4l2-core/v4l2-ioctl.c index e620387..c11a13d 100644
> --- a/drivers/media/v4l2-core/v4l2-ioctl.c
> +++ b/drivers/media/v4l2-core/v4l2-ioctl.c
> @@ -1143,8 +1143,6 @@ static int v4l_g_fmt(const struct v4l2_ioctl_ops *ops,
> bool is_tx = vfd->vfl_dir != VFL_DIR_RX;
> int ret;
>
> - p->fmt.pix.priv = V4L2_PIX_FMT_PRIV_MAGIC;
> -
> /*
> * fmt can't be cleared for these overlay types due to the 'clips'
> * 'clipcount' and 'bitmap' pointers in struct v4l2_window.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-07-21 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 13:10 [PATCH for v3.17] v4l2-ioctl: don't set PRIV_MAGIC unconditionally in g_fmt() Hans Verkuil
2014-07-21 9:11 ` Laurent Pinchart [this message]
2014-07-21 9:29 ` Hans Verkuil
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=18748136.AVYGmbiGvH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.