[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1204131200330.15151@kaball-desktop>
Date: Fri, 13 Apr 2012 12:05:14 +0100
From: Stefano Stabellini <stefano.stabellini@...citrix.com>
To: Samuel Thibault <samuel.thibault@...-lyon.org>
CC: Jesper Juhl <jj@...osbits.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Gerd Hoffmann <kraxel@...e.de>,
Alan Cox <alan@...ux.intel.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: tty, hvc, xen: leak? dead code? everything is fine?
On Thu, 12 Apr 2012, Samuel Thibault wrote:
> Jesper Juhl, le Thu 12 Apr 2012 23:33:20 +0200, a écrit :
> > Or *if* there's actually no way 'info->intfw' can actually be anything but
> > NULL in this case,
>
> There is no way that it's both non-NULL and the if was entered above: if
> the if was entered, the content of info is zeroes (kzalloc).
Yep. Thanks Samuel for the quick answer.
In more details: if the console has already been configured info->intf
is not NULL.
On the other hand if the console hasn't been configured yet info->intf
is NULL.
If the console has just been allocated by the kzalloc then obviously
it hasn't been configured and in fact info->intf is NULL.
Powered by blists - more mailing lists