[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50AD60EC.3090302@suse.cz>
Date: Thu, 22 Nov 2012 00:17:00 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Greg KH <gregkh@...uxfoundation.org>
CC: Sachin Kamat <sachin.kamat@...aro.org>,
linux-kernel@...r.kernel.org, patches@...aro.org
Subject: Re: [PATCH 1/1] tty: vt: Remove redundant null check before kfree.
On 11/22/2012 12:00 AM, Greg KH wrote:
> On Wed, Nov 21, 2012 at 11:43:34PM +0100, Jiri Slaby wrote:
>> On 11/21/2012 03:46 PM, Greg KH wrote:
>>> On Wed, Nov 21, 2012 at 10:49:07AM +0530, Sachin Kamat wrote:
>>>> --- a/drivers/tty/vt/consolemap.c
>>>> +++ b/drivers/tty/vt/consolemap.c
>>>> @@ -410,10 +410,8 @@ static void con_release_unimap(struct uni_pagedir *p)
>>>> kfree(p->inverse_translations[i]);
>>>> p->inverse_translations[i] = NULL;
>>>> }
>>>> - if (p->inverse_trans_unicode) {
>>>> - kfree(p->inverse_trans_unicode);
>>>> - p->inverse_trans_unicode = NULL;
>>>> - }
>>>> + kfree(p->inverse_trans_unicode);
>>>> + p->inverse_trans_unicode = NULL;
>>>
>>> kfree with NULL is a no-op, but the line after that just caused a kernel
>>> crash if it was NULL, so I can't accept this type of thing.
>>
>> Greg, I'm not sure -- what do you mean here? The change actually looks
>> fine to me... We do not dereference p->inverse_trans_unicode there.
>
> If we never dereference it, why is it being set to NULL?
I'm not disputing the assignment. Let it there. But I do not see any
issues with the patch. What problem do you see exactly?
--
js
suse labs
--
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