Re: [PATCH][V2][next] netfilter: synproxy: ensure zero is returned on non-error return path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH][V2][next] netfilter: synproxy: ensure zero is returned on non-error return path
From: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>
Date: Wed, 19 Jun 2019 12:51:22 +0200
Cc: Jozsef Kadlecsik <kadlec@xxxxxxxxxxxxx>, Florian Westphal <fw@xxxxxxxxx>, "David S . Miller" <davem@xxxxxxxxxxxxx>, netfilter-devel@xxxxxxxxxxxxxxx, coreteam@xxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, kernel-janitors@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20190618142244.16463-1-colin.king@canonical.com>
User-agent: NeoMutt/20170113 (1.7.2)

On Tue, Jun 18, 2019 at 03:22:44PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@xxxxxxxxxxxxx>
> 
> Currently functions nf_synproxy_{ipc4|ipv6}_init return an uninitialized
> garbage value in variable ret on a successful return.  Fix this by
> returning zero on success.

Applied, thanks Colin.

References:
- [PATCH][V2][next] netfilter: synproxy: ensure zero is returned on non-error return path
  - From: Colin King

Prev by Date: Re: [PATCH nft] nft-test.py: use tempfile module
Next by Date: Re: [PATCH v3 nf-next] netfilter: enable set expiration time for set elements
Previous by thread: [PATCH][V2][next] netfilter: synproxy: ensure zero is returned on non-error return path
Next by thread: [PATCH nft] evaluate: do not allow to list anonymous sets via list command
Index(es):
- Date
- Thread

[Index of Archives] [Netfitler Users] [Berkeley Packet Filter] [LARTC] [Bugtraq] [Yosemite Forum]

Powered by Linux