From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jean Delvare <khali@linux-fr.org>, Dan Carpenter <error27@gmail.com>
Cc: "Beholder Intl. Ltd. Dmitry Belimov" <d.belimov@gmail.com>,
hermann pitton <hermann-pitton@arcor.de>,
Douglas Schilling Landgraf <dougsland@redhat.com>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] video/saa7134: potential null dereferences in debug
Date: Sat, 29 May 2010 04:29:54 +0000 [thread overview]
Message-ID: <20100529012954.25490c3a@pedra> (raw)
In-Reply-To: <20100522225921.585b2d72@hyperion.delvare>
Em Sat, 22 May 2010 22:59:21 +0200
Jean Delvare <khali@linux-fr.org> escreveu:
> Hi Dan,
>
> On Sat, 22 May 2010 22:15:35 +0200, Dan Carpenter wrote:
> > I modified the dprintk and i2cdprintk macros to handle null dev and ir
> > pointers. There are two couple places that call dprintk() when "dev" is
> > null. One is in get_key_msi_tvanywhere_plus() and the other is in
> > get_key_flydvb_trio().
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> >
> > diff --git a/drivers/media/video/saa7134/saa7134-input.c b/drivers/media/video/saa7134/saa7134-input.c
> > index e5565e2..e14f2f8 100644
> > --- a/drivers/media/video/saa7134/saa7134-input.c
> > +++ b/drivers/media/video/saa7134/saa7134-input.c
> > @@ -61,9 +61,9 @@ MODULE_PARM_DESC(disable_other_ir, "disable full codes of "
> > "alternative remotes from other manufacturers");
> >
> > #define dprintk(fmt, arg...) if (ir_debug) \
> > - printk(KERN_DEBUG "%s/ir: " fmt, dev->name , ## arg)
> > + printk(KERN_DEBUG "%s/ir: " fmt, dev ? dev->name : "<null>", ## arg)
> > #define i2cdprintk(fmt, arg...) if (ir_debug) \
> > - printk(KERN_DEBUG "%s/ir: " fmt, ir->name , ## arg)
> > + printk(KERN_DEBUG "%s/ir: " fmt, ir ? ir->name : "<null>", ## arg)
> >
> > /* Helper functions for RC5 and NEC decoding at GPIO16 or GPIO18 */
> > static int saa7134_rc5_irq(struct saa7134_dev *dev);
>
> I would have used "(null)" instead of "<null>" for consistency with
> lib/vsprintf.c:string().
>
> But more importantly, I suspect that a better fix would be to not call
> these macros when dev or ir, respectively, is NULL. The faulty dprintk
> calls in get_key_msi_tvanywhere_plus() and get_key_flydvb_trio() could
> be replaced with i2cdprintk (which is misnamed IMHO, BTW.)
Agreed.
Dan, could you please rework your patch according with Jean's feedback?
Thanks,
Mauro
--
Cheers,
Mauro
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jean Delvare <khali@linux-fr.org>, Dan Carpenter <error27@gmail.com>
Cc: "Beholder Intl. Ltd. Dmitry Belimov" <d.belimov@gmail.com>,
hermann pitton <hermann-pitton@arcor.de>,
Douglas Schilling Landgraf <dougsland@redhat.com>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] video/saa7134: potential null dereferences in debug code
Date: Sat, 29 May 2010 01:29:54 -0300 [thread overview]
Message-ID: <20100529012954.25490c3a@pedra> (raw)
In-Reply-To: <20100522225921.585b2d72@hyperion.delvare>
Em Sat, 22 May 2010 22:59:21 +0200
Jean Delvare <khali@linux-fr.org> escreveu:
> Hi Dan,
>
> On Sat, 22 May 2010 22:15:35 +0200, Dan Carpenter wrote:
> > I modified the dprintk and i2cdprintk macros to handle null dev and ir
> > pointers. There are two couple places that call dprintk() when "dev" is
> > null. One is in get_key_msi_tvanywhere_plus() and the other is in
> > get_key_flydvb_trio().
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> >
> > diff --git a/drivers/media/video/saa7134/saa7134-input.c b/drivers/media/video/saa7134/saa7134-input.c
> > index e5565e2..e14f2f8 100644
> > --- a/drivers/media/video/saa7134/saa7134-input.c
> > +++ b/drivers/media/video/saa7134/saa7134-input.c
> > @@ -61,9 +61,9 @@ MODULE_PARM_DESC(disable_other_ir, "disable full codes of "
> > "alternative remotes from other manufacturers");
> >
> > #define dprintk(fmt, arg...) if (ir_debug) \
> > - printk(KERN_DEBUG "%s/ir: " fmt, dev->name , ## arg)
> > + printk(KERN_DEBUG "%s/ir: " fmt, dev ? dev->name : "<null>", ## arg)
> > #define i2cdprintk(fmt, arg...) if (ir_debug) \
> > - printk(KERN_DEBUG "%s/ir: " fmt, ir->name , ## arg)
> > + printk(KERN_DEBUG "%s/ir: " fmt, ir ? ir->name : "<null>", ## arg)
> >
> > /* Helper functions for RC5 and NEC decoding at GPIO16 or GPIO18 */
> > static int saa7134_rc5_irq(struct saa7134_dev *dev);
>
> I would have used "(null)" instead of "<null>" for consistency with
> lib/vsprintf.c:string().
>
> But more importantly, I suspect that a better fix would be to not call
> these macros when dev or ir, respectively, is NULL. The faulty dprintk
> calls in get_key_msi_tvanywhere_plus() and get_key_flydvb_trio() could
> be replaced with i2cdprintk (which is misnamed IMHO, BTW.)
Agreed.
Dan, could you please rework your patch according with Jean's feedback?
Thanks,
Mauro
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-05-29 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 20:15 [patch] video/saa7134: potential null dereferences in debug code Dan Carpenter
2010-05-22 20:15 ` Dan Carpenter
2010-05-22 20:59 ` [patch] video/saa7134: potential null dereferences in debug Jean Delvare
2010-05-22 20:59 ` [patch] video/saa7134: potential null dereferences in debug code Jean Delvare
2010-05-24 15:59 ` [patch v2] video/saa7134: change dprintk() to i2cdprintk() Dan Carpenter
2010-05-24 15:59 ` Dan Carpenter
2010-05-24 18:04 ` Jean Delvare
2010-05-24 18:04 ` Jean Delvare
2010-05-29 4:29 ` Mauro Carvalho Chehab [this message]
2010-05-29 4:29 ` [patch] video/saa7134: potential null dereferences in debug code Mauro Carvalho Chehab
2010-05-29 7:06 ` [patch] video/saa7134: potential null dereferences in debug Jean Delvare
2010-05-29 7:06 ` [patch] video/saa7134: potential null dereferences in debug code Jean Delvare
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=20100529012954.25490c3a@pedra \
--to=mchehab@redhat.com \
--cc=d.belimov@gmail.com \
--cc=dougsland@redhat.com \
--cc=error27@gmail.com \
--cc=hermann-pitton@arcor.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=khali@linux-fr.org \
--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.