From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH 08/30] media: v4l2-ioctl: fix some "too small" warnings
Date: Mon, 26 Mar 2018 17:28:55 -0300 [thread overview]
Message-ID: <20180326172808.1271b10b@vento.lan> (raw)
In-Reply-To: <2278589.Q4kJOvEtWm@avalon>
Em Mon, 26 Mar 2018 21:47:33 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> On Monday, 26 March 2018 13:08:16 EEST Mauro Carvalho Chehab wrote:
> > Em Fri, 23 Mar 2018 23:53:56 +0200 Sakari Ailus escreveu:
> > > On Fri, Mar 23, 2018 at 07:56:54AM -0400, Mauro Carvalho Chehab wrote:
> > >> While the code there is right, it produces three false positives:
> > >> drivers/media/v4l2-core/v4l2-ioctl.c:2868 video_usercopy() error:
> > >> copy_from_user() 'parg' too small (128 vs 16383)
> > >> drivers/media/v4l2-core/v4l2-ioctl.c:2868 video_usercopy() error:
> > >> copy_from_user() 'parg' too small (128 vs 16383)
> > >> drivers/media/v4l2-core/v4l2-ioctl.c:2876 video_usercopy() error:
> > >> memset() 'parg' too small (128 vs 16383)> >
> > >> Store the ioctl size on a cache var, in order to suppress those.
> > >
> > > I have to say I'm not a big fan of changing perfectly fine code in order
> > > to please static analysers.
> >
> > Well, there's a side effect of this patch: it allows gcc to better
> > optimize the text size, with is good:
> >
> > text data bss dec hex filename
> > 34538 2320 0 36858
> > 8ffa old/drivers/media/v4l2-core/v4l2-ioctl.o 34490 2320 0
> > 36810 8fca new/drivers/media/v4l2-core/v4l2-ioctl.o
> > > What's this, smatch? I wonder if it could be fixed
> > > instead of changing the code. That'd be presumably a lot more work though.
> >
> > Yes, the warnings came from smatch. No idea how easy/hard would be to
> > change it.
> >
> > > On naming --- "size" is rather more generic, but it's not a long function
> > > either. I'd be a bit more specific, e.g. ioc_size or arg_size.
> >
> > Agreed.
> >
> > I'll add the enclosed patch changing it to ioc_size.
> >
> >
> > Thanks,
> > Mauro
> >
> > [PATCH] media: v4l2-ioctl: rename a temp var that stores _IOC_SIZE(cmd)
> >
> > Instead of just calling it as "size", let's name it as "ioc_size",
> > as it reflects better its contents.
> >
> > As this is constant along the function, also mark it as const.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>
> I would have expected a v2 of the original patch, but it seems you pushed it
> to the public master branch before giving anyone a change to review it
> (Sakari's review came 10h after the past was posted).
>
> Patches need to be reviewed before being applied, and that applies to all
> patches, regarding of the author. Please refrain from merging future patches
> before they get reviewed.
It shouldn't have pushed. It happened due to some script errors,
when I was handling a request from Hans to push upstream some fixes
for -rc7, as mentioned on IRC:
https://linuxtv.org/irc/irclogger_log/v4l?date=2018-03-23,Fri
As I said there:
"If someone finds an issue on the warning fixes, I can revert or apply a fixup
I really hate when things like that happens :-("
Thanks,
Mauro
next prev parent reply other threads:[~2018-03-26 20:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 11:56 [PATCH 01/30] media: dvbdev: handle ENOMEM error at dvb_module_probe() Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 02/30] media: imx-media-utils: fix a warning Mauro Carvalho Chehab
2018-03-23 12:03 ` Dan Carpenter
2018-03-23 11:56 ` [PATCH 03/30] media: dvb_frontend: add proper __user annotations Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 04/30] media: vpss: fix annotations for vpss_regs_base2 Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 05/30] media: rca: declare formats var as static Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 06/30] media: ov5670: get rid of a series of __be warnings Mauro Carvalho Chehab
2018-03-23 21:45 ` Sakari Ailus
2018-03-23 11:56 ` [PATCH 07/30] media: v4l2-tpg-core: avoid buffer overflows Mauro Carvalho Chehab
2018-03-23 12:35 ` Hans Verkuil
2018-03-23 11:56 ` [PATCH 08/30] media: v4l2-ioctl: fix some "too small" warnings Mauro Carvalho Chehab
2018-03-23 21:53 ` Sakari Ailus
2018-03-26 10:08 ` Mauro Carvalho Chehab
2018-03-26 10:28 ` Sakari Ailus
2018-03-26 18:47 ` Laurent Pinchart
2018-03-26 20:28 ` Mauro Carvalho Chehab [this message]
2018-03-27 11:31 ` Laurent Pinchart
2018-03-23 11:56 ` [PATCH 09/30] media: sp887x: fix a warning Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 10/30] media: tvaudio: improve error handling Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 11/30] media: bttv-input: better handle errors at I2C transfer Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 12/30] media: solo6x10: simplify the logic at solo_p2m_dma_desc() Mauro Carvalho Chehab
2018-03-23 11:56 ` [PATCH 13/30] media: cx88: fix two warnings Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 14/30] media: cx23885: fix a warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 15/30] soc_camera: fix a weird cast on printk Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 16/30] media: videobuf-dma-sg: Fix a weird cast Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 17/30] media: ivtvfb: Cleanup some warnings Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 18/30] media: s2255drv: fix a casting warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 19/30] media: saa7134-input: improve error handling Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 20/30] media: ir-kbd-i2c: improve error handling code Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 21/30] media: ir-kbd-i2c: change the if logic to avoid a warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 22/30] media: zoran: don't cast pointers to print them Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 23/30] media: solo6x10: get rid of an address space warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 24/30] media: saa7134-alsa: don't use casts to print a buffer address Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 25/30] media: vivid-radio-rx: add a cast to avoid a warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 26/30] media: zr364xx: avoid casting just to print pointer address Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 27/30] media: em28xx-input: improve error handling code Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 28/30] media: tm6000: avoid casting just to print pointer address Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 29/30] media: tda9840: cleanup a warning Mauro Carvalho Chehab
2018-03-23 11:57 ` [PATCH 30/30] media: cec-core: fix a bug at cec_error_inj_write() Mauro Carvalho Chehab
2018-03-23 12:24 ` 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=20180326172808.1271b10b@vento.lan \
--to=mchehab@s-opensource.com \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.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