netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: David Buchmann <david@jazznetworks.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfqueue: Get pid of socket owner
Date: Mon, 7 Nov 2016 17:38:32 +0100	[thread overview]
Message-ID: <20161107163832.GB24908@breakpoint.cc> (raw)
In-Reply-To: <71D00C03-A2AD-4836-8F5F-724AECE75DE6@jazznetworks.com>

David Buchmann <david@jazznetworks.com> wrote:
> I've started work to add support in the nfnetlink_queue kernel module for
> sending the pid of the process owning the socket triggering nfqueue, and I
> want to add the userspace support in libnetfilter_queue, but before I get
> too invested in that work I just want to check whether there are any
> objections to such a feature in either the kernel or in the
> libnetfilter_queue library?
> 
> https://github.com/wuurrd/linux/commit/79d12e93ca2a28c0939937a5a690943311e4bf6c

I think this should just be added to nfqnl_put_sk_uidgid(), and just use
the new sk->sk_uid that got added to net-next recently:

--- a/net/netfilter/nfnetlink_queue.c
+++ b/net/netfilter/nfnetlink_queue.c
@@ -271,6 +271,10 @@ static int nfqnl_put_sk_uidgid(struct sk_buff *skb, struct sock *sk)
                        goto nla_put_failure;
        }
        read_unlock_bh(&sk->sk_callback_lock);
+
+       if (nla_put_be32(skb, NFQA_PID, htonl(sk->sk_uid)))
+               return -1;
+
        return 0;
 

As we don't need any locking for this I'd also be fine to just always
pass this to userspace regardless of any feature flags.

  reply	other threads:[~2016-11-07 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 14:21 nfqueue: Get pid of socket owner David Buchmann
2016-11-07 16:38 ` Florian Westphal [this message]
2016-11-07 17:09   ` Florian Westphal

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=20161107163832.GB24908@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=david@jazznetworks.com \
    --cc=netfilter-devel@vger.kernel.org \
    /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).