Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755046Ab0KBTcQ (ORCPT ); Tue, 2 Nov 2010 15:32:16 -0400 Received: from dsl-67-204-24-19.acanac.net ([67.204.24.19]:37122 "EHLO mail.ellipticsemi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752732Ab0KBTcK (ORCPT ); Tue, 2 Nov 2010 15:32:10 -0400 Date: Tue, 2 Nov 2010 15:31:50 -0400 From: Nick Bowler To: Lukas Czerner Cc: kevin granade , "Ted Ts'o" , Stefan Richter , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: ext4_lazyinit_thread: 'ret' may be used uninitialized in this function Message-ID: <20101102193150.GA14504@elliptictech.com> Mail-Followup-To: Lukas Czerner , kevin granade , Ted Ts'o , Stefan Richter , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org References: <20101102182911.GE25614@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Elliptic Technologies Inc. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 15 On 2010-11-02 15:19 -0400, Lukas Czerner wrote: > Hmm this relies on the fact that if the first part of the condition > would not be true, the second part (after and) would never be invoked, > however I am not really sure that we can rely on that on every > architecture, or can we ? This behaviour of the && operator is guaranteed by the C standard. -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/