From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Sutter Subject: Re: [nft PATCH RFC] libnftables: Make output_fp default to /dev/null Date: Mon, 20 Nov 2017 13:38:51 +0100 Message-ID: <20171120123851.GT32305@orbyte.nwl.cc> References: <20171116143224.GA17329@salvia> <20171116191415.19404-1-phil@nwl.cc> <20171120123204.GA17403@salvia> <20171120123313.GB17403@salvia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@vger.kernel.org To: Pablo Neira Ayuso Return-path: Received: from orbyte.nwl.cc ([151.80.46.58]:42358 "EHLO orbyte.nwl.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750952AbdKTMix (ORCPT ); Mon, 20 Nov 2017 07:38:53 -0500 Content-Disposition: inline In-Reply-To: <20171120123313.GB17403@salvia> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Mon, Nov 20, 2017 at 01:33:13PM +0100, Pablo Neira Ayuso wrote: > On Mon, Nov 20, 2017 at 01:32:04PM +0100, Pablo Neira Ayuso wrote: > > Hi Phil, > > > > On Thu, Nov 16, 2017 at 08:14:15PM +0100, Phil Sutter wrote: > > > Ensure output_fp is never NULL which allows to drop all respective > > > checks. > > > > > > Signed-off-by: Phil Sutter > > > --- > > > Hi Pablo, > > > > > > This is how I understood your suggestion to use /dev/null. While > > > implementing it though, I had an idea for a much simpler solution, > > > namely just rejecting NULL in nft_set_output() and therefore forcing the > > > application to deal with opening /dev/null if no output is desired. What > > > do you think about that? > > > > I like your idea of rejecting NULL. OK, cool. > BTW, why does nft_set_output() return FILE *? Is there any usecase for > this? It's a quick way to change output_fp and store its old value. Current users are nft_run_cmd_from_*(). I could introduce nft_get_output() to make the return value a dedicated success/fail indicator if you prefer that, otherwise I'd just make nft_set_output() return NULL in error case. Cheers, Phil