[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKXHbyN+CmAm3x6XU9nKDMFsShGX90NsZw5emQ+ZfWovmnCOXQ@mail.gmail.com>
Date: Fri, 30 Jan 2015 18:06:33 +0100
From: Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>
To: Valdis.Kletnieks@...edu
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Gulsah Kose <gulsah.1004@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jarod Wilson <jarod@...sonet.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Tuomas Tynkkynen <tuomas.tynkkynen@....fi>,
Martin Kaiser <martin@...ser.cx>, linux-media@...r.kernel.org,
Aya Mahfouz <mahfouz.saif.elyazal@...il.com>
Subject: Re: [PATCH] staging: media: lirc: lirc_zilog: Fix for possible null
pointer dereference
2015-01-30 14:09 GMT+01:00 <Valdis.Kletnieks@...edu>:
> On Fri, 30 Jan 2015 16:00:02 +0300, Dan Carpenter said:
>
>> > > - if (ir == NULL) {
>> > > - dev_err(ir->l.dev, "close: no private_data attached to the file
> !\n");
>> >
>> > Yes, the dev_err() call is an obvious thinko.
>> >
>> > However, I'm not sure whether removing it entirely is right either. If
>> > there *should* be a struct IR * passed there, maybe some other printk()
>> > should be issued, or even a WARN_ON(!ir), or something?
>>
>> We set filep->private_data to non-NULL in open() so I don't think it can
>> be NULL here.
>
> Then probably the *right* fix is to remove the *entire* if statement, as
> we can't end up doing the 'return -ENODEV'....
Hi
Ok, but think or know. Who knows?
Do the remove if patch?
Kind regards
Rickard Strandqvist
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists