netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Scrivano <gscrivan@redhat.com>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH] iptables: accept lock file name at runtime
Date: Wed, 15 Jul 2020 08:19:31 +0200	[thread overview]
Message-ID: <87sgdtti4s.fsf@redhat.com> (raw)
In-Reply-To: <20200714232709.GC23632@orbyte.nwl.cc> (Phil Sutter's message of "Wed, 15 Jul 2020 01:27:09 +0200")

Phil Sutter <phil@nwl.cc> writes:

> Hi,
>
> On Tue, Jul 14, 2020 at 06:52:06PM +0200, Giuseppe Scrivano wrote:
>> allow users to override at runtime the lock file to use through the
>> XTABLES_LOCKFILE environment variable.
>> 
>> It allows using iptables from a network namespace owned by an user
>> that has no write access to XT_LOCK_NAME (by default under /run), and
>> without setting up a new mount namespace.
>> 
>> $ XTABLES_LOCKFILE=/tmp/xtables unshare -rn iptables ...
>> 
>> Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
>> ---
>>  iptables/xshared.c | 7 ++++++-
>>  1 file changed, 6 insertions(+), 1 deletion(-)
>> 
>> diff --git a/iptables/xshared.c b/iptables/xshared.c
>> index c1d1371a..291f1c4b 100644
>> --- a/iptables/xshared.c
>> +++ b/iptables/xshared.c
>> @@ -248,13 +248,18 @@ void xs_init_match(struct xtables_match *match)
>>  
>>  static int xtables_lock(int wait, struct timeval *wait_interval)
>>  {
>> +	const *lock_file;
>
> This does not look right. Typo?

yes sorry, I've messed it up.  I'll send a v2.

Thanks,
Giuseppe


      reply	other threads:[~2020-07-15  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 16:52 [PATCH] iptables: accept lock file name at runtime Giuseppe Scrivano
2020-07-14 23:27 ` Phil Sutter
2020-07-15  6:19   ` Giuseppe Scrivano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgdtti4s.fsf@redhat.com \
    --to=gscrivan@redhat.com \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).