[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140902141739.GB31793@fieldses.org>
Date: Tue, 2 Sep 2014 10:17:39 -0400
From: Bruce Fields <bfields@...ldses.org>
To: Boaz Harrosh <openosd@...il.com>
Cc: Trond Myklebust <trond.myklebust@...marydata.com>,
Shakil A Khan <shakilk1729@...il.com>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Linux Kernel mailing list <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
William Andros Adamson <andros@...app.com>,
Jeffrey Layton <jlayton@...marydata.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] Next branch: authgss: authgss.c: Fix warnings for
uninitizlized variable expire
On Tue, Sep 02, 2014 at 04:59:45PM +0300, Boaz Harrosh wrote:
> uninitialized_var was made to be a friend not an enemy, in the face of real
> ugliness it is the best we can do. And that is what it should communicate to
> everyone. Why has it become everyone's favorite blasphemy I do not know.
Not personally claiming it should never be used, just that this
particular case is kind of extreme, since unless I'm missing a real
compilication it's basically just:
if (ctx)
assign to expire
...
if (ctx)
use expire
A compiler wouldn't have to be that smart to actually prove to itself
that expire is initialized at the last step, and that it's not only
failing to do that but actually flagging it as possibly unitialized is
weird.
--b.
--
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