From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Ezequiel Garcia <elezegarcia@gmail.com>,
Frank Schaefer <fschaefer.oss@googlemail.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [RFC PATCH 2/6] v4l2: add new VIDIOC_DBG_G_CHIP_NAME ioctl.
Date: Wed, 27 Mar 2013 11:11:53 +0100 [thread overview]
Message-ID: <3447822.JyctDNubxl@avalon> (raw)
In-Reply-To: <201303270941.33211.hverkuil@xs4all.nl>
Hi Hans,
On Wednesday 27 March 2013 09:41:33 Hans Verkuil wrote:
> On Wed March 27 2013 02:11:23 Laurent Pinchart wrote:
> > On Monday 18 March 2013 17:38:16 Hans Verkuil wrote:
> > > From: Hans Verkuil <hans.verkuil@cisco.com>
> > >
> > > Simplify the debugging ioctls by creating the VIDIOC_DBG_G_CHIP_NAME
> > > ioctl. This will eventually replace VIDIOC_DBG_G_CHIP_IDENT. Chip
> > > matching is done by the name or index of subdevices or an index to a
> > > bridge chip. Most of this can all be done automatically, so most drivers
> > > just need to provide get/set register ops.
> > >
> > > In particular, it is now possible to get/set subdev registers without
> > > requiring assistance of the bridge driver.
> >
> > My biggest question is why don't we use the media controller API to get
> > the information provided by this new ioctl ?
>
> Because the media controller is implemented by only a handful of drivers,
> and this debug API is used by many more drivers.
Shouldn't we then fix that instead of adding a new ioctl ?
> So I don't really see how this would be feasible today.
>
> > > Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> > > ---
> > >
> > > drivers/media/v4l2-core/v4l2-common.c | 5 +-
> > > drivers/media/v4l2-core/v4l2-dev.c | 5 +-
> > > drivers/media/v4l2-core/v4l2-ioctl.c | 115 ++++++++++++++++++++++++--
> > > include/media/v4l2-ioctl.h | 3 +
> > > include/uapi/linux/videodev2.h | 34 +++++++---
> > > 5 files changed, 146 insertions(+), 16 deletions(-)
> >
> > [snip]
> >
> > > diff --git a/drivers/media/v4l2-core/v4l2-dev.c
> > > b/drivers/media/v4l2-core/v4l2-dev.c index de1e9ab..c0c651d 100644
> > > --- a/drivers/media/v4l2-core/v4l2-dev.c
> > > +++ b/drivers/media/v4l2-core/v4l2-dev.c
> > > @@ -591,9 +591,10 @@ static void determine_valid_ioctls(struct
> > > video_device
> >
> > [snip]
> >
> > > +static int v4l_dbg_g_chip_name(const struct v4l2_ioctl_ops *ops,
> > > + struct file *file, void *fh, void *arg)
> >
> > As this is a debug ioctl that should never be used in application, I would
> > like to guard the whole implementation with #ifdef CONFIG_VIDEO_ADV_DEBUG.
> > This will make sure that no applications will abuse it, as it won't be
> > available in distro kernels.
>
> Agreed. I'll make that change. Actually, it's not so much userspace abuse I
> am worried about, but kernel space abuse. I've found several drivers where
> the bridge driver calls g_chip_ident to get information about subdevice
> drivers. That was never intended and it complicates my work of removing
> g_chip_ident. By putting chip_name under ADV_DEBUG we can avoid similar
> abuse in the future.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-03-27 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 16:38 [RFC PATCH 0/6] Add VIDIOC_DBG_G_CHIP_NAME ioctl Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 1/6] v4l2-common: remove obsolete check for ' at the end of a driver name Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 2/6] v4l2: add new VIDIOC_DBG_G_CHIP_NAME ioctl Hans Verkuil
2013-03-27 1:11 ` Laurent Pinchart
2013-03-27 8:41 ` Hans Verkuil
2013-03-27 10:11 ` Laurent Pinchart [this message]
2013-03-27 10:20 ` Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 3/6] stk1160: remove V4L2_CHIP_MATCH_AC97 placeholder Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 4/6] em28xx: add support for g_chip_name Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 5/6] DocBook media: fix syntax problems in dvbproperty.xml Hans Verkuil
2013-03-18 16:38 ` [RFC PATCH 6/6] DocBook media: add VIDIOC_DBG_G_CHIP_NAME documentation 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=3447822.JyctDNubxl@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=elezegarcia@gmail.com \
--cc=fschaefer.oss@googlemail.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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.