[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3p77q27-8495-sss2-3r38-r1448nqsoop@vanv.qr>
Date: Fri, 2 Dec 2022 10:18:44 +0100 (CET)
From: Jan Engelhardt <jengelh@...i.de>
To: Al Viro <viro@...iv.linux.org.uk>
cc: Li Qiong <liqiong@...china.com>,
Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Florian Westphal <fw@...len.de>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, netfilter-devel@...r.kernel.org,
kernel-janitors@...r.kernel.org, coreteam@...filter.org,
Yu Zhe <yuzhe@...china.com>
Subject: Re: [PATCH] netfilter: initialize 'ret' variable
On Friday 2022-12-02 08:13, Al Viro wrote:
>On Fri, Dec 02, 2022 at 03:03:31PM +0800, Li Qiong wrote:
>> The 'ret' should need to be initialized to 0, in case
>> return a uninitialized value.
>
>Why is 0 the right value? And which case would it be?
>We clearly need to know that to figure out which return
>value would be correct for it...
Judging from the error-handling branches,
it should be ret = NF_ACCEPT.
Powered by blists - more mailing lists